Salta al contenuto principale

Universal Restore media set up wants driver file that it cannot access

Thread needs solution

Universal Restore wants a driver, ltmdm64.sys, that is not in the INF folder but rather in the WinSxS folder. After I load the INF folder drivers in the media creation wizard, I get an error message of the missing driver, which stops the media creation process. I can navigate to this file in File Explorer, but I cannot navigate all the way down to it in UR media creation because UR will not open the final folder that contains this file. So I can't go forward with media creation. Any good insights on how to proceed out there?

0 Users found this helpful

Tommy, from a quick search on Google the ltmdm64.sys is for an Agere Windows Modem which sounds like a very old dialup device to have in your system - are you sure that you want to include such a device in your Universal Restore media?

The purpose of Universal Restore is to provide drivers for new hardware installed in a different system than where your backup was created so that when your backup is restored it can work with that new hardware.

There should be no need for you to include the contents of your system INF folder in your UR media and doing so will cause problems in creating the media.

Please see KB document: 2149: Acronis Universal Restore where it states:

(!) All the other drivers (e.g. video and sound card drivers, plug and play drivers) are not installed by Acronis Universal Restore, as they can be installed in Windows after the successful migration.

Tommy,

Are you restoring an image from a different machine to a new one? If so, often times, it is easier to run Universal Restore "as is" without adding any drivers at all.  This will generarlize all drivers to the OS defaults and hopefully make it bootable (in most cases).  Then, you boot into Windows and manually install drivers in computer management >>> device manager.

You can slip in drivers with UR if the system is not booting after UR has been run (for instance if you have a special RAID controller that is not in the OS generic drivers when Windows is installed fresh).  If UR is seeing your installed OS though, I would try running it without any other drivers first and then try to boot Windows and go from there.

FY, I hope you have a backup of the original data before running UR - just in case.