Acronis True Image 2019 Universal Restore Media Builder Error
First I created a folder containing drivers for all my storage devices and controllers (.inf and .sys files listed in the "Properties" for each by right-clicking on device/controller entries in Device Manager).
I executed the Acronis Universal Restore from the "tools" window:
- select "Windows-Like Representation" then "Next" button.
- "Next" button on the Linux parameter dialog without entering any parameters.
- Select Actonis True Image and Acronis Universal Restore from components to add, then "Next" button.
- "Next" button on bootable media startup parameters without adding any parameters.
- Select .iso on the output media selection pane then "Next" button.
- Select the location and name for the output file then "Next" button.
- Select the folder with my storage device / controller drivers then "Next" button.
- Select "Proceed" on the Media Builder summary page (see screenshot).
The following error alert is displayed, the operation is cancelled and no media is built.
Code: 262,158(0x0004000E)
LineInfo: 0x6983D207431790EE;
Module: universal_restore_media_builder_vs_40067
If I do not select to add any drivers, (just hit "Next" on step 6 without designating a folder with driver files), the media will be built.
What does the error above mean, and / or what am I doing wrong?
I've already built a rescue disk (DVD) using the MVP Media Builder (v 18.2) accessible through the "Third Party Tools" gadget on the Acronis TI 2019 "Tools" pane. However, on that one I did not inject drivers, just used the "Installed ADK" option.
What a dummy like me hasn't figured out yet is, by not explicitly specifying drivers, which drivers will be included by default? My system (HP z840 workstation) has a single system drive, and a 4-drive RAID 10 running from the internal SAS controller, in addition to three external USB HDs (used primarily for system and media [photos, video, and graphics] backups). With all those drivers installed and working on the system from which I create the rescue media, do I need to explicitly specify (and create a fold containing .inf and corresponding .sys files) for each of those storage "modes" (single HD, RAID, and USB external storage)?
My second dumb question is: The "Universal Restore" 'feature' infers it allows restoration to "unlike" hardware, or a 'transfer' of the system to another machine. That would seem to indicate that a standard Acronis system backup of one full system can't be restored to a different machine that is booted to bare-bones OS install, then Acronis TI install, and select "restore". Now, the one time I had to do this (TI 2016 perhaps?) I recall I had all kinds of problem with incorrect permissions on almost every file that was not the base OS install. Would that still happen if a bare-bones OS install is "replaced" by MVP / Universal Restore media install followed by a TI full system backup restore?
Third, I've seen other references as to how to inject drivers into wim and other "rescue media", but they usually send me to multiple long pages about remote installs, complex batch files using power shell scripts... I'm too old, I need a simpler process - like "mount the image, copy <these files from here in a working OS> to <this location in the mounted rescue media volume>. Assuming of course, MS hasn't made such a simple operation impossible to "protect the preisthood" :^}
Final dumb question: During MVB media build it says if I choose WinRE instead of PE from ADK, that "Acronis Backup not supported." What exactly does that mean? Could I not, subsequent to getting booted from WinRE, run TI to do a restore, even if TI is on separate media?
Sorry for the stupid questions, but it has been years (decade and a half?) since delving into WIndows internals, so all this RE-PE-DISM etc. stuff is somewhat puzzling...
Enchantech wrote:
This is a known issue as far back as TI 2016. The workarounds are to not build the media with the drivers present. It the UR media you created can locate your restored OS. If it can use it to inject the drivers at that point.
If you build WinPE media , you can inject drivers during the build process if you use the MVP Media Builder tool which you can find HERE
WMC,
You wrote:
What a dummy like me hasn't figured out yet is, by not explicitly specifying drivers, which drivers will be included by default? My system (HP z840 workstation) has a single system drive, and a 4-drive RAID 10 running from the internal SAS controller, in addition to three external USB HDs (used primarily for system and media [photos, video, and graphics] backups). With all those drivers installed and working on the system from which I create the rescue media, do I need to explicitly specify (and create a fold containing .inf and corresponding .sys files) for each of those storage "modes" (single HD, RAID, and USB external storage)?
The MVP Media Builder tool includes a few common drivers found on a good number of motherboards. It includes Intel IRST Storage drivers, and Killer NIC drivers for example for convenience. If you read the Read me file included with the tool there are instructions on how to add your own drivers.
In your case given that you have an SAS controller you would need to add the controller drivers for that drive array to have full support for the hardware. As for USB drivers those should be default in the WinPE itself.
You Wrote:
My second dumb question is: The "Universal Restore" 'feature' infers it allows restoration to "unlike" hardware, or a 'transfer' of the system to another machine. That would seem to indicate that a standard Acronis system backup of one full system can't be restored to a different machine that is booted to bare-bones OS install, then Acronis TI install, and select "restore". Now, the one time I had to do this (TI 2016 perhaps?) I recall I had all kinds of problem with incorrect permissions on almost every file that was not the base OS install. Would that still happen if a bare-bones OS install is "replaced" by MVP / Universal Restore media install followed by a TI full system backup restore?
Third, I've seen other references as to how to inject drivers into wim and other "rescue media", but they usually send me to multiple long pages about remote installs, complex batch files using power shell scripts... I'm too old, I need a simpler process - like "mount the image, copy <these files from here in a working OS> to <this location in the mounted rescue media volume>. Assuming of course, MS hasn't made such a simple operation impossible to "protect the preisthood" :^}
Not a dumb question at all. Universal Restore is a mystery to most users. The Universal Restore tool is used to generalize drivers when a backup image from one machine is restored to another with differing hardware. The procedure would go like this:
- Use the True Image boot media application to perform the restore of the image to the differing machine.
- Run Universal Restore to address (Generalize) driver differences on the newly restored machine.
- Once complete boot the restored machine.
Windows 10 is much better at handling this sort of thing by itself these days and in most cases if the restored OS is Windows 10 then Windows itself will in all likelihood be able to generalize drivers itself without the use of Universal Restore..
You wrote:
Final dumb question: During MVB media build it says if I choose WinRE instead of PE from ADK, that "Acronis Backup not supported." What exactly does that mean? Could I not, subsequent to getting booted from WinRE, run TI to do a restore, even if TI is on separate media?
Acronis Backup is a different product than True Image. The reference you see is directed toward user of that product.
You can use WinRE which is or should be resident on your Windows installed machine to build MVP media in lieu of installing the Windows ADK to create a WinPE version. This choice is up to you as both provide the same features..
Thanks for you patience and clear answers to my "stupid user" questions. If only fora and support sites for other products were so accommodating...
Thanks again.