Cloned disk unable to boot

Pentagon said:

Why don't you check the disk 1 BCD for missing entries?
Whith a "Recovery Environment" it would have been very easy to check the bootability of the disk!
You did not read the Megahertz instruction carefully.

Yes, I followed Megahertz' cmd instructions to the letter, and I reported back precisely. There's no Recovery Environment because the source disk 0 has no Recovery partition.

- - - Updated - - -

Volume Z said:

In your image partition 2 is selected, so no volume is selected as diskpart does not consider Reserved a volume.

Skip the list stuff and enter

select disk 1

select partition 1

as we know which disk to address and which partition as well.

Ok, so just to make sure before proceeding, these should be the steps in cmd right? Also, I see the letter w then shown as W, should I use w in all steps, or W? (I guess makes no difference)

diskpart
select disk 1
select part 1
format fs=fat32 quick label=EFI
set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b
assign letter=w
exit
bcdboot D:\Windows /s W: /f UEFI
diskpart
select vol W
remove letter=W
exit
exit

That is correct.

Volume Z said:

You shouldn't have selected partition 2, but partition 1.

Is this ok now?

diskpart
select disk 1
select part 1
format fs=fat32 quick label=EFI
set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b
assign letter=w
exit
bcdboot D:\Windows /s W: /f UEFI
diskpart
select vol W
remove letter=W
exit
exit

Yes.

Volume Z said:

Yes.

ok, will test now and report back, thanks

- - - Updated - - -

Ok, here are the results, as you can see in the first screenshot all commands executed with success, but after cmd was successful, Disk Management still shows Disk 1 (target) without the Boot, Page File and Crash Dump components in the OS D drive. Should I still test if Windows will boot from the target or it will fail?

This wasn't an issue to begin with as Boot, Page File and Crash Dump are tags of the powered-on machine. There is never more than one "Boot", "Crash Dump" and mostly "Page File" per Disk Management shot as only one Windows is running.

Just change the disks now as startup of Disk 1 should be fixed.

Volume Z said:

This wasn't an issue to begin with as Boot, Page File and Crash Dump are tags of the powered-on machine. There is never more than one "Boot", "Crash Dump" and mostly "Page File" per Disk Management shot as only one Windows is running.

Just change the disks now as startup of Disk 1 should be fixed.

Great, will physically replace then the source disk with the target and see if Windows boots now. Fingers crossed. Will report back, thanks.

- - - Updated - - -

Unfortunately Windows is still unable to boot, identical symptoms as reported before the cmd boot sector fix. BIOS is detecting the drive and settings are fine AFAIK. Maybe the EFI boot manager needs further repair with additional cmd commands? I'm attaching screenshots of BIOS with target drive installed. Second screenshot is after I click "Add Boot Option", but I think it's not relevant, the one shown in BIOS by default is the Boot Manager:

Berton said:

A default install on my WIn10 Pro:

Yes, my install lacks the Recovery Partition but that shouldn't be a reason for the disk clone not to be able to boot into Windows

Please run:

V2 log collector > post a share link

BSOD - Posting Instructions


Tuneup plus > post a share link

Diskpar info > post a share link

https://www.tenforums.com/attachment...p_plus_log.bat

https://www.tenforums.com/attachment...iskparinfo.bat


Batch files for use in BSOD debugging
Batch files for use in BSOD debugging
Batch files for use in BSOD debugging