Recovering a VeraCrypt system drive with a questionable/damaged bootloader without a VeraCrypt recovery disk

[snotrag]

Recovering a VeraCrypt system drive with a questionable/damaged bootloader without a VeraCrypt recovery disk

Due to actions outside of VeraCrypt, I was suggested to run commands to initialize the boot area of a VeraCrypt system drive.

Normally, I'd get a:
-BIOS Screen
-VeraCrypt authentication request
-Windows loading logo

Unfortunately, after triggering a few 'bootrec' commands, I no longer receive a request for VeraCrypt authentication and my system understandably never boots into Windows.

I don't have a VeraCrypt recovery disk, and if I mount the primary system disk onto another system with VeraCrypt, I am unable to decrypt the contents of my target disk, even though I know the password.

-Select volume
-Select the data volume of the primary disk
-Volume Tools -> Permanently Decrypt -> (Follow the wizard)

Browsing around, it doesn't look like the above scenario is supported.

Is there a supported direction to use to recover my environment?

[John Deener]

Here's what I would try. I have mounted system disks before in a different system. I'm not sure if you can decrypt but you can mount and then copy off the files. Try going to "system">"mount without pre-boot authenication". Might want to try under "system">"permantly decrypt system/Partition drive"

I had a windows system drive that once had the first part overwritten by a Linux distro that installed to the wrong drive. Took me forever to get it back. I had to mount the encrypted drive. Write back the backed up files. Reinstall windows boot. Then reinstall the veracrypt boot. It was a night mare...but it worked.

Hope it works for you.