MicrosoftWSL 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.
