Skip to main content

BIOS Reset after restore

Thread needs solution

Hi, 

I have been using True image for years, and never had any problem. I used true image either from within windows (to make backup) or booting on the usb stick (to restore). 

Recently I though it would be great not to need the USB stick. I tried to activate "startup recovery manager" but did not work. So I created a 500mb partition, and copied the files from the usb (linux version of true image, not windows PE) to this partition and added an EFI entry pointing to the bootx64.efi in the EFI folder of this partition (using easyEFI). It worked without any problem, I manage to boot true image from that partition and restore my OS (C drive). 

HOWEVER: after the restore was completed, the laptop rebooted, and went straight into the bios. In the bios, the HDD was showing, but the EFI entries  (e.g. windows boot manager) were not showing. I then rebooted a number of time, but each time it went straight into the bios and I could not get pasted that. I then turned off the laptop (full power off), waited a bit, and started it again. It took a good 2 minutes as the laptop did a cmos clear. After that, my bios was back to factory default, and the standard efi entries (e.g. windows boot manager) were showing again.

Is this a one off? No. I tried again to restore a different backup, and same thing happened. If I restore the same backup using the USB, it works fine. 

Any idea why this is happening? Is it because the 500mb partition (with true image) is on the same disk as the C partition I am restoring?

Thanks

 

0 Users found this helpful

It may be the bios.  I've been battling with my custom Gigabyte Gaming3 Z170X for months and thought it was fixed with a recent bios versions.  UEFI does not seem to be standard like legacy/CSM bios is/was.  In my bios, the firmware seems to set some kind of record for each device that has ever booted.  You would think that after a cold boot (unplug, dissipsate current, etc), it would detect all hardware adn create proper "windows bootmanager" and UEFI bootable paritions each time... not the case with my board - it holds onto them from the first time the device was detected and has been a royal P.I.A.T.A.!!!!  With all of our Office Dells, this is a relatively an easy process, but on this board, I basically have to physically short the CMOS with the jumpers when I deal with any internal disk changes or OS recoveries/clones.  I can repeat this behavior even after doing simple things like bootrec /fixboot ... bootrec /fixmbr... bootrec /rebuildbcd which also put my sytgem in a non-bootable state again, just from running those basic commands!

Grrrrrrrrrrrrrrr.  I feel for you.  However, based on my own testing and results, I think some of us may be in for UEFI bootloader issues until UEFI entries are standardized.  

I've recently been playing around with the info from:

https://neosmart.net/wiki/fix-uefi-boot/#amph=1  under Fix UEFI Boot in Windows 8, 8.1 or 10, and still basically have to reset the CMOS anyway - sigh. 

I concur with Bobbo here.  Without a standard UEFI manufacturers are free to roll their own UEFI flavors.  As a result some will work fine while others not so much!