Skip to main content

Computer won't start after restoring with True Image

Thread needs solution

Hello all,

I'm having a (probably common) issue where my computer will not start after restoring my hard drive via True Image.

I tried using Universal Restore, but that wouldn't work, as it would tell me that some required driver is missing. It says "Cannot find device driver 'PCI\VEN_8086&DEV_8C03&SUBSYS_2253103C&REV_04' for Windows 10," which I can't find on Google or anything. I even tried looking on the support page for my computer and that didn't work either.

Any thoughts? Or am I going to have to start from scratch? (I didn't have anything too important on this computer, by the way.)

Attachment Size
20190329_022834 (2).jpg 1.6 MB
0 Users found this helpful

Joseph, sorry but more questions than answers at this point in time.

What type of backup image are you restoring from, i.e. was this a Disk & Partitions backup, Entire PC backup, or a Files & Folders backup?

What computer was the backup made from, and is this the same computer you are recovering to?
Note: If yes, then you do not need to use Universal Restore - that is only for recovering to different computer hardware, not the same!

How are you doing the Recovery here, i.e. are you booting from the Acronis Rescue Media (on a CD/DVD or USB stick)?
Which boot method are you using for the Rescue Media, i.e. booting as Legacy or as UEFI?

This forum is focused on ATI 2019 - is this the version you are using here or is it ATI 2016 as shown by your signature information?

To answer these questions, this was a Disk & Partitions backup. The computer I backed up is the same as the computer I'm trying to restore. I thought of using Universal Restore because the computer wasn't starting up after I restored the image. I am recovering using Acronis Rescue Media on a DVD, and it is booting as legacy.

Also, I totally forgot to change the version of ATI in my signature from the last time I was here a couple years back.  I'm using ATI 2019.

(By the way, it's totally fine if there are more more questions than answers.)

Don't use UR since this is the same computer you took the backup of.

1) do you know how the OS was originally installed? GPT/uefi or legacy/MBR?

You need to start the rescue media so it boots the same way, which will partition the drive to match. It's important because you want it to be the same, but it is also possible to convert legacy to UEFI (in some cases) but you can't go from UEFI back to legacy

 

2) after restoring, boot the bios and ensure the boot priority is pointing to the main drive still. It's nit uncommon that the bios will switch to the DVD or USB as the priority and will fail to boot those as a result.

 

Joseph, having a disk & partitions backup is good news, so the next question is whether your computer boots into Windows 10 using Legacy or uses UEFI, as this needs to match with how you are booting the Acronis rescue DVD.

Your signature lists 2 different systems where the i7 computer would be expected to use UEFI but the Core 2 Duo could be Legacy or UEFI.

Note: You must boot the Acronis Rescue media using the same BIOS mode as used by Windows in order for the recovery to be successful.

See KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media - with reference to the above note.

I just realized I left out a huge detail here!

At first, I backed this computer up using wbAdmin. wbAdmin wasn't detecting the system image (neither was the "Restore from a system image" option) so what I did was connect the VHDX file as a volume and made a backup of that. I'm guessing that's why the computer isn't starting and why I thought of using Universal Restore, which asked me for an extra driver.
With that said, is there still a way for me to fix this? (Sorry it's so complicated...)

 

Joseph, what's wbadmin? Was this a True image backup or a backup 12.5 (12 or 11) backup? 

 I don't believe it will bootable if you mounted the .vhdx and then backed it up, although I haven't tried. But, I believe when mounted, it's only mounting the OS partition (not sure). If that's the case, might be trouble for booting of it didn't capture the bootloader partition too .

The thing is, if you have a .vhdx already, you can just restore that with Acronis, or even with Windows installer media. It's a supported format.  Is this .vhdx that was built by Acronis or is it an origiginal virtual machine. Just curious, for more clarification.

I'm a little more up to date on wbadmin after Googling it. Had no idea it even existed in Windows as a backup alternative to control panel Windows backup. 

I'd try restoring the original vhdx with your Windows installer disk. If that doesn't work, try with the Acronis media. Just make sure it's a restore of the original vhdx and not the mounted one.

https://sourcedaddy.com/windows-10/perform-backup-and-restore-wbadmin.h…