I have a Lenovo Ideapad 510 with Windows 10. I was mounted to a volume on a network drive when my computer crashed, it rebooted and I tried to mount it again and this dialogue box popped up:
WARNING: The host file/device is already in use!
Ignoring this can cause undesired results including system instability.
All applications that might be using the host file/device (for example, antivirus or backup applications) should be closed before mounting the volume.
Continue mounting?
I believe I am now unable to mount because it did not dismount properly when it crashed.
I have tried a full PC reboot as I understand Widnows 10 fastboots.
I've also tried disabling Windows Defender.
I am only able to locate the volume when I'm logged in as I said it's on a network drive, so locating the drive via disk mgmt is out of the question because it's not local.
I can still access the network drive and my other volumes on VeraCrypt, but not this one that was open when my notebook crashed.
The last time I backed the volume up was 2 months ago and I'm afraid I've lost the last 2 months of work - lesson learned.
Is anybody able to help me please?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
By 'network drive', do you mean a network attached storage (NAS) device? If so, this occasionally happens to me; restarting the NAS always solves the problem, and everything works normally thereafter, with no data loss. Note that I always format my VC volumes with NTFS, which may be relevant; it's the most robust filesystem, and I always get away unscathed from incidents like this, and eg pulling out USB sticks before unmounting the volumes thereon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a Lenovo Ideapad 510 with Windows 10. I was mounted to a volume on a network drive when my computer crashed, it rebooted and I tried to mount it again and this dialogue box popped up:
WARNING: The host file/device is already in use!
Ignoring this can cause undesired results including system instability.
All applications that might be using the host file/device (for example, antivirus or backup applications) should be closed before mounting the volume.
Continue mounting?
I believe I am now unable to mount because it did not dismount properly when it crashed.
I have tried a full PC reboot as I understand Widnows 10 fastboots.
I've also tried disabling Windows Defender.
I am only able to locate the volume when I'm logged in as I said it's on a network drive, so locating the drive via disk mgmt is out of the question because it's not local.
I can still access the network drive and my other volumes on VeraCrypt, but not this one that was open when my notebook crashed.
The last time I backed the volume up was 2 months ago and I'm afraid I've lost the last 2 months of work - lesson learned.
Is anybody able to help me please?
By 'network drive', do you mean a network attached storage (NAS) device? If so, this occasionally happens to me; restarting the NAS always solves the problem, and everything works normally thereafter, with no data loss. Note that I always format my VC volumes with NTFS, which may be relevant; it's the most robust filesystem, and I always get away unscathed from incidents like this, and eg pulling out USB sticks before unmounting the volumes thereon.