Edited: Some of below isn’t true anymore, as explained in my second post.
I’ll try and be right to the point, but I know details are needed.
I successfully created a dual-boot situation a couple months ago on a small HP laptop to test switching to Linux from Windows in order to do it “for real” on my wife’s HP Envy. I used GParted before to remove the Windows partitions and all went well on the test laptop. Today was the “for real” day on the Envy. And I had a problem that I’ve been able to temporarily fix, and am stepping back to get a bigger picture and to get advice. What happened…
After confirming all files were now on the Linux side, and doing successful Timeshift and LuckyBackup sessions to an external drive, I rebooted on the Linux USB to use GParted to remove Windows. I deleted the Windows ntfs partition, plus I saw the Windows Recovery partition which I deleted as well since we’re leaving Windows, plus one more “unassigned” (I think) partition as well. When done, all that was left was the EFI partition at 200MiB, the partition with Linux now at 931GB, and a “unassigned” partition at 3.71Mb (going by memory on that number). The video I used to successfully do this on the test laptop before had a similar final result of those three partitions, and no “Windows Recovery” partition, so I thought all was set.
Rebooting to see the results, a blue screen came up with “Your device needs repairs” in Microsoft-looking messages. The error code of 0xc0000225 indicated that the Boot Configuration Data was the problem. Oh dear. The video I used for GParted said, “never ever delete the EFI partition or you won’t be able to boot up”, so I thought since I had followed instruction, plus did this before that I’d be all set. No.
So, following this link: 0xc0000225 Error Code on Windows 10 [Fixed] - Driver Easy, and other advice on the LinuxMint forums, I determined I had to create a Windows Boot USB. Thankfully my daughter is still on Windows or, yeah (I’m on a Mac, yet). Once I got the Windows 10 USB created, I loaded it in the Envy and rebooted.
F9, and chose the USB drive from the boot manager that did show up now. I ran steps from the above mentioned site and ran the four terminal actions regarding rebuilding the boot configuration problem:
bootrec/ scanos - seemed okay
bootrec /fixmbr - said it was done successfully though I don’t know what that meant
bootrec /fixboot - said Access denied. Hmm…
bootrec /rebuildbcd - had no message after being done.
I decided to shut down from the options and went to reboot from the USB again with F9.
I noted that this Boot Manager screen I had used did not look like the boot manager I saw on the Linux USB, so I’m assuming this is a local boot manager on the USB.
I noticed (did I miss it before? I don’t know) but there was the Ubuntu option! I chose it and Linux came up and ran like normal. It showed me that the Linux partition was fine and I launched apps and all that with no problem. So my wife has been able to get on her computer for the moment and do normal stuff, but the problem is temporary. That USB slot is for the backup hard drive for the backups, and the other slot is for the mouse/keyboard wireless signals.
So the question is: is there a way to get the Boot Configuration Data back on the hard drive again? I had gone into GParted on the USB Linux boot and changed the Linux partition down to 650GB-ish, and created a new 250GB-ish ntfs partition (leaving an 100GB-ish open area on the drive for another partition) thinking that I might have to re-install Windows to “fix this” but I’m not sure.
That’s where my question comes in now that I have explained the situation. The Envy seemed to need a Windows thing in order to operate at all based on the error I first got when I rebooted. Having Windows 10 on a USB drive made it possible to see something again. What are my options to get this fixed? That’s where I’m at. We wanted to be 100% free of Windows, but at the moment, we still aren’t.