Skip to main content

Steve Smiths Universal Restore Explanation Thu, 12/22/2016

Thread needs solution

I created a Universal Restore USB and Acronis Bootable Media and sees the "no operating system found" when he loads it to see if it boots. Unsure of what is going on I place my inquire here for when I get a new Motherboard ect. I would like to understand.

I have an older system with legacy BIOS  not UEFI. I got past the creation of a Universal Restore, Acronis Bootable Media USB issue. Now on to 1. Making an image of my full C: disk & partition to be migrated.

I am preparing for the day I make the switch. I do not understand the not seeing the operating System. In my case Windows 10

I get going to DriverIdenifier and getting the drivers for my new system I am a simple guy, i like Steve Smiths steps I just don't know what I am missing.

 

Steve Smith posted way back when:

Samuel, I am not sure that you are understanding how Universal Restore is intended to be used.

In brief, the steps should be as follows:

  1. Make a full disk & partitions backup image of the source disk drive containing the OS being migrated.
  2. Make the Acronis bootable Rescue Media on CD or USB.
  3. Make the Acronis bootable Universal Restore Media on CD or USB.
  4. Boot the target system from the Acronis bootable Rescue Media and restore the backup image created in step 1. to the target disk drive.  
  5. Shutdown the target system and remove the Acronis Rescue Media and storage drive.
  6. Boot the target system from the Acronis Universal Restore Media and select the restored Windows OS on the drive where the backup was restored to.  All AUR to prepare the OS to work with the different hardware found on the target system.
  7. Shutdown the target system and remove the AUR media.
  8. Attempt to boot the target system from the restored / prepared Windows OS and allow time for any new devices to be detected during Windows startup, new device drivers to be installed etc.
0 Users found this helpful

Tsquare, it probably isn't a true test to try using the AUR boot media on your existing system as would be better to do this when you have the new computer that you will want to use it on in anger.

I tested this on my current laptop and got mixed results. 
With the default Linux based AUR boot media, this just gave me a black screen with a blinking cursor then sulked forever!
I then created the Windows PE version of AUR (using the MVP Custom ATI builder script) and was able to launch AUR successfully but then the only OS that it found was my second copy of Windows 10 which is used in dual-boot on this laptop!  So it didn't find my primary Windows 10 OS on this computer.

capture_001_19102017_164347.png

BCDEdit shows that Windows 10 1703 is found on my D: partition but that my Current OS is Windows 10 Insiders

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 10 Insiders
locale                  en-US
osdevice                partition=C:
systemroot              \Windows
resumeobject            {239fed79-a3bc-11e7-9ab2-806e6f6e6963}
bootmenupolicy          Standard
hypervisorlaunchtype    Off

Windows Boot Loader
-------------------
identifier              {32bba944-a449-11e7-85df-fb07e114a1ed}
device                  partition=D:
path                    \Windows\system32\winload.exe
description             Windows 10 1703
locale                  en-US
osdevice                partition=D:
systemroot              \Windows
resumeobject            {f626537c-a493-11e7-90e7-806e6f6e6963}