Salta al contenuto principale

BackUp & Recovery

Thread needs solution

The recovery won't work. It requests a device driver that doesn't exist.

PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31

How do I resolve the problem?

0 Users found this helpful

Patrick, you will need to create a WinPE recovery disk if the default Linux recovery disk is unable to locate your drivers for the recovery process to continue.

However, based on the limited info provided above, it seems like you may have already pushed an image to a system and it is not booting because of a missing driver - ist that the case?  If so, did you push an image to new hardware?  If you did push the system to new hardware, you will need to run Universal Restore Recovery media at this point in time and generalize the install with UR, boot to Windows and then install additional drivers manually.  Or, you can slip specific drivers into your newly pushed image using Univesal Restore as well and hopefully it will boot after that.  

Acronis Universal Restore

Using Acronis Universal Restore

Creating Acronis Universal Boot media

 

 

Bobbo_3C0X1,

  Thank you. However, I guess I didn't make my problem clear.

  I was attempting to upgrade from one windows 10 PC to a new windows 10 PC and when I was running the Universal Restore it stopped at 56% and gave me the message that PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31 is missing and needed ot continue. Both PC's are still running, but the old one won't be for much longer.

 Now, what do I do.

 

The driver in quesiton is that for Intel extensible host controller 3.0 driver.  This is your USB 3.0 driver.  Provide the .inf driver for your USB controller so that UR can install it.

I'm still not sure of what you've done so far.  I'm guessing that 1) you took an image of an older Win 10 PC on one type of hardware 2)You pushed that image to new hardware 3) You are now running UR on the new hardware that has the old Win 10 OS image on it 4) You are supplying drivers during the UR restore process.  Is that correct?  If not, please verify the steps you've taken.

Other than #4 above, if you've done the first 3, don't supply drivers at this point.  I do not know where you obtained your drivers or if you copied them all from the old system and are trying to inject them... the error is suggesting that one of the drivers you are trying to inject is not available at the location where you have told it to look for drivers to inject during the UR process.  As a result, I would just  run UR by itself to generalize all drivers and not inject anything at this time.  Once complete, Windows should then boot with all generic drivers.  Upon Windows boot, you can then install specific manufacturer drivers through computer management for each unrecognized device.  It would be good if you had all of your manufactuer drives downloaded in advance to help streamline the process.  Alternatively, when you run Windows update, it will install updated Windows compatible drivers which should work for most devices, but may not be the latest ones available from the manufacturer.

Bobo_C0X1,

  You are to a degree correct with what I have attempted.

  I created the clone of my old PC Windows 10 on an exteranl HD.

  I created a Bootable Flash drive.

  On the same Flash drive I created as the boot, I installed the UR ( the first time w/o any drivers ) and that is when I ran into the problem of not being able to move the old system to the new system and no oportuntiity to install any drivers.

  I then created the UR with all the drivers I have, including the INF files ) from the New PC. I thought I needed to save and use the drivers from the New PC, not the one I have on the drive cloned. Again, I started getting requests for numerous DLL's. After the 5th request ( each time I find and add I had to start the procedure over ).

  Now, did I understand things wrong. AM I supposed to use the drivers from the cloned PC on the UR?

  I appreciate all your help.

Thank You,

Hi Patrick.

Here's what I would try...

Clone your original drive to the new disk that will be going into the new machine.  

Remove the new machines disk (if it is not the same one you just cloned to) and replace it with the newly cloned disk.

Boot the machine to your UR offline recovery media.  Don't inject any drivers at all.  Instead, just run UR.  This should generalize all drivers in the clone image to Generic Windows 10 drivers which should make the PC bootable.

Boot the machine and hopefully it boots "as is".  If it does, then go into computer management / device manager and manually update drivers that have triangles next to them or question marks.  Windows 10 should catch most of them anyway - the main one you need at first is networking so it can connect to the web and download drivers.  otherwise, grab the drivers from the manufacturer and install those one by one as needed. 

This is probably the easiest method, although a little slower because of the manual steps after Windows boots up.

 

Alternatively, during UR, you would still need to generalzie the system, but would supply the drivers for the new system hardware - usually though, you only want to add drivers for things like RAID storage controllers, special hard drives (PCIE NVME drives) and/or networking.  If you add the wrong drivers here, your system probably won't boot so I usually just generalize and install drivers after Windows has booted up.

Bobo_3C0X1

  Thank you. I will try as you suggest - hopefully tomorrow or the day after and let you know how it goes.

Pat