I was running windows 10 v1607 on an encrypted external hard drive, and mistakenly unplugged it while it was running, and Windows still continued to run, amazingly. I'm surprised that Veracrypt didn't dismount the running system. but everything seemed to work afterwards. It was running veracrypt 1.22.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
and then I wrote a file from 1607 to 1903, from veracrypt 1.22 to 1.24 update 4, and while it was still transferring, I ran chkdsk on my 1903 drive which I had to mount using Veracrypt 1.22, and chkdsk dismounted the drive while it was still transferring, did a check, and so the two files I transferred from veracrypt 1.22 drive to 1.24 U4 drive did not write correctly, and had to run chkdsk from 1607 and also on the 1903 computer, and now the computer will boot, but it's basically stuck on the acer logo screen, 6 or 7 dots going in a circle, and then the hard drive shuts down after a while / or at least I don't hear any data being written to it, and then when I press a button to turn the screen on again, then I hear the hard drive spinning up. what a mess. I don't know if it's because I was using chkdsk on a veracrypt 1.22 system or if it's because it's a 1607 windows system, or what the deal is.
but I figure that if someone can pull out the usb cable to the running system drive, then put some sort of hard ware device to read all the data going to and fro, they could get the password. but I see that it's already being done with elcomsoft's software
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was running windows 10 v1607 on an encrypted external hard drive, and mistakenly unplugged it while it was running, and Windows still continued to run, amazingly. I'm surprised that Veracrypt didn't dismount the running system. but everything seemed to work afterwards. It was running veracrypt 1.22.
and then I wrote a file from 1607 to 1903, from veracrypt 1.22 to 1.24 update 4, and while it was still transferring, I ran chkdsk on my 1903 drive which I had to mount using Veracrypt 1.22, and chkdsk dismounted the drive while it was still transferring, did a check, and so the two files I transferred from veracrypt 1.22 drive to 1.24 U4 drive did not write correctly, and had to run chkdsk from 1607 and also on the 1903 computer, and now the computer will boot, but it's basically stuck on the acer logo screen, 6 or 7 dots going in a circle, and then the hard drive shuts down after a while / or at least I don't hear any data being written to it, and then when I press a button to turn the screen on again, then I hear the hard drive spinning up. what a mess. I don't know if it's because I was using chkdsk on a veracrypt 1.22 system or if it's because it's a 1607 windows system, or what the deal is.
but I figure that if someone can pull out the usb cable to the running system drive, then put some sort of hard ware device to read all the data going to and fro, they could get the password. but I see that it's already being done with elcomsoft's software