WSL icon indicating copy to clipboard operation
WSL copied to clipboard
verified publisher icon microsoft

WSL cannot read local profile with FSLogix

Open smitpascal opened this issue 7 months ago • 4 comments

Windows Version

10.0.26100.3775

WSL Version

2.4.13.0

Are you using WSL 1 or WSL 2?

  • [x] WSL 2
  • [ ] WSL 1

Kernel Version

5.151674

Distro Version

24.04

Other Software

Linux cannot read metadata of files in a profile redirected by FSLogix, causing the enrollment of Ubuntu to fail. This may be related to the new 'GetFileInformationByName' functionality in Windows 11 24H2, Python 3.12+ has the same issue (https://github.com/python/cpython/issues/133965).

This also means that wsl incorrectly sees these files as non-existent.

Repro Steps

  • Set up an AVD with FSlogix as profile management solution.
  • Log in as user with FSlogix managed profile
  • Install any linux distro
  • Start linux distro with '-e /bin/bash' option
  • When at '/mnt/c/Users/':
  • ls -lAh
  • output:

Image

Expected Behavior

A certain amount of metadata is displayed:

Image

Actual Behavior

See steps

Diagnostic Logs

No response

smitpascal avatar May 20 '25 13:05 smitpascal

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

github-actions[bot] avatar May 20 '25 13:05 github-actions[bot]

/emailed-logs

smitpascal avatar May 20 '25 14:05 smitpascal

Diagnostic information 
Found '/emailed-logs', adding tag 'emailed-logs'

github-actions[bot] avatar May 20 '25 14:05 github-actions[bot]

FSLogix might have had a regression here. We investigated logs in another related issue and found that it wasn't due to changes in WSL and recommended filing an issue with FSLogix.

Linking the issue here incase it's the same report: https://github.com/microsoft/WSL/issues/12899

craigloewen-msft avatar May 20 '25 15:05 craigloewen-msft

Closing since this isn't a WSL issue

OneBlue avatar May 27 '25 21:05 OneBlue

Any update on this? Im facing the same issue

Kosaln avatar Jun 19 '25 14:06 Kosaln

@Kosaln

The following is a workaround that works on my end:

  • Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\frxdrvvt
  • Backup key (optional)
  • Modify value for SupportedFeatures and set it to B Hexadecimal
  • Reboot the machine

smitpascal avatar Jun 24 '25 07:06 smitpascal

@smitpascal This works. Thanks!

Kosaln avatar Jun 24 '25 09:06 Kosaln

@smitpascal thank you that works, can you please explain how you came up with it and what this regkey does exactly

ximragequit avatar Jul 22 '25 09:07 ximragequit