Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

OneDrive error FSLogix_unsupported_environment on virtual machines that use FSLogix

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

The OneDrive sync client shows "OneDrive can't sync", "Contact your system administrator for help." and "Error code: FSLogix_unsupported_environment", then closes when the message window is closed. Microsoft's page gives one cause: the sync client is blocked on virtual machines that use an FSLogix version earlier than FSLogix 2009 hotfix 1, and it gives one fix: "download and install the latest version of FSLogix on all virtual machines that use the OneDrive sync client." Check the version first, then update.

What the error means

FSLogix is a Microsoft product installed on the virtual machine; the install page calls it FSLogix Apps. The page says the OneDrive sync client is blocked on virtual machines that use an FSLogix version earlier than FSLogix 2009 hotfix 1, and "These earlier versions are no longer supported by Microsoft."

Two points follow from that wording:

  • The fault is the version of FSLogix on the machine where the user's session runs. A user can be fine on one host and blocked on another if the hosts differ.
  • The page's scope is "virtual machines that are configured by using FSLogix". It does not name a Windows Server version and does not describe a registry setting that switches the check off. Updating FSLogix is the documented fix.

Microsoft's FSLogix release notes add a general rule: "Customers are required to install and use the latest version." The install page says that to open a support case you are required to have the latest version.

Likely causes

Cause What you see How to confirm
FSLogix on the host is older than 2009 hotfix 1 Every user on that host gets the error; the sync client closes Run frx version on the host; any host not on a current release is a candidate (the note after step 5 explains why)
Only some hosts in a pool are old Users are blocked only when a session lands on an old host Check the version on every host, not only one
An old FSLogix is baked into the golden image New or rebuilt virtual machines have the error from first sign-in Check the version inside the image or template
The version was read from the wrong place One tool says current, another says old Compare the three methods below on the same machine

Prove the cause before changing anything

All of these are read-only. Sign in as a local administrator on the affected virtual machine.

  1. Use the FSLogix command-line tool:
C:\Program Files\FSLogix\Apps\frx.exe version
  1. Or read the install version from the registry:
(Get-ItemProperty -Path HKLM:\SOFTWARE\FSLogix\Apps).InstallVersion
  1. Or read the installed product entry:
$uninstallPath = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall"
$appCheck = Get-ItemProperty -Path $uninstallPath\* | Where-Object { $_.DisplayName -eq "Microsoft FSLogix Apps" }
($appCheck | Where-Object {$_.EstimatedSize -eq ($appCheck | Measure-Object -Maximum EstimatedSize).Maximum}).DisplayVersion
  1. For many machines, Microsoft names an "FSLogix Version Validation script", and says: "The following PowerShell script is provided as is and isn't supported by Microsoft." Run any such script on one machine first.
  2. Write the version of each host in a list, with the host name and the date.

Microsoft's release notes give no build number for "FSLogix 2009 hotfix 1"; the oldest release listed there is FSLogix 2210 hotfix 4 (version 2.9.8884.27471). A version number from frx version therefore cannot be matched to 2009 hotfix 1 from those notes. Use this rule instead: any host that is not on a current release is updated, because Microsoft's fix is the latest version.

The install page also describes an Installed apps check: right-click Start, choose Installed apps and find Microsoft FSLogix Apps.

Example (illustrative): a collection on contoso.com.au has four session hosts, rds01 to rds04. A check shows rds01, rds02 and rds03 on a current release and rds04 on a version earlier than 2009 hotfix 1. With 40 users spread evenly, 10 users sit on each host. Only the 10 users on rds04 get the error, so a quarter of the users are affected, and the help desk sees it as intermittent because a user only meets the fault on the days the connection broker places them on rds04.

Fix

The fix is to bring the FSLogix on every affected host to a current release. Plan it as a change, because FSLogix handles user profile containers.

Get the installer

The install page says to "upgrade to the latest version of FSLogix as quickly as your deployment process can allow". It offers a direct download and the Microsoft Download Center. A footnote says the Download Center "provides only the last two feature and associated hotfix releases", so save the installer you use. Check the current release on the release notes page.

Take a record first

Before changing a host, record frx version output, the FSLogix profile path or container location in use, and the count of signed-in sessions. Copy the current installer package if you still have it.

Install on one host first

Disruptive step: the install needs a reboot of the host. Impact: every user signed in to that host is disconnected, and an unsaved document is lost. Choose a time when the host is empty, or drain the host with the method your Remote Desktop design uses, so no new sessions land on it. Back-out: if a problem other than the OneDrive error appears after the update, run the installer you used with /uninstall, install the earlier package you saved, and reboot. Be aware that going back to a version earlier than 2009 hotfix 1 brings the same OneDrive error back, so the back-out is only for returning to a previous supported release.

Risk: the install page carries a warning about the April 2026 Windows Server update, in which the default Kerberos encryption type changes from RC4 to AES-SHA1, and "File shares hosting FSLogix containers that aren't upgraded to AES-SHA1 might have access issues after this change is applied." Before you update the hosts, find out whether your file shares for profile containers have been moved to AES-SHA1. Back-out for the share is the owner's change record for the share.

Install steps from the page: extract the downloaded .zip, go to the x64 folder, then Release, run FSLogixAppsSetup.exe, accept the licence terms, select Install, watch the progress and reboot. The same page lists silent switches: /install (default product installation), /quiet (no UI and no prompts), /norestart (suppresses any attempt to restart) and /log log.txt. A silent install without an automatic restart would use /install /quiet /norestart.

Update the image and the other hosts

After the first host is proven, update the golden image so rebuilt machines do not return to the old version, then update the remaining hosts one at a time.

Save first: before touching the golden image, make a copy of it (a clone, snapshot or exported template, whichever your platform provides) and write down the image name, its version and the FSLogix version inside it. The earlier record of host versions covers hosts only, not the image.

Disruptive step: installing FSLogix into the golden image replaces software in the master that every machine rebuilt from it will use. Impact: any session host rebuilt from the changed image carries the new FSLogix, and an image that is changed wrongly spreads the fault to every rebuilt host. Back-out: put the saved copy of the image back in use and rebuild the affected hosts from it; hosts that are already running are not changed by this and keep the per-host back-out above.

Risk: updating every host in one pass leaves no working host if the new release misbehaves in your environment. Update in small groups, and let the first updated host serve real users for a working day before you continue. A host still on the old release keeps showing the OneDrive error, so move its users to updated hosts as you go. Back-out for a group is the per-host back-out above.

Confirm the fix

  • frx version on each host shows the release you installed.
  • A test user signs in to an updated host, OneDrive starts, signs in and shows the usual sync status. The error window does not appear and OneDrive does not close.
  • A file created in the OneDrive folder on that host appears in the web version of OneDrive.
  • A list of every host and image with its FSLogix version shows no entry earlier than the release you chose.

What to watch afterwards

  • New session hosts built from an old template. Add the version check to the build checklist.
  • Hosts added back after maintenance or restored from a backup. A restored machine carries the FSLogix version it had at backup time.
  • The FSLogix release notes. Microsoft states that customers are required to install and use the latest version, so plan a regular version check rather than waiting for an error.
  • OneDrive-related fixes in newer releases. The release notes for FSLogix 26.08 list fixes such as "unlinking OneDrive during a session could lead to data loss" and corrupted OneDrive cloud-only placeholder files, which is a reason to keep the version current.

Risks and limits

These commands have not been run or lab-tested.

  • Microsoft's error page is short: it gives the cause and the fix and no further diagnostic. If the error continues after FSLogix is current, contact Microsoft Support; the install page says a current FSLogix version is required to open a support case.
  • Microsoft's error page names no affected Windows Server or client versions beyond "virtual machines that are configured by using FSLogix".
  • Microsoft's error page describes no way to hide the error or turn off the version check, and none is given here.
  • The version-check script for many machines is not supported by Microsoft.
  • Updating FSLogix changes the profile-container software for every user of the host. Test on one host and keep a recent backup of the host and of the profile container share before the change.
  • The release notes and install pages are updated over time, so check the current pages before relying on a version name or download link given here.

Sources