Share via

FSLogix container profile and issue withindexing

Brice Pradel 0 Reputation points
2026-03-03T13:46:22.5533333+00:00

Dear Technet,

I'd like to submit an issue we are having here.

Please find below a description of the issue we are facing with our environment.

We have a pool of Windows 11 Pro 25H2.

It's an on premise endpoint Single-User using FSLogix to roam user's profile.

We have One Drive setup for each user, linked to their Microsoft account, with E3 licenses.

In the One Drive, there are links coming from Sharepoint Online environment for files and folders access in the File Explorer.

When we perform searches in the Windows Explorer search box, the search result doesn't return anything or sometimes wrong answer.

When we do it in an environment without FSLogix, it works perfectly.

After performing some tests, we conducted it to the conclusion that  the indexing of folder is only performed one time when the user's profile is created.

But after that, it doesn't update, unlike with profile outside of the FSLogix setup.

Which means no search on new files, renamed files, etc.

Some consultants were able to contact a distributor's technical presales consultant for AVD environment.

They have been able to reproduce it in a similar environment as us.

But also noticed that the issue is not existing if they use AVD + Windows 11 25h" and a multi-users image (instead of the single-user)

That distributor's technical presales consultant asked us to raise the ticket at MS Support.

Does anyone already saw that kind of issue and was able to fix it ?

Many thanks.

Windows for business | Windows Client for IT Pros | User experience | FSLogix
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Tan Vu 235 Reputation points Independent Advisor
    2026-03-07T15:22:55.06+00:00

    Hi Brice Pradel,

    I just wanted to follow up and see if your issue has already been resolved. If you still need any clarification or additional help, please feel free to reply here. If the previous information helped solve your problem, consider marking the response as “Accept Answer” so it can assist other community members as well. Thank you!

    0 comments
  2. Tan Vu 235 Reputation points Independent Advisor
    2026-03-03T15:26:38.6+00:00

    Hi Brice Pradel,

    The issue appears to be related to how FSLogix profile containers interact with Windows Search indexing. When the profile container is mounted, the Windows Search index may not be properly rebuilt or reattached after the initial profile creation. As a result, the index can become stale and stop reflecting newly created, renamed, or synchronized files. In Windows 11, the search architecture has evolved to use a modern per-user indexing mechanism, and OneDrive Files On-Demand also affects how content is indexed (online-only files are not indexed until hydrated locally). Therefore, the combination of profile mount timing, OneDrive file state, and legacy FSLogix search configuration can lead to the search index appearing "frozen".

    First, please ensure that the Windows Search (WSearch) service is running correctly. If the service is stopped, disabled, or not starting automatically, indexing will not function properly and search results will not update. Kindly verify in services.msc that the Windows Search service is in a Running state and that the Startup type is set to Automatic (or Automatic - Delayed Start). If the service does not remain stable, we recommend reviewing Event Viewer under Microsoft -> Windows -> Search for related indexing errors.

    Second, on Windows 10 and Windows 11, it is not recommended to use the legacy FSLogix Search Roaming configuration. Modern versions of Windows implement per-user search indexing natively, and enabling legacy settings such as RoamSearch=1 or EnableSearchRoaming=1 may cause conflicts or prevent proper index updates in single-user Windows 11 environments. Please review the following registry path on the affected machine:

    HKLM\SOFTWARE\FSLogix\Profiles

    Ensure that legacy Search Roaming settings are not enabled (for example, set RoamSearc to 0 if present). After making changes, we recommend restarting the machine and testing again-ideally with a newly created profile-to confirm whether the behavior has improved.
    I hope this answer is helpful to you. Have a great day!
    TV

    0 comments
  3. Q&A Assist
    2026-03-03T13:46:44.8266667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The described behavior matches known limitations and design aspects of FSLogix profile containers and how they interact with search and cloud storage (OneDrive/SharePoint) in non-persistent or containerized profiles.

    Key points from the documented behavior:

    1. FSLogix profile containers roam the user profile and provide high‑performance access to profile data in VDI and similar scenarios, but they do not change how Windows Search indexes remote/cloud content.
      • FSLogix stores the complete user profile in a VHD/VHDX and attaches it at sign‑in so it appears as a local profile, but indexing and search behavior are still governed by Windows and the storage provider.
      • FSLogix is primarily solving profile roaming and performance issues (for example, Outlook cached mode and OneDrive support in non‑persistent environments), not providing its own indexing engine.
    2. For Microsoft 365/Office data, FSLogix’s Office 365/ODFC container is specifically designed to roam Outlook data and the Windows Search index for Outlook in non‑persistent environments.
      • In RDS/non‑persistent scenarios, the Office 365 container roams the Outlook .OST and its search index so Outlook search is immediately available across sessions.
      • This improvement is documented for Outlook search; there is no corresponding FSLogix feature in the provided material that extends or maintains Windows Search indexing for general OneDrive/SharePoint‑synced file system content in the same way.
    3. OneDrive with FSLogix is supported and works by redirecting the default OneDrive path into the FSLogix profile container.
      • Users should select the default OneDrive location (C:\Users\%username%\). FSLogix redirects this into the container, and OneDrive disk‑space policies evaluate the FSLogix VHD size rather than the OS disk.
      • This ensures data and quota behavior are correct, but again does not introduce additional search/indexing logic beyond what Windows and OneDrive provide.
    4. The documentation provided does not describe a supported configuration or setting in FSLogix that forces continuous or refreshed Windows Search indexing for OneDrive/SharePoint locations in single‑user Windows 11 with FSLogix profiles.
      • There is no documented FSLogix setting in the context that would “re‑trigger” or maintain Explorer search indexing for new/renamed files in those synced locations when using profile containers.
      • The only search‑specific enhancement described is for Outlook search via the Office 365 container.

    Given the above, from the available documentation:

    • FSLogix is functioning as a profile/container solution; it is not documented as responsible for maintaining or refreshing Windows Search indexing for OneDrive/SharePoint content in Explorer.
    • The issue seen (indexing apparently only occurring at initial profile creation and not updating) is not addressed by any configuration or fix in the provided FSLogix documentation.
    • The only search‑related FSLogix feature documented is Outlook search roaming via the Office 365 container in RDS/non‑persistent environments.

    From the supplied material alone, there is no documented FSLogix configuration change or workaround that resolves the described Explorer search/indexing issue for OneDrive/SharePoint content in a single‑user Windows 11 25H2 + FSLogix profile container scenario.

    Escalation to Microsoft Support, as already suggested by the presales consultant, is appropriate because the behavior differs between similar environments (AVD multi‑user vs single‑user) and is not covered by the current FSLogix guidance.

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.