Forum Discussion
MicrosoftThe FSLogix 2201 Public Preview is now available
It seems to be tied to a later (latest?) version of FSLogix since these errors are a relatively new occurrence for my clients.
The only other culprit I could think of that can hold files on driver/kernel level would be the antivirus software. We are using WithSecure (formerly F-secure) maybe other people are using the same?
Since it's a Kernel process there is no way of determining what process opened the file.
Jason_Parker can you elaborate what 3rd party software was involved in other occurrences?
For us the folders that are left in use (access denied) are mainly:
- AppData\Roaming\Adobe\Acrobat\DC
- AppData\Roaming\Downloaded Installations
- AppData\Roaming\Google\Chrome
- AppData\Roaming\Microsoft
- AppData\Roaming\Microsoft Teams\Logs
- AppData\Roaming\Slack
Since it's such a variety of files it's probably FSLogix itself or a virusscanner. I would like to trial running without AntiVirus but the issue only occurs every so often so that could take a long time to determine for sure if the issue stays away or not.
Microsoft- WebSocketService.exe (Citrix)
- PolicyPak
- Credential Manager
- AntiVirus without exclusions
- Thank you for the information.
In my case we are not using the first 2 applications, so they are not exclusively to blame! 'Credential Manager' is the manager from Microsoft itself I assume? Can't call that 3rd party.
Something else I don't understand. Why would these locks be generated when you logoff? If for example the Google folder is locked during normal usage the user would be unable to use Google Chrome. But that is not the case!
Also some other behavior I observed. As soon as the problem occurs for one user. All user that logoff after that exhibit the same behavior. But once again, only when they logoff, during operation no error occurs. To me that seems to indicate that Fslogix itself does something upon user logoff causing certain files to blocked on kernel level.
If it was a virus scanner it would be hit and miss, it's not logical that all the same directories for every user just happened to be scanned the moment a user logs off each and every time.