Skip to main content

WinRE created on Windows 7 won't boot

Thread needs solution

Today I created new WinRE recovery media using the latest build. I have a Windows 10 and Windows 7 PC and created the media on each system. I used the easy approach.

I noticed that the size of the data on the Windows 10 boot drive was significantly larger than the Windows 7 version.

The Windows 7 USB would not boot on the same Windows 7 PC is was created on. The Windows 10 USB would boot just fine on both systems. Both PCs are configured nearly identically. Both run Asus M/Bs, Samsung SSD C: drive and WD Black D: drive. Windows 7 PC is 2014 vintage, Windows 10 PC is 2017 vintage.

On the Windows 7 system, I selected the UEFI: SanDisk U3.

DSC_2427-1.JPG

This is what appeared. I don't understand what that message really means.

DSC_2432-1.JPG

The boot worked fine selecting the same thing when it was the other Windows 10 created drive. I ended up running two backups, one created with the Linux boot drive and one with the working Windows 10 drive. They are nearly identical in size. Would there be any difference at recovery time? OK to use WinRE to recover the Linux created .tib? I assume I'm good with what I got... just curious as to why the WinRE on Windows 7 would not boot. Is it that it needs to be created using the ADK? I thought ATI 2018 took care of that.

 

0 Users found this helpful

Bruno,

Does your Win 7 machine boot via UEFI?  If not you need to select the SanDisk option without UEFI in the entry.

If you are booting via UEFI and you have Secure Boot enabled you might need to disable Secure Boot in order to boot the WinRE or WinPE media.

Yes, UEFI on the Windows 7 machine. The WinRE rescue disc created by ATI on the Windows 10 machine boots fine on the Windows 7 machine (selecting the UEFI boot), so I can't see how there would be any reason to change anything in the bios.

I did happen to also discover that consistently my C: drive is backed up as the D: drive when using the WinRE boot drive, but with Linux it is backed up as C: drive.