Last updated:
An FSLogix update is intended to fix problems, but under certain conditions it can prevent Office containers from mounting.
Microsoft has confirmed this issue in FSLogix 26.01 (3.26.102.18413).
🔴 The symptoms
In environments using both FSLogix Profile Containers and ODFC Containers, creating or mounting the ODFC VHD(X) fails.
The key condition:
CleanupInvalidSessions = 1
This setting is intended to clean up orphaned sessions and prevent issues with locked containers.
🔬 Technical cause
The issue occurs in FSLogix 26.01 when the following conditions are combined:
• Profile Containers enabled
• ODFC Containers enabled
• CleanupInvalidSessions enabled
Microsoft has officially documented this problematic combination.
🛠️ Diagnosis
First, check the installed FSLogix version.
Then check the registry value:
|
1 2 3 4 5 |
HKLM\SOFTWARE\FSLogix\Apps CleanupInvalidSessions (DWORD) Value 1 = enabled |
Also review the FSLogix logs under C:\ProgramData\FSLogix\Logs for errors when creating or mounting the ODFC container.
✅ Workaround and fix
As a temporary workaround, Microsoft recommends disabling CleanupInvalidSessions.
The fix was released in FSLogix 26.01 CU1 (3.26.126.19110) on February 10, 2026.
Updating to a current FSLogix version approved for your environment is therefore the preferred solution.
⚠️ Important: Disabling CleanupInvalidSessions may prevent automatic cleanup of orphaned containers after sessions end unexpectedly.
💡 Takeaway
If ODFC containers suddenly stop mounting after an FSLogix update, storage or permissions are not necessarily responsible.
Sometimes the cause is simply the combination of a product version and an otherwise useful setting.
📚 Sources:
Microsoft FSLogix Known Issues:
https://lnkd.in/eU_ygcFg
Microsoft FSLogix Release Notes:
https://lnkd.in/eiMCtPqw