Windows 10 Recovery Tools - Bootable Rescue Disk

  1. Coram Daes's Avatar
    Posts : 118
    W10Pro x 4
       #1321

    Been using HIRENS for ages, time for an upgrade. :)
      My Computers

  2. Coram Daes's Avatar
    Posts : 118
    W10Pro x 4
       #1322

    bleh, general memory error

    - Secure boot enabled on desktop
    - x64 version
    - created with rufus using iso as boot source
    - nothing altered
    - could get in to task manager doing ctr-alt-del
      My Computers

  3. Kyhi's Avatar
    Posts : 3,539
    Windows 3.1 to Windows 10
    Thread Starter
       #1323

    Coram Daes said:
    bleh, general memory error

    - Secure boot enabled on desktop - OK
    - x64 version - OK
    - created with rufus using iso as boot source - NO GO
    - nothing altered - OK
    - could get in to task manager doing ctr-alt-del
    Copy Contents of ISO to Fat32 Formatted USB
    The System Needs about 5GB Ram to load Rescue Media
      My Computer

  4. Coram Daes's Avatar
    Posts : 118
    W10Pro x 4
       #1324

    Ah, I see now, it was NTFS. Damn Rufus.

    Also "MBR partition scheme for UEFI"
      My Computers

  5. NavyLCDR's Avatar
    Posts : 15,492
    Windows 10 Pro
       #1325

    @Kyhi,

    Help, please! Most of my computer have an SSD and a HDD drive. At the end of the HDD I put an 8 GB FAT32 partition to hold a Windows 10 installation drive with the boot.wim file replaced with your recovery tools boot.wim file. So far all of my computers have picked up the bootable FAT32 partition and have added the option to boot to it automatically to the UEFI boot menu (F12).

    I just got a new laptop and have not added the second hard drive to it. I put the 8 GB FAT32 partition at the end of the single SSD, but it is not getting added to the UEFI boot menu. I have the option of manually adding a UEFI boot menu option by entering the filename I want to boot from, so my question is, which .efi file do I select from the recovery partition? The choices are below:

    Windows 10 Recovery Tools - Bootable Rescue Disk-capture.jpg

    Thank you!
      My Computer

  6. Superfly's Avatar
    Posts : 3,325
       #1326

    NavyLCDR said:
    @Kyhi,

    Help, please! Most of my computer have an SSD and a HDD drive. At the end of the HDD I put an 8 GB FAT32 partition to hold a Windows 10 installation drive with the boot.wim file replaced with your recovery tools boot.wim file. So far all of my computers have picked up the bootable FAT32 partition and have added the option to boot to it automatically to the UEFI boot menu (F12).

    I just got a new laptop and have not added the second hard drive to it. I put the 8 GB FAT32 partition at the end of the single SSD, but it is not getting added to the UEFI boot menu. I have the option of manually adding a UEFI boot menu option by entering the filename I want to boot from, so my question is, which .efi file do I select from the recovery partition? The choices are below:

    Windows 10 Recovery Tools - Bootable Rescue Disk-capture.jpg

    Thank you!
    The EFI boot file is this one:
    \efi\Microsoft\boot\efisys.bin
      My Computer

  7. Kyhi's Avatar
    Posts : 3,539
    Windows 3.1 to Windows 10
    Thread Starter
       #1327
      My Computer


  8. Posts : 7
    Windows 10
       #1328

    Hello,

    I am using Windows 10 x64 (Version 1803) with standart NTFS filesystem on my PC.

    I am trying to add additional softwares to Win14393PESE_x86 ISO v170116 with Modify WinPESE.

    • I "Select 2" and add new folders and files to the "Program Files" folder only. I am not doing any other changes.
    • I "Select 2" again.
    • finally I "Select 4" to build a new iso.



    I am trying to boot the ISO with VMware and it is working.

    When I repeat the software adding process, the VMWare is failing on the windows logo with the error below. Also sometimes I am getting the error on first time of the process.

    Powering on a virtual machine fails with the error: A fault has occurred causing a virtual CPU to enter the shutdown state

    Click OK to restart the virtual machine or Cancel to power off the virtual machine.
    A fault has occurred causing a virtual CPU to enter the shutdown state. If this fault had occurred outside of a virtual machine, it would have caused the physical machine to restart.
    The shutdown state can be reached by incorrectly configuring the virtual machine, a bug in the guest operating system, or a problem in VMware ESX.
    I am doing health check to the wim file with Image Health. Wim is healthy.

    Have you ever experienced this problem?
      My Computer

  9. cereberus's Avatar
    Posts : 12,008
    Windows10
       #1329

    Makiko said:
    Hello,

    I am using Windows 10 x64 (Version 1803) with standart NTFS filesystem on my PC.

    I am trying to add additional softwares to Win14393PESE_x86 ISO v170116 with Modify WinPESE.

    • I "Select 2" and add new folders and files to the "Program Files" folder only. I am not doing any other changes.
    • I "Select 2" again.
    • finally I "Select 4" to build a new iso.



    I am trying to boot the ISO with VMware and it is working.

    When I repeat the software adding process, the VMWare is failing on the windows logo with the error below. Also sometimes I am getting the error on first time of the process.



    I am doing health check to the wim file with Image Health. Wim is healthy.

    Have you ever experienced this problem?
    There is a new version of vmware out that is 1803 compatible - maybe you need to upgrade?
      My Computer


  10. Posts : 7
    Windows 10
       #1330

    cereberus said:
    There is a new version of vmware out that is 1803 compatible - maybe you need to upgrade?
    I am using the latest version of VMWare: VMware Workstation 14 Pro (14.1.2 build-8497320)

    This problem does not seem to be related with VMware. Something seems going wrong while editing and rebuilding the wim and iso.

    If anyone experience this problem, have a solution or have an idea please let me know.

    Thank you.



    ---------------------------
    WinPESE - VMware Workstation
    ---------------------------
    A fault has occurred causing a virtual CPU to enter the shutdown state. If this fault had occurred outside of a virtual machine, it would have caused the physical machine to restart. The shutdown state can be reached by incorrectly configuring the virtual machine, a bug in the guest operating system, or a problem in VMware Workstation.

    Click OK to restart the virtual machine or Cancel to power off the virtual machine.

    [ ] Do not show this message again
    ---------------------------
    OK Cancel
    ---------------------------
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 08:56.
Find Us




Windows 10 Forums