veracrypt
1.25.9 bricks system when microsoft ransomware protection triggered
After 7 hours of investigating, I can tell that, on new Windows 10 x64 (Rufus windows on the go, but it should not matter) if microsoft ransomware protection is enabled, it will block VeraCrypt from writing rescue disk to Documents. Just change the path and press next. But then when the Test run is proposed, VeraCrypt experience more errors and can't proceed. Does not have access to Harddrive0/Volume1/DR0/ (to read the bootmgr etc).
If after seeing this error popup the user will go to windows settings to whitelist bocked veracrypt format.exe, without closing the last step veracrypt window, and then choose to proceed with the test, it will indeed reboot, allow to enter password and pim, and even correctly determine it was authorized... But then PC hangs.
Looks like the ransomware magic above made VC think something was already done, but it wasn't. For example I think I see in "bad, broken" EFI/Microsoft/Boot folder just one small file bootmgfw.efi, while in "good" EFI/Microsoft/Boot folder I can also see a new big file bootmgfw_ms.vc. It is missing after the ransomware bug.
On the user side, after VC wizard got error and user has whitelisted it, we must close the wizard and start all over. Then there will be no bug.
