Looking for help unborking a W10 install w/bootloader issues

Lordhumungus

Golden Member
Jan 14, 2007
1,207
33
91
Ok, so coming to you guys again as I cannot wrap my head around what is going on with the Windows 10 Enterprise install I have on my new Ryzen APU machine.

This all started when I created a bootable USB installer and began the install process as usual, but when I tried to select my NVMe drive to install to I got the error "Setup was unable to create a new system partition or locate an existing system partition", preventing my from doing the install.

I've not run into this before, but the info I found points to this is being common error (but not why, or explicitly how to fix it) and that the best course of action is to create a small partition on the drive and copy the install files over from the USB drive. Specifically, I followed everything in this video to a T and it worked PERFECTLY. Great right? Not so much...

So now I have a 5000MB partition on my HDD that I cannot use, so I go and remove it, thinking I that I can just then extend my C: partition to fill the drive. What I did not realize is that apparently Windows put the bootloader info on the 5000MB partition, so when I nuked it, bye-bye being able to boot into Windows.

After a bunch of screwing around with EaseUS Partition Master and Windows in-built recovery utilities l am still not any further than when I started (and in fact I am assuming I have gotten it into a state where trying to recover this install may not even be possible).

I don't really mind re-installing Windows again as I've already done it like 20 times to get this machine working, but I don't see how I can avoid starting back at having an unusable partition of 5000MB on my drive.

So ultimately I'm happy to either make the existing install bootable again or start fresh, but I'd like to figure out how to not have unusable space on my drive.

Also, there are clearly a few concepts in this process that I am either misinterpreting or not understanding, so the more info I can get to turn this into a learning experience on how to deal with this in the future, that would be awesome!

Thanks in advance for any help!
 

Lordhumungus

Golden Member
Jan 14, 2007
1,207
33
91
Looks like I might have solved the initial problem by setting storage to UEFI only on the BIOS instead of Legacy.
 

Lordhumungus

Golden Member
Jan 14, 2007
1,207
33
91
Yeah, I had no idea that was even a setting until I went looking for something else. Seems weird that none of the solutions I saw mentioned that and instead recommend the posted work around. Oh well, any day you can learn something new is a good day!