Did anyone ever encounter problems with programs updating/doing automatic file renamings inside an FSLogix Profile and know the root cause and solution to this? We have a legacy application that lives in the user’s roaming profile %APPDATA%\Prosytec\WMSClient.exe The program runs great. No issues. BUT its weird Update-Process occacionally bricks the programm: It updates itself when starting WMSClient.exe by downloading WMSClient.upd, renaming the running/current WMSClient.exe to .old, renaming .upd to .exe, and starting the new version. This works most of the time, but sometimes the application crashes during the update. In one case, the rename to .old repeatedly failed with error 650, referring to an invalid device object or a device object not attached to the specified volume. In a later case, it crashed even earlier, immediately after WMSClient.upd appeared, before .old was created. Now why do I post this in the fslogix channel? I moved the whole application folder from AppData to the user’s redirected Documents folder. That location is not part of the FSLogix container and is hosted on a Linux Samba file server. Since then, the application appears to update and run correctly.

Does your problem program use a filter driver?

It appears to be a normal user-mode application performing standard file operations. The filter drivers relevant to the problem is most likely FSLogix ^^ (disclaimer: I have no idea about filter drivers)

Well FSLogix filter driver would only generally cause an issue if there was another filter driver involved. It could just be a bug though

Follow up: we moved the application out of fslogix (appdata) and into the redirected documents folder of the user. Problem solved. So there is some kind of problem with fslogix and the read/write/delete operations of the update mechanism of this software.

Does the problem still occur if you leave the files in AppData but don't use FSLogix to capture the profile?

I did not try that but assume that it would work. However I don't have the time to investigate further because it is low priority now.