[German]There has been a nasty bug in OneDrive in conjunction with FSLogix since weeks, that occurs on Windows Server 2019, according to a reader observation. OneDrive items can then no longer be renamed. Microsoft Support has already thrown in the towel in this context. Here is a summary of what we know so far.
OneDrive suddenly stops working
German blog reader Mischa K. from Switzerland has reported early September 2019 a crude observation that may also be plaguing other administrators. Mischa wrote in an email dated September 11, 2025, "We have been observing a bug in FSLogix for several weeks now," with an annoying error pattern emerging.
The FSLogix OneDrive bug
When FSLogix is used in conjunction with Windows Server 2019, files and folders in OneDrive can no longer be renamed. When creating files and folders, the default name (New Folder) simply appears and cannot be renamed, Mischa wrote.
In this case, the user only sees the meaningless error dialog shown in the screenshot above. Renaming via Powershell/CMD does not work either. All in all, this is quite annoying, as it is not possible to work with OneDrive in this scenario (see below).
Only occurs with FSLogix in different versions.
According to blog readers, the bug outlined above occurs for all of their customers with the configuration mentioned below and with various FSLogix versions. Tests were carried out with FSLogix versions 25.02 and 25.06, among others.
The reader and his colleagues have not yet been able to test FSLogix version 25.09, which was only released on September 10, 2025, due to a lack of maintenance windows. However, a glance at the release notes gives little cause for hope.
The Windows Server 2019 system environment
The blog reader's company uses Windows Server 2019 in conjunction with the above-mentioned FSLogix versions. FSLogix is a profile management solution originally developed by Randy Cook that is used to personalize user sessions for application and desktop virtualization technologies.
According to the reader, the problem only occurs under Windows Server 2019 when the user's profile is located on FSLogix. In the reader's environment, for example, administrators are excluded from FSLogix profile management as soon as there are problems with FSLogix. In this case, the user profile is located under C:\Users, and OneDrive works without any problems.
Users either synchronize their OneDrive manually or it happens automatically through the Known Folder Move. There, FSLogix can no longer be used to rename the folder names. So it can definitely be attributed to FSLogix.
Addendum: The issue has been fixed in FSLogix 2509, according to my German blog readers (see FSLogix 25.09 fixes Outlook 365 error [58tm1] and Windows Server 2019 OneDrive rename bug).
Microsoft support didn't help
To my knowledge, FSLogix was acquired by Microsoft in 2023, so it is an official product. The reader opened a ticket on July 14, 2025, and it was closed on September 1, 2025, with the following explanation:
After further discussions with the escalation department and my boss, I regret to inform you that the escalation has been rejected as the case is outside the scope of our support.
Microsoft 365 support also declined to assist with the reader's inquiries (only FSLogix is supported in connection with AVD). Therefore, the reader has exhausted all options. His hope lies in the collective knowledge of the readership—perhaps someone knows a solution?
Similar articles:
Citrix: FSLogix causes logon and logoff errors
FSLogix blocks OneDrive synchronization in virtual machines
FSLogix v2210: Bugs, bugs, it's terribad"
Windows Logon hangs on "Other user" because of Citrix Workspace app; FSLogix V2210 bug causes logon hang
Microsoft Teams: Appointment/language bug and new/old problems with FSLogix in connection with Citrix/VDI
