Forum Discussion
FSLogix Profile Hangs - "Reset to device, \Device\RaidPort1, was issued."
Through the FSLogix team via Microsoft Support, we were given a workaround that worked.
That is to turn off Hiding Rules in FSLogix completely. Essentially not using that feature at all. Since then, that error has stopped.
But we had to go remove a bunch of Start Menu shortcuts we didn't want users trying or were useless to them. Definitely a pain, but it stopped the bleeding.
I hope this helps.
Thanks for your answer. In our case it was a totally other issue. I want to share it, so it maybe helps someone who experience the same issue.
We found out that the fileserver, where the share for the fslogix VHDX files are stored, had memory usage from over 95% from time to time. At the exact same timetamp we saw warnings from NTFS (Event ID 140) in the Eventlog of the fileserver and the "Reset to device, \Device\RaidPort1, was issued." Event log entry on the affected Terminalserver. It seems that fslogix somehow could not finish the VHDX mount or unmount process successfully at the time when not enough memory was available on the fileserver and after that it started to act awkwardly on the affected terminalserver resulting in the exact behavior you described. Adding more memory to the fileserver completely solved our problem.
BR,
Andreas