FSLogix 26.01 CU1 • v3.26.126.19110 • CRITICAL UPDATE • MARCH 2026

FSLogix Deep Dive
Profiles, Cloud Cache & Versions 2026

FSLogix remains the go-to profile solution for VDI/DaaS โ€” AVD multi-session, Horizon Instant Clone, Citrix MCS/PVS non-persistent. Version matrix, Cloud Cache HA/DR, VHDX tuning, redirections.xml, troubleshooting, and frx CLI โ€” all from real-world production deployments.

// Version Matrix

Current FSLogix Versions โ€” v3 Era (2025/2026)

Microsoft uses YY.MM naming. Download at aka.ms/fslogix-latest. No backports โ€” always upgrade to latest for support eligibility.

ReleaseFull VersionPublishedTypeKey Notes / Why Update
26.01 CU1 Critical 3.26.126.19110 Feb 10, 2026 Latest Critical stability fixes โ€” required for support cases. Profile mount reliability, memory leak fixes, concurrent session improvements.
26.01 3.26.102.18413 Jan 13, 2026 Supported Core stability updates, logon/profile reliability improvements. No new features โ€” upgrade to 26.01 CU1.
25.09 3.25.822.19044 Sep 9, 2025 Supported General stability & fixes. Solid baseline before 26.x era. Still supported but upgrade recommended.
25.06 / 25.04 3.25.xxx Jul / Apr 2025 Supported Teams/OneDrive/Outlook compatibility, earlier v3 fixes. Still supported โ€” but CU1 is materially better.
25.01 3.25.xxx Jan 2025 Supported First v3 stable release. If still on this, upgrade immediately to 26.01 CU1.
2.x era (2210 and older) 2.x.xxx Pre-2025 EOL Unsupported. Known issues with AVD multi-session, Teams 2.0, OneDrive. Migrate immediately.
Best Practice: Integrate FSLogix 26.01 CU1 into gold images + deploy via Intune/SCCM. Pre-v3 (e.g., 2210) unsupported โ€” migrate now. No backports: if Microsoft finds a bug, the fix ships in the next release only.
// Container Types

Profile Container vs ODFC Container

The fundamental architecture decision: one big container or two smaller specialized ones.

Profile Container (Full)

Contains the entire user profile โ€” AppData, NTUSER.DAT, OneDrive, Teams, Outlook PST, browser caches, everything.

+Simplest โ€” one container per user
+Works on any VHD-capable storage
โ€“Bloat risk โ€” PST + Teams cache can push container to 50+ GB
โ€“Large containers = slow mount at logon
ODFC Container (Office Data + Profile)

Separate container for Office data: Outlook cache, OneDrive, Teams, OneNote. Profile Container handles the rest.

+Profile Container stays lean (10โ€“15 GB)
+ODFC can go on different storage tier
+Faster logon โ€” smaller profile mount
โ€“Two containers = more GPO/Intune config
2026 Recommendation: Use both containers (Profile + ODFC) for any AVD or Horizon pooled deployment. Profile Container stays under 15 GB. ODFC holds the Outlook/Teams bloat. Add redirections.xml to exclude browser caches, Windows Temp from both containers.
// Container Options Matrix

FSLogix Profile Container Options

Key registry settings that determine container behavior. Set via GPO (HKLM\SOFTWARE\FSLogix\Profiles) or Intune configuration profile.

Option / Registry KeyValuesBest For2026 Recommendation
EnabledDWORD: 1 (on) / 0 (off)All deploymentsAlways 1. Setting 0 = FSLogix installed but not active.
VHDLocationsREG_MULTI_SZ: \\server\shareSingle storage locationUse CCDLocations instead for Cloud Cache HA. Never mix VHDLocations + CCDLocations.
VolumeTypeREG_SZ: VHDX (recommended) / VHDAllAlways VHDX. VHD is legacy, cannot be resized without workarounds.
SizeInMBsDWORD: 30720 (default = 30 GB)All30 GB good default. Monitor actual usage โ€” resize if consistently >75% full. VHDX compacts automatically.
ProfileTypeDWORD: 0=Normal, 1=RO-diff, 2=RO-delete, 3=RO-merge0 or 3 for pooled; 0 personalType 0 for persistent/personal. Type 3 for non-persistent (merges changes back). Avoid Type 3 with Cloud Cache.
DeleteLocalProfileWhenVHDShouldApplyDWORD: 1Non-persistent poolsSet 1 to remove local profile if FSLogix container is available. Prevents profile corruption fallback.
FlipFlopProfileDirectoryNameDWORD: 1AllSet 1 โ†’ folder named %username%_%sid% (readable). Default 0 = %sid%_%username% (hard to browse).
PreventLoginWithFailureDWORD: 1Non-persistentBlock login if container fails to mount. Set 1 to prevent empty desktop sessions.
PreventLoginWithTempProfileDWORD: 1Non-persistentBlock login if FSLogix falls back to temp profile. Critical for non-persistent โ€” prevents data loss confusion.
Pro Tip: In 2026 pooled (AVD/Horizon/Citrix non-persistent): ProfileType=0 + separate ODFC + redirections.xml + PreventLoginWithTempProfile=1. Keep Profile Container under 15 GB. ODFC can be larger. Monitor with frx list-profiles.
// Cloud Cache (CCD)

Cloud Cache Configuration & Best Practices

Cloud Cache provides native HA/DR: write-first to local cache, async replication to 1โ€“4 remote providers (SMB/Azure). No DFS-R needed. Not the same as Azure StorSimple.

Setting (Registry)Type / ValuePurpose2026 Best Practice
CCDLocationsMULTI_SZ
type=smb,name="Name",connectionString=\\server\share
Define 1โ€“4 remote providers (SMB or Azure)2+ for HA/DR (e.g. Azure Files Premium East + West US). First listed = read-preferred. NEVER mix with VHDLocations.
CacheDirectoryREG_SZ
C:\ProgramData\FSLogix\Cache
Local cache VHDX locationUse ephemeral SSD/NVMe (D: drive on Azure D-series ephemeral OS). High-perf local storage is critical.
ClearCacheOnLogoffDWORD ยท 1Delete local cache on logoffAlways 1 for non-persistent. Default 0 retains โ€” creates stale cache risk on pooled VMs.
HealthyProvidersRequiredForRegisterDWORD ยท 1Minimum healthy providers to allow logon1 = basic HA (logon if at least 1 provider reachable). Set 2 for strict DR (both must be up).
CcdUnregisterTimeoutDWORD ยท 0 (indefinite)Wait time if providers unhealthy at logoff0 = wait forever (safe โ€” don't forcibly eject dirty cache). Tune to 300 for UX balance.
CcdBlockRetryIntervalDWORD ยท 5000 (5s)Retry interval when provider unhealthyDefault fine. Reduce to 2000ms for faster failover detection.

Cloud Cache Config Example (2 Providers)

# GPO/Intune Registry โ€” HKLM\SOFTWARE\FSLogix\Profiles
CCDLocations (REG_MULTI_SZ):
  type=smb,name="EastUS-Primary",connectionString=\\storeast.file.core.windows.net\profiles
  type=smb,name="WestUS-DR",connectionString=\\storwest.file.core.windows.net\profiles-dr

CacheDirectory = D:\FSLogixCache           # Ephemeral SSD on Azure VM
ClearCacheOnLogoff = 1                      # Always for non-persistent
HealthyProvidersRequiredForRegister = 1     # Allow logon if 1 provider up
CcdUnregisterTimeout = 0                    # Don't time out at logoff
2026 Best Practice: Cloud Cache for any multi-region, HA, or DR scenario. Azure Files Premium Primary + SMB Secondary. Monitor via Microsoft-FSLogix-Apps/Operational event log (Event IDs 27, 28 = provider health changes). Avoid with ProfileType=3 โ€” combined overhead degrades logon times.
// redirections.xml

redirections.xml โ€” What to Exclude

Critical for keeping containers lean. Excluded paths are redirected to local temp โ€” not included in VHDX. Wrong exclusions = data loss. Too few = container bloat.

<?xml version="1.0" encoding="UTF-8"?>
<!--
  FSLogix Redirections.xml โ€” Production 2026
  Place at: \\server\share\ProfileContainers\Redirections.xml
  Or: C:\Program Files\FSLogix\Apps\frxshell.exe redirections
-->
<FrxProfileFolderRedirection ExcludeCommonFolders="47">
  <Excludes>
    <!-- Browser caches (major bloat source) -->
    <Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Default\Cache</Exclude>
    <Exclude Copy="0">AppData\Local\Microsoft\Edge\User Data\Default\Cache</Exclude>
    <Exclude Copy="0">AppData\Local\Mozilla\Firefox\Profiles</Exclude>
    <!-- Teams 2.x cache -->
    <Exclude Copy="0">AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache</Exclude>
    <Exclude Copy="0">AppData\Local\Temp</Exclude>
    <Exclude Copy="0">AppData\Local\Microsoft\Windows\INetCache</Exclude>
    <Exclude Copy="0">AppData\Local\Microsoft\Windows\WebCache</Exclude>
    <!-- Windows Update artifacts -->
    <Exclude Copy="0">AppData\Local\Microsoft\Windows\DeliveryOptimization</Exclude>
    <!-- OneDrive sync cache (handled by ODFC container) -->
    <Exclude Copy="0">AppData\Local\Microsoft\OneDrive\logs</Exclude>
    <Exclude Copy="0">AppData\Local\Microsoft\OneDrive\setup</Exclude>
  </Excludes>
</FrxProfileFolderRedirection>
โš  Don't exclude too much: Excluding AppData\Roaming breaks most app settings. Excluding NTUSER.DAT = broken profile. Start conservative: only exclude caches and temp data. Use frx list-profile-size to identify the biggest folders before adding exclusions.
// Storage Sizing

Storage Sizing & Tier Selection

PlatformRecommended StorageMin IOPS/userNotes
AVD (Azure)Azure Files Premium (Private Endpoint)~10 IOPS logon burstNever Standard. Provision min 1 TiB (100k IOPS). Use Private Endpoint.
AVD Cloud CacheAzure Files Premium ร— 2 regions~10 IOPS ร— 2 providersBoth providers on Premium. Local cache on ephemeral D: drive.
Horizon (on-prem)NFS/SMB on All-Flash or NVMe SAN~8โ€“15 IOPS logon burstvSAN ESA best. NetApp AFF or Pure Storage ideal. SMB recommended over NFS for containers.
Horizon + NutanixNutanix Files (SMB 3.0)~8โ€“12 IOPS logon burstEnable SMB Multichannel. Files scale-out handles logon storm well.
Citrix MCS (on-prem)SMB on SSD-tiered NAS~8โ€“15 IOPSSame as Horizon on-prem. SMB3 recommended.
AWS WorkSpaces PoolsAmazon FSx for Windows (SSD)~10โ€“20 IOPS logon burstSSD tier always. Multi-AZ FSx for HA. Same VPC as WorkSpaces.
// frx CLI Reference

frx Command-Line Tool โ€” Production Commands

Profile Management

# List all profile containers on share
frx list-profiles -filename \\server\share

# Show size breakdown of a specific container
frx list-profile-size -vol \\server\share\ -username jsmith

# Copy local profile into FSLogix container
frx copy-profile -filename "D:\profiles\jsmith.vhdx"
  -username jsmith -domain CORP

# Compact VHDX (reclaim free space)
frx compact-profile -filename "D:\profiles\jsmith.vhdx"

# Check container integrity
frx verify-container -filename "D:\profiles\jsmith.vhdx"

Diagnostics & Logging

# Enable verbose logging (temp)
reg add HKLM\SOFTWARE\FSLogix\Logging /v LoggingEnabled /t REG_DWORD /d 1
reg add HKLM\SOFTWARE\FSLogix\Logging /v LogLevel /t REG_DWORD /d 4
# Logs land at: C:\ProgramData\FSLogix\Logs

# Event log path (most useful)
# Applications and Services Logs โ†’
#   Microsoft โ†’ FSLogix โ†’ Apps โ†’ Operational
# Key Event IDs:
#   26 = Profile container mount FAILED
#   27 = Provider health change (Cloud Cache)
#   60 = Profile container mounted OK
#   61 = Profile container dismounted OK

# Flush and recreate stale container lock
frx delete-profile-lock -filename "D:\profiles\jsmith.vhdx"
// Troubleshooting

Common FSLogix Issues & Fixes

Event ID 26 โ€” Profile container mount failed
Check UNC path accessibility from the session host. Verify computer account has Modify rights on share (not just user account). Check antivirus exclusions for FSLogix VHDX paths. Check available space on storage.
User gets temporary profile (empty desktop)
PreventLoginWithTempProfile=1 will block this and show error instead (recommended). Check if VHDX is locked by orphaned session. Run frx delete-profile-lock. Check if another session has it open.
Cloud Cache provider shows 'Unhealthy'
Check SMB connectivity to provider from session host. Test: net use \\server\share. Check firewall rules for SMB 445. Check storage account firewall if Azure Files โ€” ensure session host subnet is allowed.
Profile container growing too large
Run frx list-profile-size to identify top folders. Add exclusions to redirections.xml for browser caches, Teams cache. Run frx compact-profile after exclusions applied. Separate ODFC container for Office data.
User can't log in โ€” container locked (concurrent session conflict)
Occurs when VM powers off without clean logoff (crash, Azure eviction). Find and kill orphaned lock: frx delete-profile-lock -filename path. If lock file corrupted, manually delete .lock file on share (SMB access required)
FSLogix 2.x (pre-3.x) โ€” unexpected behavior with Teams 2.0 / OneDrive
FSLogix 2.x is unsupported. Teams 2.0 changed cache paths. OneDrive sync has known conflicts with 2.x VHDX mounting. Solution: upgrade to 26.01 CU1 โ€” not optional.
// Platform-Specific Notes

FSLogix by Platform โ€” Key Differences

AVD Multi-Session
  • โ†’ Azure Files Premium + Private Endpoint (required)
  • โ†’ Profile + ODFC separation strongly recommended
  • ! Don't use Standard storage tier โ€” IOPS too low
  • ! Enable compaction via policy (new in 26.x)
Omnissa Horizon (Instant Clone)
  • โ†’ NFS or SMB on All-Flash recommended
  • โ†’ ProfileType=0 standard for non-persistent
  • ! DEM + FSLogix together: ensure DEM DirectFlex doesn't conflict with FSLogix AppX rules
Citrix MCS/PVS Non-Persistent
  • โ†’ SMB share on SSD-tiered NAS
  • โ†’ WEM 2511 + FSLogix: use WEM's profile backup scheduling feature
  • ! PVS: BDM/USB boot needed โ€” PXE boot can conflict with VHDX driver loading order
AWS WorkSpaces Pools
  • โ†’ Amazon FSx for Windows File Server (SSD tier)
  • โ†’ Same VPC as WorkSpaces fleet
  • ! Computer account (not user) needs Read+Write on FSx share
  • ! FSx DNS must resolve from WorkSpace VPC โ€” verify DNS server config
// Related

Related Deep Dives