Windows 10 Recovery Tools - Bootable Rescue Disk

You should be able to boot a wim file from HD under either efi or bios. I have at least a dozen on my boot menu. It is just a bootable wim made with a program to which many of us have contributed. I don't use the builder, I make mine manually.

The macrium thing is also a bootable wim.

Probably something wrong with the bcd entries.

Kbird said:

Thanks for confirmation ..thats what I normally do too.


Can't figure out why I can't get the Kyhi Rescue Partition to Work though that's mentioned in the OP
have tried it at the biginning and end of Drive now , FAT32 ,Active etc made no difference still getting a 0xC0000225 Error and a device that can't be accessed.



KB

SIW2 said:

You should be able to boot a wim file from HD under either efi or bios. I have at least a dozen on my boot menu. It is just a bootable wim made with a program to which many of us have contributed. I don't use the builder, I make mine manually.

The macrium thing is also a bootable wim.

Probably something wrong with the bcd entries.

I looked at it with EasyBCD2.2 but didn't see anything wrong myself , but perhaps you will ?

Is the Bootloader path for Kyhi's entry right? or is it pointing to C:\

I have not seen a OsLoader Entry before but assume that is the Windows Boot Manager from the Partition Info.

Not sure I have seen CD entries before either but this MB has a setting for booting EFI CD/DVD's in the bios ( on Auto) as I think it cameout about Win8 time. Thanks

If you are using EasyBCD, you can look at it better using the detailed (debug) mode. Assuming the location is correct ( M:\sources\boot.wim) not sure why the loader path is winload.exe rather than winload.efi.
You also need to check the sdi path. \NST\BOOT.SDI

Mignt be better to use something that lets you change the values. BOOTICEx64.zip

Ztruker said:

See what @KYHI or @NavyLCDR have to say.

My rig is a full UEFI with GPT partitions.

I don't use a BCD entry for the boot.wim file. I extract the entire contents of the ISO file to a FAT32 partition and use boot override in UEFI to boot from the partition. If you have a legacy BIOS, the FAT32 partition must be the active partition on an MBR partitioned drive.

NavyLCDR said:

I don't use a BCD entry for the boot.wim file. I extract the entire contents of the ISO file to a FAT32 partition and use boot override in UEFI to boot from the partition. If you have a legacy BIOS, the FAT32 partition must be the active partition on an MBR partitioned drive.

I have MBR and a partial EFI MB it seems, but changing that setting in the Bios didn't help. The FAT32 partition is Active , and I mounted the KYHI Iso and copied all the Files too it , then ran the .bat provided in the zipfile in the OP , but no luck so far.

In a Command Prompt (Admin), I would try running:

bootsect /nt60 M: /force /mbr

Are you flat booting winpe. Different from booting wim file. You have 1.24gb used on that partition.

@ TomCat ...I think the difference is the GPT Disk and Full UEFI in your Case

@SIW@ I am not flat-booting ( had to google that) it is setup as a RamDisk and this is confirmed by the BootICE Program Posted above. BootICE's UEFI Tab actually shows the DVD entries and the Boot Manager Entry (OsLoader00) ..I tired adding the M Partition using that TAB but it didn't help , that is the weird EFI setup I have on this X58A Board I think and why , the Windows Boot Manager "can't find a device". Plain old MBR , fat32 ,active partition is not working either though...

@ NavyCDR I have not tried fixing the MBR , incase I screwup my Win10 Boot , though I guess the Macrium or Kyhi Disk could fix it if it went all pear shaped on me...

Thanks guys.

KB

I apologize if this issue has all ready been addressed in this thread. I used search but I have not found anything that helps me so far.
I have a USB Drive with Win14393PESE_x64 ISO v170116installed and it boots my system. My issue is no Wi-Fi. PENetwork shows only the LAN network adapter. How do I get it to find the Wi-Fi adaptor?
HP Pavilion Notebook 17-g121wm
LAN Realtek PCIe FE Family Contoller is found
WLAN Realtek RTL8188EE 802.11 bgn Wi-Fi Adaper is not found