Windows 10: Boot manager problem - failure to boot - bcdedit error

The machine is MSI Titan GT80 SLI running Windows 10 1903.

It has 4 SSD disks, two PCIe and 2 SATA. I am only concerned about the PCIe SSD (2280 format). Here is the layout, it's disk 0 and disk 1 that are relevant.





Disk 0 boots just fine.
I cloned the disk 0 to disk 1 using Macrium reflect. Then I created the BCDboot entry to create a multiboot operating system. It looks like this. Here is a view through EasyBCD:





and here is the output of bcdedit:




Windows Boot Manager
--------------------
identifier {bootmgr}
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {34222f3b-2d98-11e9-9e5a-d8cb8aefea8e}
displayorder {d1256220-1323-11e9-8b85-806e6f6e6963}
{bbb9cb4e-6dfd-11e9-9eee-806e6f6e6963}
{bbb9cb4f-6dfd-11e9-9eee-806e6f6e6963}
{bf1f5d80-a0fd-11e9-8b69-806e6f6e6963}
{ef173654-a0f6-11e9-8b6b-806e6f6e6963}
{d1df20ef-1342-11e9-a142-995979db796d}
{current}
{34222f43-2d98-11e9-9e5a-d8cb8aefea8e}
{34222f46-2d98-11e9-9e5a-d8cb8aefea8e}
toolsdisplayorder {memdiag}
timeout 9
displaybootmenu Yes

Firmware Application (101fffff)
-------------------------------
identifier {d1df20ef-1342-11e9-a142-995979db796d}
description Fedora
custom:250000c2 0

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale en-US
inherit {bootloadersettings}
recoverysequence {34222f3e-2d98-11e9-9e5a-d8cb8aefea8e}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {34222f3b-2d98-11e9-9e5a-d8cb8aefea8e}
nx OptIn
bootmenupolicy Standard

Windows Boot Loader
-------------------
identifier {34222f43-2d98-11e9-9e5a-d8cb8aefea8e}
device partition=L:
path \Windows\system32\winload.efi
description Windows 10 -- 860 M.2
locale en-US
osdevice partition=L:
systemroot \Windows
resumeobject {edea4af9-af54-11e9-9f32-806e6f6e6963}

Windows Boot Loader
-------------------
identifier {34222f46-2d98-11e9-9e5a-d8cb8aefea8e}
device partition=G:
path \Windows\system32\winload.efi
description Windows G:
locale en-US
osdevice partition=G:
systemroot \Windows


After I did the clone, it stopped booting completely. Not even the primary drive is seen. Seems there is a conflict between two drives somehow. I went into BIOS and none of the 4 disks were seen. Furthermore when I hit F11, I could not even boot off the flash drive with Gparted to edit the partitions.

When I removed the primary disk, I could boot into the cloned disk just fine, it's just that they don't work together. I did have to go into BIOS and adjust this. When I get a boot failure with 2 disks installed at the same time, I don't even see the option for Boot Option 1.. et cetera. When I remove either the primary or the clone disk, I get that option back and when I correct add Boot Option 1 pointing to the Samsung MZVxxxx, it boots correctly.






So with 2 disks installed, I don't even see this:





But this is the real question, why do I see this debian entry? I had previously used the disk for Debian install but since reused the disk for Windows clone and it should have retained none of the Linux stuff. The grub bootloader is still on the disk, or is that a conflict in NVRAM, grub is conflicting with bcdedit stuff?

Disk 0 and Disk 1 are identical NVMe/PCIe disks with identical data on them but it can only boot off one if I nuke the EFI System Partition on the other disk, the 100MB sector. Then it boots. I re-run the Macrium Reflect clone/image process several times, copying *all* of the partitions, and always end up with the same result. I even formatted the disk and re-cloned it off primary, same result.
I cannot multi-boot anymore, and the other disk is just a disk that can be used for data and nothing else. They both boot, just not together.
How do I delete the Linux bootloader entry and where is it located?

It used to multi-boot in that exact BCDEDIT configuration with these exact disks until I got Linux involved.

:)

 

Windows boot manager

There could be some system conflict triggered after the said changes. To help you with your concern, we suggest that you perform a clean boot. A
clean boot is performed to start Windows by using a minimal set of drivers and startup programs. This will help to determine what is causing the issue on the Windows boot manager. To do this, click on this
link and scroll down to the
How to determine what is causing the problem by performing a clean boot section then follow the steps listed..

Note: If the installation is successful and the issue has been resolved. Please go through the section “How to reset the computer to start as usual” to reset your computer to the normal startup.

Let us know how it goes after performing the suggested steps.

 

Failures to boot, error 0x80070003

These problems began after my computer fell off my desk, so it is likely a hardware issue, however I would like to determine if this is indeed the case, and if so which components need to be replaced.

I've recently been having problems with my PC failing to boot. It freezes on the Windows 10 logo upon start up, before crashing to a black screen. Occasionally, windows will successfully enter system recovery, but fails to repair the problem. Attempting
system restore from restore point results in an "unspecified error, 0x80070003". I will occasionally (perhaps 1 in 20 times) be able to load fully into Windows with no issues- once logged in typically I experience no problems. It seems random when this happens
and I am unable to reproduce it regularly.

Steps already taken:

1. Windows system restore, failed with error 0x80070003
2. Deployment Image Servicing and Management tool ran, no corruptions found
3. System File Checker tool, no integrity violations found

Any advice or suggestions is much appreciated, thank you.

UPDATE:

I checked the log file created by windows automatic repair upon failure with error 0x80070003: C:\Windows\System32\LogFiles\Srt\SrtTrace

This file showed a number of successful tests, up to this:

Code:

Test Performed: ---------------------------Name: System boot log diagnosisResult: Completed successfully. Error code =  0x0Time taken = 0 msRoot cause found: ---------------------------Boot critical file e:\boot\resources\custom\bootres.dll is corrupt.Repair action: File repairResult: Failed. Error code =  0x2Time taken = 1500 ms---------------------------

This seems likely to be the root cause. How should I go about repairing this file?

 

Boot problem

Hi Brandon,

Windows boot up problem can be caused by boot sequence and hardware issues.

For us to properly assist you, please answer the following questions:

• To avoid performing the same troubleshooting steps, can you tell us the troubleshooting steps that you've tried performing to resolve Windows 10 boot up problems?
• Any error messages when booting your PC from the recovery drive?
• Have you made any hardware or software changes on your device prior to the issue?

We'll keep an eye out for your response.