Hi - we've had issues with our Windows Server 2016 farm since the rollout of this version to our servers; Windows Search roaming now appears to be broken for many folks, and it is causing all kinds of logon issues that seem to get worse every day (this seems to point to repeated index corruption). Despite deploying the latest ADMX files, we continue to see that the Group Policy Management console views the RoamSearch configuration as an "additional registry key setting", despite the fact that I am able to configure it within the policy itself. This feels like something might be amiss with the policy to begin with...? Thank you for your attention to this.

Hi Jason, is there any roadmap to fix the OneDrive signing in bug on Server 2019 ? This is affecting many of our users. 

WSL Unable to Access FSLogix Profile – Compatibility Issue with WSL Distributions

Overview:
After upgrading to the latest FSLogix version 3.25.202 or 3.25.401, users may experience issues where no WSL distribution is able to read from or write to the FSLogix-mounted user profile. This problem was observed in environments running Windows Server 2022, WSL 2 (Kernel 5.15.167.4-1), and Rancher Desktop.

Issue Description:
When launching Rancher Desktop, startup fails because the associated WSL distribution attempts to access paths like C:\Users\<username>\AppData\Local\rancher-desktop, which are inaccessible.
Example output from WSL:

ls -al /mnt/c/Users/

ls: /mnt/c/Users/.docker: No such file or directory

ls: /mnt/c/Users/.eclipse: No such file or directory

This behavior is consistent across all WSL distributions – not just Rancher Desktop – indicating a broader issue with WSL accessing FSLogix-mounted profiles.

Root Cause:
The issue appears to be introduced with FSLogix version 3.25.202 and 3.25.401. After extensive testing and analysis, it was confirmed that downgrading to FSLogix version 2.9 resolves the problem entirely, restoring normal access from WSL distributions.

Conclusion:
The latest FSLogix release introduces compatibility issues with WSL 2 that prevent access to user profiles. Until a fix is provided, environments that depend on WSL (especially those using Rancher Desktop) should consider rolling back to FSLogix 2.9 to ensure functionality.

We are still experiencing some users across diffrent servers which keep getting the 58tm1 error when openening office apps after signin out the day earlier.

This is on windows server 2022 with the latest version of FSLogix. 

If we delete the aadbrokerplugin folder the user can sign in again but it comes back the next day.
Not all users are experiencing this.

Is this issue on the Radar for the FSLogix team? it seems to be an issue with the roamingidentity function.

Thanks for the updates. Looking forward to the OneDrive sign in fix :)

Hi,

there is a problem with the 25.04 admx file:

-------------------------
The resource displayName listed in the property "$(string.v2105_Definition)" could not be found.

File \\contonso.com\sysvol\domain\Policies\PolicyDefinitions\fslogix.admx, Row 11, Column 74
------------------------

We've skipped 25.02 but tested admx from this version. Same problem.

admx from 22.10 hotfix 4 is OK.

Any ideas?

Thanks in advance!

Hi Jason, thanks for the prompt and clear answer. So it is mostly third party tools that inject themselves somewhere in the logon process. Good to know.  

Hi Jason, what do you mean by ‘ODFC settings applied to systems after ProfileLoad during sign in aren't applied to the user.’? Which settings does this relate to and what potential (negative) results could we encounter?

Hi Jason do you know when this version will be included in the marketplace images ? Thanks