chkdsk
, sfc /scannow
, safe mode with networking, and probably some more), but none of these resolved the issue.
Introduction to Malware Binary Triage (IMBT) Course
Looking to level up your skills? Get 10% off using coupon code: MWNEWS10 for any flavor.
Enroll Now and Save 10%: Coupon Code MWNEWS10
Note: Affiliate link – your enrollment helps support this platform at no extra cost to you.
tldr: Delete or rename C:\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini
after removing the system encryption.
A few more words about this:
There’s a file C:\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini
(documentation) which VeraCrypt creates when encrypting the system partition, with the following content (for me at least):
[SetupConfig]
ReflectDrivers="C:\Program Files\VeraCrypt"
PostOOBE=C:\ProgramData\VeraCrypt\SetupComplete.cmd
After removing system encryption, the file only contains
[SetupConfig]
but still exists.
Removing or renaming this file allowed me to upgrade and re-enable system encryption without further problems. I’ve tried it on another (desktop) machine to verify - ran into the exact same problem, which went away after removing that file.
Edit: I’ve opened a bug report at VeraCrypt’s repo.
Article Link: Upgrading to Windows 11 with (pre)existing VeraCrypt system encryption – nullteilerfrei