petitlou60 - 2019-06-22

Hello Mounir,
When system is encrypted windows command reagentc fail , logs show it is unable to find GUID of disk
After decrypting system and reboot this bug remains.
you need to :
1) uninstall veracrypt
2) reboot
3) re install veracrypt
4) then reagentc is good

When system is not encrypted

1) with no volumes mounted reagentc is good
2) with any volume mounted reagentc failed
so this is a problem of veracrypt driver

other bugs
1) in \EFI\boot bootx64.efi is very old copy of bootmgfw.efi from first encrypting time after decrypt
2) in \EFI\Microsoft\Boot, windows update bring frequently a new copy of bootmgfw.efi and bootmgfw_ms.vc ** remain old copy but is executed to start windows boot** may be with risk of incompatibility.

in short:

rename of bootmgfw.efi is never safe
for me the only quasy absolute solution is:

1) in EFI put VeraCrypt directory inside Microsoft one ,so no veracrypt boot menu is build
2) in BCD start bcdedit /set {bootmgr} path \EFI\Microsoft\VeraCrypt\dcsboot.efi
3) when dcsboot.efi has finished start \EFI\Microsoft\Boot\bootmgfw.efi
4) in \EFI\Boot put as bootx64.efi a copy of dcsboot.efi

so the only case not handled is bcdedit /rebuild started from windows update
to restart you need to boot with veracrypt usb key then command m and v

Best regards

 

Last edit: petitlou60 2019-06-26