Universal Restore Missing Driver

Welcome James to the Forum,

Your storage controller mode is the problem.  I would change the mode from AHCI to ATA/IDE on the new rig and attempt to boot.  I believe it should.  Once booted into Windows you can then install the AHCI drivers using Windows Device Manager.

Thank you for the quick reply, unfortunatley the new mobo's bios won't allow me to put it into IDE. AHCI is the only option for it. Would switching the old PC to AHCI and restarting the whole process work? If so, would I have a high chance of corrupting anything? thank you for your help

-Update- I just figured out that I can't change the bios to ATA as I am using a ssd(850 evo). I am going to trying using a hdd(western digital wd10ezex) in hopes of it allowing me to put the drive into ATA mode

-Update 2- My bios still will not allow me to set the mode to IDE on the hdd. Also the old pc bios only allows for ATA mode. What would be your reconmendation for how to handle this now?

Change to ATA, that should infer IDE.

What options do have besides AHCI?

In the old PC bios the only option is ATA. In the new PC bios the only option is AHCI both when I used an ssd or hdd.

What I ended up doing was changing the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msahci registry to 0 from 3 to enable AHCI(which broke it on the old PC). Then backed this up and tried universal retore on it. During the universal restore process I still get the same error as before. But now once I click ignore I can get the new PC to boot finally. Now the problem is that it only makes it to the user select screen and then my I/O devices turn off for some reason leaving me stuck at this point. This happens in safe mode as well. 

Windows 7 is not the best OS when it comes to changing drivers.  When needing to change the SATA mode in the bios, it is best to prep the machine first, immediate close down, change the SATA mode in the bios, and then boot.

In this case, since you're switching machines..

1) Take a full system backup of the original machine "as is" before doing anything else - just in case

2) run the MS fixit tool in this KB article directly on the working (old/current machine) and then power down. https://support.microsoft.com/en-us/kb/922976

3) Take a full system image of the original machine that has been prepped by the fixit tool usin your Acronis bootable offline recovery media - don't boot the system yet - except to the Acronis recovery media to take yoru image.

4) Restore you image to the new machine and set the sata mode as need be (AHCI).  

5) Try to boot - most likely a BSOD due to other driver issues

6) Run universal restore on the system to generalize the drivers - don't include any extra drivers.  When done - try to boot . Hopefully it boots, you would need to go into computer management and install drivers manually.

Assuming this works, you can try to go back to #6 and then inject your drivers with UR so you don't have to manually do them in computer management via Windows.  

Thank you for your time. I searched the page you linked and couldn't find a MSfixit tool. But I read the detailed instructions on the page and they match the steps that I took earlier(post #4) to try to resolve this.

Do you have any other ideas that I could try out?

Well, all be.  There used to be a download on that link provided by Microsoft as a fixit tool to automate the process for you!  I'm digging around my favorites to see if I can find another reference to the actual fixit tool.  Regardless, the change should be applied when the OS is booted.

To my knowledge, no, there isn't really another option when you plan (or need) to change the SATA mode in the bios.  If that is the one driver that's holding you up from booting, you can try booting into safemode on the new system (if you're unable to make the change on the old system - due to hardware failure or the system is already done) and that might allow you to then make the registry change.  

I suppose you could also boot to winPE or some other temporary Windows OS and mount the registry of the newly deployed image to make these changes there as well, but that's probably more complicated than most would like to deal with.  But, iF you had a bootable Windows OS (WinPE would work too with a third party registry editior - or build acronis winPE bootable recvoery using our MVP tool and it will add some nice features like a functioning registry), that would be another option to make this change as well.  

From there, you would launch regedit or a 3rd party registry tool and highlight "hkey local machine".   Then, at the top of the regedit menu, click on file >>> load hive an navigate to the system registry of the original drive (the one you deployed or recovered to the new hard drive).  It would be under C:\Windows\System32\config\system (assuming that your using WinPE and it is loaded as X: and that your restored OS drive is showing up as C: under WinPE.  

You'd give that hive a name (any name you want - I usually just call it "1" without quotes to keep it simple.  That will mount "1" under HKEY local machine  and you could then navigate to those files and change them from there:

HKEY_LOCAL_MACHINE\1\System\CurrentControlSet\Services\Msahci

HKEY_LOCAL_MACHINE\1\System\CurrentControlSet\Services\IastorV

James,

I had a look at your mobo support page and note that there are no storage controller drivers available for your board.  I do see a System and Chipset driver however.  Did you include that driver package on the media where you have drivers loaded?  The System drivers may contain the necessary AHCI drivers you need.

In your first post the device driver pci ven_8086&dev_a102&subsys_79951462&rev_31 is the SATA AHCI device driver not the ATA/ATAPI driver that you suspected.  I was able to find reference to this driver as well on another information site.

You are going to have to locate an appropriate AAHCI driver to go any further with this.  If you cannot locate the driver in the System and Chipset driver package than you can download the Intel 32 bit version from the link below:

https://mega.nz/#!0AEW0SiC!h4EPFl9b6pGeDl-aEG5bQT-mGK0lhNYsl-5ofsPnGZw

Once on the page above click on the Download through your browser link to get the driver file.  It will come in an .rar package so you will need 7zip to unpack it and extract the contents which should then be added to your flash media.

I was able to restore the old PC using a back up so if we need to try anything else on just the old PC it is still an option. Unfortunatley that one reg change only allows the new system to get to the user selection screen before freezing. For now, I think that I am going to use your (00) link to learn some more about using a WinPE and dive into what you just explained.

Oh wow, thank you for that Enchantech. I'm going to give it a look now

James if you're able to get the system booting, but issues are happening (freezing) after that, that hard work is done.  You could now try an inplace Windows upgrade over teh top of the existing OS which should "repair" any issues with the OS and still bring in your applications and user data on top of that.  

How to Perform an In-Place Upgrade on Windows Vista, Windows 7, Windows Server 2008 & Windows Server 2008 R2:  https://support.microsoft.com/en-us/kb/2255099

That did it! I was able to get through the Universal Restore process with no warnings or errors. When I booted the system I'm now looking at a Startup Repair window that says that "Your computer was unable to start" is this normal with the universal restore? I'm amazed that you were able to find that driver, hours of googling turned up nothing when I was looking for it.

Ok, if this current "startup repair" yeilds nothing I'll give that a try! Thank you guys for all of the help!

Ii is not normal that a startup repair needs to be done after using Univeresal Restore.  What I suspect is that you original restore operation did not include the MBR and track 0 for some reason.  You can attempt to restore that partition using the Ti Recovery Media and your backup file or you can also use Windows install disk.  https://www.lifewire.com/how-to-perform-a-startup-repair-in-windows-7-2…

Each time I try to start the computer it fails to start with the same error detected. It says that my iastora.sys file is corrupt. Which I know is one of the driver files you linked to me a min ago. So I've tried using a different thumb drive with the same file as well as redownloading the one you linked me. I also tried different download sites and each time it says it's corrupted. Each time I make sure to remove the previously tried files before I add in the new and run the UR. I will also give the method you just mentioned a try just to make sure that isn't it

Did you provide the System and Chipset drivers for Universal Restore along with the Intel driver I linked for you?  System and Chipset drivers at the bottom of this linked page:

https://us.msi.com/Motherboard/support/H110I-PRO.html#down-driver&Win7%…

Yes, I have extracted the needed chipset files from that download and made sure to include them in the UR process. Sorry about all the hassle  

Ok, so what or how did you get from a startup repair error to a corrupt driver error?  It sounds now like Windows starts and then bombs out with this corrupt driver error, is that correct?

Yeah I get past the windows screen and then it starts looking for files. At the end of that it moves to another window where is says failed to start. Then it trys to repair the disk and at the end I look at all of the tests it ran and results. It's within these results that I see that it's a corrupt driver and that windows can't fix it. 

I'll post a pic of it soon

Have you tried just running UR without including any drivers at all?  Out of the box, Windows should still install on just about any machine.  It is very rare that one has to include any drivers during the Windows install, except for when custom RAID controllers are in play.  I would deploy the existing image again (start with a clean deployment) and, if it will let you, then run UR without adding any additional drivers.  The SATA mode is the biggest issue though since your bios are so different.  

This may be of some help as well as posted by another user recently

https://forum.acronis.com/forum/126967#comment-401091

Acronis states "Your old and new hard drives work in the same controller mode (for example, IDE or AHCI)." So that could have been my problem, I was going from RAID to ACHI. There is a really simply way to fix the change in Windows from RAID to ACHI - found it here

1. Right-click the Windows Start Menu. Choose Command Prompt (Admin).
2. Type this command and press ENTER: bcdedit /set {current} safeboot minimal
3. Restart the computer and enter BIOS Setup (the key to press varies between systems).
4. Change the SATA Operation mode to AHCI from either IDE or RAID (again, the language varies).
5. Save changes and exit Setup and Windows will automatically boot to Safe Mode.
6. Right-click the Windows Start Menu once more. Choose Command Prompt (Admin).
7. Type this command and press ENTER: bcdedit /deletevalue {current} safeboot
8. Reboot once more and Windows will automatically start with AHCI drivers enabled.

I originally tried running this image through UR without any extra drivers as I forgot to select them the first time. It gave me that same error I mentioned and when I clicked ignore and tried the system out it didn't even get to the windows screen. I think like you said that sata mode probably killed it. I'll perform the steps you just mentioned(@Bobbo) on the old PC and back it up to give it a try. 

James,

I agree with Bobbo on this.  The biggest issue you have here is that MSI is assuming a clean install of an OS on this board so is not supplying drivers for the storage controller instead allowing native Windows drivers to do their thing.  Your move from an older ATA/ATAPI controller to one of the latest  SATA controllers is a problem because of the mode change.  It is best to get the mode right at the source, backup and then restore to the new board.

Ok, so after doing a bunch of research I found out that the H61 Chipset in the old PC can run in AHCI mode. But, Dell has chosen to not to allow me to swtich out of ATA in the bios for some reason. So now I am looking at using a bios mod app to change this setting and reflash the bios. I think that this might be the only way that I can make the old system run AHCI. Are there any bios mod apps that you guys would recommend?

Right now, what the new system is doing is booting up fine and getting all the way to the user select screen then either freezing or turning off my I/O devices. I have been able to boot it into repair mode and do the start up repair that you mentioned last night Enchantech. Once through with the start up repair it will say that windows booted normally and that there where no errors. Yet, I can never get past that user select screen. Running the startup repair tells me this happens because there is no OS installed. Also, I am at a point now on the recovery disk that I can install drivers to the new system

I find the site at the link below a good source for bios modding and storage controller drivers in general.

http://www.win-raid.com/forum.php

I will ask again if you tried to restore the MBR and Track 0 partition from the backup image file you have to your new disk?  Your reference now to startup repair not finding an OS installed is troublesome.  I would think that indicates a corrupted BCD store.

Another question I have is did your old system boot via a legacy bios or did it have UEFI capability or do you even know?  I am betting that your old system booted via bios and this restored disk you are working with might have been restored as a UEFI boot device which has furthered your issues.

Do you recall when you booted the recovery media to perform the restore did the boot enrty selection you chose to launch the media have UEFI in the name?

The old system boots in Legacy and the new system uses Legacy+UEFI. When I boot the acronis bootable disk on the new machine it says uefi, but the hhd that the old system is restored to doesn't have uefi next to it when I boot the system. Is there anyway to just try to recover the MBR and Track 0? Or will I need to start the whole recovery/UR procedure again? I'll be able to provide some more hopefully useful information soon

Ok, you have said a mouthful there.  Your new system can boot either UEFI or Legacy where as your old machine which the image came from boots Legacy only.  When you boot the recovery media and use the UEFI entry this boots the media in UEFI mode so any restore attempt will result in a disk prepared for a UEFI capable system as UEFI bootable. 

Your image of Windows 7 is a 32 bit version and is incapable of booting as UEFI.  So long story short failure to boot.  I am surprised that you get along as far as you do with it!  Amazing!  I do not think this will work but you can give it a try, go into your bios and change the boot mode options from UEFI + Legacy to Legacy only.  Change any other settings that refere4nce UEFI + Legace to Legacy olly as well.  Save and exit and see what happens!  If that fails and I think it will, perform the following:

So here's were I think you stand at the moment.  First you are going to have to forget about using UEFI boot on this new board if you are going to continue using the Win 7 32 bit OS.  Since the new board will work in Legacy mode then you are going to have to set the bios for Legacy mode only.

You are at that point, going to have to redo the restore operation on the new disk again using the bootable recovery media.  Once you have the new board set to boot Legacy only then when you look at the boot order for the bootable recovery media you will see that the UEFI in the name has gone.  If you do not see UEFI in the name then scroll through the list of devices until you find that one without UEFI in the name and make it first in the boot order list.

If you are using a hotkey like F8 for a boot menu list to boot from, same thing applies to that too.

Once booted browse to your backup image file and select the entire disk, all partitions for recovery.  Then select your new drive as destination and run the restore just as you had done before.

After that run the Universal Restore tool and I would suggest that you only provide System - Chipset, and storage drivers for it.  Hopefully it will complete the process.  Once done attempt boot.

Ok, I'll give all of this a shot and let you know how it goes! and thank you again for taking all this time to give me a hand, I really appreciate it