Hi, Brian - Good news: I can once again boot into the main new Win 10 1809 system on the Samsung SSD, and it is first in the boot order. But I haven't installed BIBM on that drive yet. I'll explain what I did to get it working again in my response below...
Brian K wrote:
> Ambertus wrote:
> > Yes, I always enable the Swap option for every bootable
> > partition on all disks.
> Are you sure? Swap should not be enabled on the HD containing BIBM.
WOW! That is extremely critical information that I, in my ignorance, simply did not know until right now!
But, yes, I had Swap enabled on all storage devices containing BIBM. A key Pilot Error on my part. Thanks!
> > I suspect that the most relevant and crucial aspect of this whole nightmare
> > is that BIBM doesn't appear to handle non-UEFI Win 10, or at least
> > release1809, installations completely correctly, where the BCD store is NOT
> > located in C:\Boot\BCD but somewhere else.
> I have a fresh Win10 1809 installation on a MBR disk and the BCD store is in C:\Boot.
> >, and I've
> > confirmed that not a single one of them has a BCD in the Boot folder of
> > their root folders. NOT A ONE!
> I have two MBR 1809 installations and they are both fine. What are we doing
> differently? You aren't installing Win10 1809 by this method...
No, I didn't do it that way, and I don't think I ever have. What I INTENDED to do back in mid-November was what I eventually did later. My plan was to disconnect ALL storage devices except the Samsung SSD and the Win 10 1809 installation flash drive and then use the second Windows 10 installation option to install Win 10 from total scratch. But because the second SSD (the Crucial) is installed within the computer case and can't be seen unless you remove a side panel, I inadvertently left it connected during that initial install. I don't recall the boot order in the BIOS at that time, but as I wrote earlier, for whatever reason, the Windows installer decided to store at least some of the necessary boot files somewhere on the Crucial SSD. Which is why I could ONLY boot correctly into the new Win 10 on the Samsung IF and ONLY IF the Crucial SSD came first in the boot order, followed by the Samsung SSD.
More recently, I began a new install from scratch after properly disconnecting ALL storage devices except for a single, unformatted 500 GB standard hard drive (and of course the installation flash drive). There were NO SSDs connected at all. This succeeded and booted correctly every time. BUT when I examined the drive with a partition manager later, I discovered an EXTREMELY important fact: Although as Ive reported several times now that there was NO C:\Boot folder created (and hence the BCD had to be somewhere else), the new correctly booting disk has a hidden NTFS partition at the start of the drive labeled "System Reserved" and THERE was the \Boot folder AND the BCD store was created within!! BINGO!
So this is what I did that allowed me to boot Win 10 1809 on the Samsung SSD again:
(1) Use a partition manager to reduce the size of the Samsung's Win 10 system partition by about 516 MB.
(2) Used DD 12.5 to move the Win 10 partition further down the drive to place the 516 MB unallocated space at the front of the Samsung SSD.
(3) Used DD 12.5 to copy the 500 MB "System Reserved" partition from the start of the 500 GB hard drive to the start of the Samsung SSD (leaving 16 MB for possible eventual use to contain BIBM).
(4) Booted up an old Win 7 system partition on a backup disk from another ASUS Z87-A computer.
(5) Used EasyBCD v2.4 to examine the BCD Store on the newly copied "System Reserved" partition
(6) Edited that BCD to correct the boot drive and so forth to boot from the Win 10 partition.
(7) Disconnected the 500 GB hard drive from the system, set the Samsung SSD first in the BIOS boot order, and booted up.
(8) Sigh: Failure - No Operating System Found again!
(9) Purchase and download the Home edition of Easy Recovery Essentials for Windows 10, wrote it to a spare flash drive, and booted into it.
(10) I chose the Automatic Repair option, let it finish, and tried to boot into the Samsung SSD Win 10 system.
(11) Success!! Finally!!
I have not installed BIBM on the Samsung SSD, and I'm not going to keep pressing my luck by trying again for a while, that's for sure! I've got far too much stuff to do until after Christmas.
However, for the hell of it, I cloned the Samsung SSD onto a spare hard drive, complete with "System Reserved" partition, 16 MB of unallocated space for BIBM, and the remainder of that SSD, the Win 10 system partition. Then I put it first in the boot order, booted into the BIBM v1.52 installation flash drive, installed BIBM into that 16 MB space, and rebooted (with the cloned hard drive first in the BIOS boot order).
Once into BIBM, I entered into Partition Work, and selected the "System Reserved" partition, and pressed the BCD Edit button. It once again proclaimed that there was NO BCD Store. So I selected the Win 10 system partition and pressed the BCD Edit button again. And once more: NO BCD STORE!!
Ah, well. When II get the chance, I'll try disabling the Swap option and see what happens. But not until after Christmas!
So put this thread aside until I post a new response after Xmas, and Enjoy your Holidays, kind and respected Brian K!