![]() What I do - and kudos goes to Terabyte Unlimited for this info (makers of BootitNG and Bootit BareMetal ) - is to make 4 primary partitions on my primary drive. I've learned that, if allowed, Windows will put boot info on the first partition, even if you're installing Windows on,say, a third partition. If I'm uncertain about what it shows me, I'll boot Win 10 in Safe Mode with Command Prompt and use the bcdedit command passively to see what it says about the BCD. Instead I'm first going to boot Win 10 normally and install EasyBCD, then see what it shows about the BCD store. That tool easily allows me to move the existing Windows 10 partition down a bit (32 MB), after which I'll create a new FAT32 partition there.īut I don't plan to install BIBM there immediately. My plan now is to boot up Acronis Disk Director 12.5 from a flash drive. The BCD store was indeed created where Kasual expected: C:\Windows\BootĪs I promised, I haven't installed BIBM yet. There was only one no separate boot partition. When I booted up (successfully), I used Disk Management to take a look at all partitions on the target. Then I installed Win 10 1809, which worked perfectly. Here's where I am: I first deleted all partitions on the target SSD drive, and left the entire drive unformatted. In that case, what are your thoughts about me copying the BCD store from /Windows to /Boot so that BIBM can locate in the expected location? Of course, I'd need to know the correct paths of the BCD. In that case, I'll install BIBM in some OTHER partition to avoid clobbering the boot partition.Īnd if there is no boot partition, the BCD store will be located in \Windows. So I'm now going to try it from scratch again, but this time, after the installation and reboot, I'll go into Disk Management and look for a boot partition, which if it exists will probably be located in that first 32 MB partition. That is extremely valuable information, Kasual! Wow - Thanks! So if I understand you correctly, either (1): the Win 10 installation built the boot partition into that 32 MB FAT32 space and I unintentionally destroyed it when I installed BIBM in that space, -OR- (2): the BCD store was created in \Windows, which isn't where BIBM was expecting to find it. The entirety of the rest of the available space, 111 GB, is formatted as NTFS but otherwise empty. I create two partitions total on the target drive: The first is a blank 32 MB FAT32 partition which will eventually hold BIBM. I guess I must not have built the BCD correctly, which is why I'm asking why my installs aren't creating one for me. I've tried creating a fresh BCD store using the BCDEdit and the related commands, but when I then reboot, I get "NTLDR is missing" or No Operating System found. But every time I try this with Win 10 1809, BIBM reports that No BCD Store exists, so I can't continue. ![]() Every previous time, including when I installed previous versions of Windows 10, BIBM loads and then I ensure that the BCD store has all the correct parameters. ![]() Then I reboot and install Bare Metal and reboot again. What I do is install the OS completely and make sure it boots properly. To accomplish that, I've been using TeraByte's BootIt Bare Metal (BIBM), a product I'm a huge fan of and have been using for decades. I should add that all my systems can multi-boot into either Win 7 or Win 10, and I want this system to do that also. I will do that next time, but at the moment that system will not boot.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |