Forum Discussion
Issue - (\Device\HarddiskVolume100) needs to be taken offline to perform a Full Chkdsk.
Hello, We recently had a user encounter this error when logging into one of our AVDs. So far no other user has experienced this issue and the AVD seems to be operating correctly. Looking for info...
This is a headache we keep seeing as I think its also associated with a notification popup for all users on the session host that a drive needs scanning due to errors. I have yet to work out which FSlogix VHDX file it is that needs scanning as the anticipated behaviour from clicking into the notification is for Windows to attempt the scan at boot time when clearly the profile disk is no longer going to be attached!
Fixing it I'd expect is a case of mounting the VHDX file manually (i.e. not via an FSLogix login when the drive needs to be in use) and then running chkdsk in such a way to disconnect any active handles chkdsk /x or chkdisk /offlinescanandfix or powershell Repair-Volume although my issue up to now has been actually tracking down the correct user on a 16 core multi-user session host servicing about 20-25 users to know which VHDX to be (first backing up) and then manually mounting and scanning!
Fixing it I'd expect is a case of mounting the VHDX file manually (i.e. not via an FSLogix login when the drive needs to be in use) and then running chkdsk in such a way to disconnect any active handles chkdsk /x or chkdisk /offlinescanandfix or powershell Repair-Volume although my issue up to now has been actually tracking down the correct user on a 16 core multi-user session host servicing about 20-25 users to know which VHDX to be (first backing up) and then manually mounting and scanning!
Have you been able to get more information on the issue?
We have been dealing with the same problem on just one of our customers host pool.
We can match the timestamp of the error to a FSLogix user logging in to the AVD. However: every occurance of the error, it's caused by a random user. It's not limited to one specific user profile.
We have been dealing with the same problem on just one of our customers host pool.
We can match the timestamp of the error to a FSLogix user logging in to the AVD. However: every occurance of the error, it's caused by a random user. It's not limited to one specific user profile.