FSLogix causes Python 3.12 and WSL to incorrectly report files and folders as non-existent / missing metadata

Question

FSLogix causes Python 3.12 and WSL to incorrectly report files and folders as non-existent / missing metadata

Pascal Smit 5

In an AVD environment for a customer we need both Python 3.12+ and WSL. QGIS, for example, depends on Python 3.12+. It seems that at least the 'GetFileInformationByName' syscall returns incorrect information on paths within an FSLogix managed profile, causing all files and folders in the user's profile to be seen as non-existent by Python, breaking the application. WSL does not seem to use this specific syscall, but related ones, but seems to have the same issue. The issue exists with 25.02 and 25.04. Does anyone have a workaround or solution?

https://github.com/python/cpython/issues/133965
https://github.com/microsoft/WSL/issues/12939

1 answer

Your answer

Answer 1

Anonymous

Hello,

Thank you for posting the question on Microsoft Windows forum!

You can follow the below step to check.

Check if you are using the latest version of FSLogix,

currently the latest version of FSLogix is FSLogix 25.04, please update FSLogix to the latest version to check if the problem still occurs.

https://learn.microsoft.com/en-us/fslogix/overview-release-notes#fslogix-2504

Temporarily disable FSLogix to test if the problem reoccurs

Disable FSLogix via Group Policy:
- Open the Group Policy Editor (gpedit.msc).
- Navigate to Computer Configuration > Administrative Templates > FSLogix.
- Locate the relevant FSLogix settings and disable them.
Modify Registry Settings:
- Open Registry Editor (regedit).
- Go to HKEY_LOCAL_MACHINE\SOFTWARE\FSLogix\Profiles.
- Look for the setting Enabled and set its value to 0 (default) to disable FSLogix.

If the problem disappears after shutting down FSLogix, it is recommended that you contact the Python and WSL. QGIS technical teams, as it may be related to compatibility between the software, and if necessary a technical support ticket can be opened with the Microsoft FSLogix team at the same time to further investigate the issue together.

Hope the above information is helpful!

Pascal Smit 5 Reputation points

2025-06-04T11:14:56.98+00:00

I will verify with the disabling of FSLogix, but am certain the issue is with FSLogix. When testing on another system without FSLogix the software works as expected.

The issue persists with 25.04.

WSL referred me to FSLogix support. An issue has already been raised with Python.
Pascal Smit 5 Reputation points

2025-06-06T10:10:38.53+00:00

The issue disappears when FSlogix is not used. The issue is not present for Python 3.12 in Windows 23H2, which is consistent with the fact that the API function "GetFileInformationByName" is only available from 24H2 and python falls back to the old-style "open->check-if-successfully-opened" method when the new API function is not available. WSL uses a related API function, that must have been available earlier and has the same underlying bug. WSL therefore does have the issue on 23H2 with FSlogix. This needs to be fixed in the way FSLogix interacts with the NTFS subsystem.
Pascal Smit 5 Reputation points

2025-06-06T11:14:47.3433333+00:00

Next to that, WSL already closed the issue as they see it as an FSLogix regression: https://github.com/microsoft/WSL/issues/12939

Share via

FSLogix causes Python 3.12 and WSL to incorrectly report files and folders as non-existent / missing metadata

1 answer

Your answer