Open intently opened 3 years ago
I am also dealing with the same issue. I haven't been able to figure out what to do. Did you ever come up with a solution?
Yeah, it was related to UEFI. The problem was resolved when I removed my SSD and re-installed it.
On Fri, Sep 10, 2021 at 12:26 PM Erin Giglio @.***> wrote:
I am also dealing with the same issue. I haven't been able to figure out what to do. Did you ever come up with a solution?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/veracrypt/VeraCrypt/issues/810#issuecomment-917080326, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJRERTGGMVCSHRILEFNNPDUBI5U7ANCNFSM5BALZONQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Rats--I'm getting this error on the whole machine. Did you just physically remove the drive and reinstall it? I'm not great at UEFI and BIOS issues generally, and absolutely wouldn't have installed VeraCrypt if I had realized that Windows 10 updating automatically could brick my machine likethis!
Yes, physically remove the SSD and replace it, then let your BIOS detect it again. Then try booting from the veracrypt boot sector (or w/e it's called) on the ssd
On Wed, Sep 15, 2021 at 1:21 PM Erin Giglio @.***> wrote:
Rats--I'm getting this error on the whole machine. Did you just physically remove the drive and reinstall it? I'm not great at UEFI and BIOS issues generally, and absolutely wouldn't have installed VeraCrypt if I had realized that Windows 10 updating automatically could brick my machine likethis!
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/veracrypt/VeraCrypt/issues/810#issuecomment-920267893, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJRERT5VMKQ2FY4KT3D64LUCDPZDANCNFSM5BALZONQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Edit: everything made with 1.25.9 I had this same issue, something went wrong with my computer and it wouldn't boot any more - the bootloader wouldn't even load. I tried every option on the backup disk and most said "not ready" ("Decrypt OS" did something, completing after a few hours, but it still would not boot after). Nothing worked, including the recommendations in this thread. I eventually had to restore a months-old backup from before I encrypted my drive with veracrypt. I did everything right: I read the manual and wizard instructions thoroughly, I made and verified the backup disk, I backed up a system image daily, I backed up my user files 3 times a day. My trust in this project has been trampled.
Windows updated and changed my bootloader. This has happened before and I've been able to restore it from the rescue disk. However, this time it doesn't seem to be working. I only get a yellow "not ready" message when I attempt to "restore veracrypt loader to boot menu".
I'm also not able to "boot veracrypt loader from rescue disk".
Almost every option says "not ready".
Googling hasn't helped.
1.24-Update2 rescue disk
Help?