Note: This information is generally only applicable for single-user OSs and not for multi-user OSs.
With the release of Win 10 1809, the Windows search service has implemented a method for the Windows Search service to roam a user's search index along with their profile. This has been principally mentioned in relation to Windows 10 multi-user OS and the Server versions of Windows (2019 and above). However, it is applicable for single-user OSs as well. So there are now two methods to roam a user's search index on single-user OSs (Windows 10 1809 and above): FSLogix or the Windows Search service. They both store the user's search index in the profile, but in different locations. The indexing engine for both is the Windows Search service; the difference is that FSLogix redirects the default OS location into the profile where the Windows Search service (with the setting below) creates a per-user index in another location in the profile. They cannot be used at the same time. One or the other must be properly configured while the other is disabled.
Recommendations: Review all the settings and storage locations mentioned below to determine which method is in operation. If it appears that both may be in operation, disable one method, reboot, and then validate that only one method is operating. Otherwise, validate the settings and storage for the method configured or desired.
FSLogix:
- For storage of the search index in the Profile container enable (or create as necessary) the following registry key: HKLM\SOFTWARE\FSLogix\Profiles\RoamSearch (DWord) =1.
- For storage of the search index in the Office container enable (or create as necessary) the following registry key: HKLM\SOFTWARE\Policies\FSLogix\ODFC\RoamSearch (DWord) =1.
- Note: If both the Profile Container and Office Container are configured, the database will be placed in the Profile Container VHD(X). It is recommended that search be configured in either Profile Container or Office Container, but not both.
- Note: If both the Profile Container and Office Container are configured, the database will be placed in the Profile Container VHD(X). It is recommended that search be configured in either Profile Container or Office Container, but not both.
- Validation: Check for files with current update times in this location - c:\programdata\Microsoft\Search.
- Also check using the frx.exe utililty as below for the redirection from the above location into the VHD as the highlighted line below shows. Note: the 'HarddiskVolume' number shown may be different from system to system even when it is commonly referencing the c: drive. This is due to the way underlying Windows systems identify volumes at a level below the drive letter identification level.
- Note: it may be possible, but is not common, to redirect the default/common system index location. If that is the case, then the paths given above would not be correct and validation of the alternate location paths would be necessary.
- Also check using the frx.exe utililty as below for the redirection from the above location into the VHD as the highlighted line below shows. Note: the 'HarddiskVolume' number shown may be different from system to system even when it is commonly referencing the c: drive. This is due to the way underlying Windows systems identify volumes at a level below the drive letter identification level.
Windows Search Service:
- Setting: EnablePerUserCatalog (DWord) = 1 is set (or created as necessary) in the following location - HKLM\SOFTWARE\Microsoft\Windows Search.
- Validation: Check for files with current update times in this location - C:\Users\<username>\AppData\Roaming\Microsoft\Search\Data\Applications\<User SID>\<User SID>.edb
Microsoft
