Mark Goldey

I finally gave up and wiped the machine. Reinstalled Windows. Haven't reinstalled VC yet.

More: Windows repair keeps placing a Windows boot loader into the boot sequence, but the loader is actually VeraCrypt's boot loader. Even if I delete all Windows boot loaders via UEFI BIOS, and then boot into a Windows Rescue Disc, and select "Continue to Windows 10" I wind up at VC's password prompt. The BIOS then shows a new WIndows Boot Manager as the first boot device. Pretty clearly, that Windows Boot Manager is actually Veracrypt. Mislabeled? Maybe intentionally because it was installed in...

Thank you for the advice! Unfortunately, the "z" option to remove VC from the boot menu does nothing, except return to the VC rescue prompt, as if VC was not loaded. I even removed the VC boot loader from the UEFI menu. When I reboot, I see the VC password prompt, which accepts my password and drops me at the Surface welcome screen. Bizzare.

Folks: Looking for advice on how best to completely remove Veracrypt from the boot menu and restore the Windows boot loader on a partly-unstable Windows 10 Surface system. The core problem was: using Veracrypt 1.18 and Windows 10 would not do quarterly updates. I upgraded VeraCrypt to 1.24u6 (current version) and rebooted, at which point the PC hung at Veracrypt's "Authorizing . . . Start 0" message, which appears on the Surface's unlocked boot loader screen (red bar across the top, black background)....

MJ: Thanks for the explanation. Turns out that my problem was a missing GUACAMOLE_HOME....

MJ: Thanks for the explanation. Here's what I can offer re: messages: From /var/log/syslog,...

I think I can shed some light to this. I was using 0.8.x in Debian Wheezy without...