Wimboot Won't Load System Image Recovery from Windows Repair

[NiKiZe]

So for usb boot it shows cdrom as well?

(2016-08-12 16:35)vphoebe Wrote:  Booting from USB (and getting bmrui to load), these are a few registry keys in HKLM\System\CurrentControlSet\Control

Code:

"SystemStartOptions"=" MININT  REDIRECT RDIMAGEOFFSET=8192 RDIMAGELENGTH=3161088 RDPATH=MULTI(0)DISK(0)CDROM(0)\\SOURCES\\BOOT.WIM"
"FirmwareBootDevice"="multi(0)disk(0)cdrom(0)"

and here's those keys from wimboot

Code:

"SystemStartOptions"=" MININT  REDIRECT RDIMAGEOFFSET=8192 RDIMAGELENGTH=3161088 RDPATH=MULTI(0)DISK(0)RDISK(0)PARTITION(1)\\SOURCES\\BOOT.WIM"
"FirmwareBootDevice"="multi(0)disk(0)rdisk(0)partition(1)"

I'm thinking for some crazy reason it's trying to get back to the actual wim file (it's accessible when booting from USB), and it can't because wimboot doesn't mount the boot media as an accessible drive. Who knows why it needs to do this because obviously the wim is unpacked as the X drive.

The wim itself is likely irrelevant, but the boot partition is "cdrom(0)" vs "partition(1)" which bmrui likely uses to try and find other files it needs, or maybe just the existence. with wimboot the partition likely does not exist at all.

Could you test dumping the "cdrom" reg, and importing it into wimboot started, and then trying to run bmrui again, and see what it says.

Full logs of procmon when it fails (stopping the log when the error dialog is shown) and when it works, and then comparing the two logs should narrow down the possibilities.