veracrypt
Issues with Windows USB energy saving (it ignores/fails to detect VC volume in use)
Expected behavior
When a drive is used, USB energy is not cut off and the volume is dismounted
Observed behavior
After some time of continuous write, veracrypt-hosting usb hdd is disconnected (and therefore dismounted) and the copy fails. It may only happen with locked OS. Sometimes it was after less than 20 Minutes, sometimes it took more than 40 minutes.
Steps to reproduce
- Have energy management for usb devices turned on in windows. Afair its default.
- copy a large file from a bitlocker usb-hdd to a veracrypt usb-hdd
- (maybe required: lock screen)
- wait
Your Environment
Windows 10, VC 1.26.24, 64 bit, 2,5" usb hdds (powered via USB)
I tested 3 usb drives, 2 cables and 2 usb ports (cables and ports all combinations). Bitlocker (source) drive was never affected, but veracrypt one was several times. After disabling usb device energy management in windows energy settings, it immediately worked for several hours without issues.
So I assume that windows can detect the hdd corresponding to a bitlocker drive (and its activity and hence not cut usb power off) but not the hdd corresponding to a veracrypt drive and tehrefore it cuts of the usb port if energy saving for usb is enabled.
I am nut sure whether this can be fixed by VC or only on the windows side, but definitely it is a bug.
That's a long living bug: https://github.com/veracrypt/VeraCrypt/issues/1443
It is not the same issue:
- 1443 is a container, this is a partition
- 1443 does fail to dismount, even if requested, this does dismount automatically,
- 1443 is a 3,5" usb drive case which means it is powered externaly, not via USB, like the external hdds I used
- 1443 is an issue with waking up after sleeping, this is short-term disconnect
BUT I suggest you try to disable energy saving for USB and test your AgeStar 3U2B3A and check whether this solves your issue.
BUT I suggest you try to disable energy saving for USB and test your AgeStar 3U2B3A and check whether this solves your issue.
These issues some how related to the USB connection, not just to a particular device. Because the issue is catched on other devices attached to the USB.