MVP Tool - CUSTOM ATI WINPE BUILDER

Tom,

I can give you a few pointers. As you've learned, Universal Restore is usually not needed with Windows 10. It handles adapting to new hardware quite well on its own. The MVP Tool will automatically include UR if it is installed on the machine you are building from. Adding the drivers you need to the recovery media is easy. Use the Drivers_Custom folder with the MVP Tool. Build using the Advanced option using the ATI media builder to get the add a driver option. There are a couple of good references on how to get the drivers you need in the correct inf/sys format. Getting them from OEM support websites can be difficult. Here are two forum topics on the subject.

https://forum.acronis.com/forum/best-practices-data-protection/guide-add-drivers-winpe-recovery-media

https://www.acronis.com/en-us/blog/posts/power-user-insights-advanced-winpere-driver-injection-acronis-media-builder

The easiest way to have drivers available for injection in a restored system that will not boot is to use a USB flash drive for the recovery media and create a Drivers folder in the root of the drive. A good way to practice would be to change the SATA mode in the BIOS of a machine from AHCI to RAID. This will prevent the machine from booting if the boot drive falls under the RAID controller. An example would be an SSD or HDD boot drive connected to an Intel SATA port. You will need to inject the Intel RST driver IaStorAC.inf found in the MVP Tool Drivers_Custom folder. I've found that Universal Restore hasn't worked well lately for Windows 10 systems. If it doesn't work, you will need to restore the system again and you can inject the driver manually from the recovery media as follows:

1. Boot the MVP media.

2. Use the command prompt to inject the driver with this command:

dism /Image:C: /Add-Driver /Driver:"F:\Drivers\x64\IRST\IaStorAC.inf"

Where C: is the drive letter WinPE has assigned to the Windows boot drive you are injecting the drive into.

Where F: is the drive letter WinPE has assigned to the recovery media.

You can use the A43 File manager in the MVP media to identify the proper drive letters.

@IanL-S Not sure how I ended up in the 2017 forum... Sorry about that!

@Mustang Thank you for the tip. I have since discovered that using DISM to inject drivers obsoletes Universal Restore for us entirely. I had read (or assumed) that Universal Restore would also generalize the image in the same way that Sysprep does, but either I am using it wrong or it actually does not. All the original hardware remains "ghosted" in device manager instead of actually being removed as Sysprep would.

Tom Bailey wrote:

@IanL-S Not sure how I ended up in the 2017 forum... Sorry about that!

It is easy to do Tom - I am constantly having to confirm which forum I am looking at - can be important as things work differently in different versions (and sometimes builds) of ATI.

Ian 

Hi guys,

I'm trying to restore an Acronis image into my newly purchased Dell laptop XPS 15 (2019) 7590. I am running the latest MVP Acronis WinPE Media Builder (v 18.6) to inject the RAID drivers as the SSD hard drive ain't visible otherwise.

The process with MVP works well until I am prompted to create the USB flash drive. I have an 8GB USB flash drive which I recently formatted and used to create the normal Acronis bootable USB without issues. When I select the drive in the options and type in the pertaining letter drive (D: in this case) the formatting process begins and then I get the following error:

ERROR: Failed to format "D:"; Diskpart errorlevel - 2147024809

Any ideas what to do to correct this and get the USB bootable drive properly created?

Thanks in advance

Joel

Bonjour,

Merci infiniment pour votre travail.

Après une journée de galère  en utilisant le win pe standard d'ATI 2020, j'ai découvert le Win pe MVP.

Explications: Avec la version standard il m'est impossible de faire une clé USB bootable !! si j'utilise une clé 2019, il est impossible de lire les .tib  avec l'information "fichier endommagé", impossible aussi d'ouvrir les fichiers protégés par mot de pass, "mot de pass non reconnu"  alors que je suis sur du mot de pass et de son écriture (malgré clavier qwerty)... J'ai cru que toutes mes sauvegardes étaient perdues !!!

Le MVP m'a permi de faire une clé bootable 2020, d'ouvrir mes fichiers de sauvegarde, d'avoir un clavier azerty. Une émotion toutefois : ma première tentative de récupération sur une sauvegarde en "diff" s'est soldée par un échec, avec un "conflit de mémoire". J'ai tenté la récupération sur une "full" et HURRA !!!

Encore Merci

You're welcome. I'm glad you found success.

Do you by any chance have a Windows 7 system? There is a known bug in the later versions of TI 2020 where the Simple option media won't boot.

Just wanted to give my two cents on this, just had to recover a raid system on my main PC, now am I going mad or is this software becoming less user-friendly and more buggy? 

The software allowed me to configure my point to point backup server by adding IP and subnet mask to my Mellanox fibre NIC, fair enough it shows as connected in PENetwork tool, but unlike older versions, the drive does not automatically show up as a share in file explorer or Acronis. I now have to manually add it as a network share first in file explorer, then further direct Acronis to it by entering in i.e. D:\Share\ and so on, until it finally shows :/

Also, in the older versions, my freshly configured RAID array (NEW OS Drive), which was initiated in the bios first,  used to show up as a drive as soon as WinPE booted, however, I must now open CMD and conduct diskpart malarky :/, never used to have to do that.

Hello,

i  made a WinPE Bootstick via MVP Tool and try to backup my encrypted drive.

I can unlock the drive via manage-bde (succes info) and access files via Filebrowser A43.

PROBLEM: Acronis still says Drive ist locked after refresh view or restarting Acronis App in WinPE.

The Message is the same as before unlock.

What could be the reason for this?

Thank you

What version of ATI are you using when creating the MVP rescue media?  This is a known problem that is meant to be fixed with the latest ATI 2020 #25700 version.

The fix is included in version 19.0. http://www.mechrest.com/plugins/MVP_ATIPEBuilder/Advanced/MVP_ATIPEBuilder_v190.zip

We are still waiting for Acronis to sign the new version. You may get anti-virus warnings because it has not been signed. It is safe to trust.

Mustang wrote:

You're welcome. I'm glad you found success.

Do you by any chance have a Windows 7 system? There is a known bug in the later versions of TI 2020 where the Simple option media won't boot.

 

Bonjour, je viens enfin d'avoir accès au forum!!

Ma réponse: Non, je suis sous W10 dernière version. 

Merci d'avoir porté intérêt à mon poste.

Cordialement

I too am faced with the issue that I cannot restore to my wireless Dell laptop using a Win PE USB boot stick as there is no wireless connection once started

AT THE MOMENT I can use the ethernet port but the next laptop will probably not have one and in fact my wireless speed is higher than the ethernet connection (well, it is in Win10 anyway)

I have followed this     https://www.acronis.com/en-us/blog/posts/power-user-insights-advanced-winpere-driver-injection-acronis-media-builder     and there are no errors shown in the log but I still cant get it to work - when booted I cant see my ethertnet connected NAS drive where the backup is stored nor any other computers and my router doesnt show a wireless connection so am assuming it hasnt connected.

David,  I would download the specific drivers for your system from Dell, extract them and inject them when using the custom builder (select the entire extracted folder).  Just make sure that you get the drivers to match your WINPE - the drivers need to be the same...

i.e. if you have a Windows 7 OS, but build Windows 10 Win PE, inject Windows 10 PE drivers into your Win10 PE build.

Dell drivers are from the manufacturer here:  https://www.dell.com/support/article/en-us/sln312414/dell-command-deploy-driver-packs-for-enterprise-client-os-deployment?lang=en

You can try to use Dell's generic WinPE driver CAB (extracted) or you can try to use Dell's specific model driver CAB (extracted) - don't do both - it's too many drivers and likely to cause conflicts.

Alternatively, and I'd suggest having one on hand anyway, is pick up a cheap USB to ethernet adapter from Amazon (gigabit).  They can be lifesavers for any system that only has wifi.  

Example:

https://www.amazon.com/Matters-adaptador-Gigabit-Ethernet-velocidad/dp/B00BBD7NFU/ref=sxin_9?ascsubtag=amzn1.osa.798c4fba-4dbc-4248-b6c6-406bfd5aa3d7.ATVPDKIKX0DER.en_US&creativeASIN=B00BBD7NFU&crid=3F5JVNEKOL7UF&cv_ct_cx=usb+to+ethernet+adapter&cv_ct_id=amzn1.osa.798c4fba-4dbc-4248-b6c6-406bfd5aa3d7.ATVPDKIKX0DER.en_US&cv_ct_pg=search&cv_ct_wn=osp-single-source&dchild=1&keywords=usb+to+ethernet+adapter&linkCode=oas&pd_rd_i=B00BBD7NFU&pd_rd_r=be91d69e-e63d-4557-b8e0-bc53a3bd86d1&pd_rd_w=1ZVqn&pd_rd_wg=oMcYu&pf_rd_p=ad792221-7c05-4384-852b-971b142fa109&pf_rd_r=S857JVTW32W62WMEFQAK&qid=1594140000&sprefix=usb+to+ethernet%2Caps%2C246&sr=1-1-72d6bf18-a4db-4490-a794-9cd9552ac58d&tag=rsonsite-20

Of course, if you need USB C, then grab one of those instead.  

In most cases, these are plug and play with Windows 10 or Windows 10 based WinPE.  However, if they don't pick up, the manufacturer will usually provide drivers as well.  

Good day,

Thank you for nice product, it really help alot.

I have new precision 7550 and existing IRST drivers dont work with it

Would you please help, what folder must I put new custom drivers ?

must I delete exiten drivers from IRST folder?

I found this drivers are working with new 7550

Intel-Rapid-Storage-Technology-Driver_57C0H_WIN_17.8.0.1065_A00_Win10-x64\iaStorAC.inf

12/11/2019  03:54 PM         1,917,440 HfcDisableService.exe
12/11/2019  03:54 PM            11,927 iaAHCIC.cat
12/11/2019  03:54 PM            15,131 iaStorAC.cat
12/11/2019  03:45 PM            27,150 iaStorAC.inf
12/11/2019  03:54 PM         1,339,360 iaStorAC.sys
12/11/2019  03:54 PM            74,208 iaStorAfs.sys
12/11/2019  03:54 PM           221,696 iaStorAfsNative.exe
12/11/2019  03:54 PM         2,900,480 iaStorAfsService.exe
12/11/2019  03:54 PM           115,168 Optane.dll
12/11/2019  03:54 PM            24,544 OptaneEventLogMsg.dll
12/11/2019  03:54 PM            27,104 RSTMwEventLogMsg.dll
12/11/2019  03:54 PM         2,241,536 RstMwService.exe
12/09/2019  07:10 PM           630,784 ShellPackage.msi

Thank you

All you need to do is go to the \Drivers_Custom\x64\IRST folder and delete all the existing files. Then copy the driver files you show above to that folder.

I'm trying to restore an Acronis image onto my Windows 10 Dell XPS 8930 for the first time. Starting from Acronis 2017 inside of Windows, this does NOT work. After restarting, Acronis loads, then says it is "Preparing". After several minutes, the system boots back into Windows, but the backup image was NOT restored. I am pretty sure that it does not recognize my Samsung 970 EVO Plus SSD. 

Next, I tried building a boot CD using the standard Acronis ISO file. I verified that it can see the SSD that came with my Dell XPS 8930, but it does not recognize my Samsung 970 EVO Plus SSD. That is where Windows 10 is installed, and also where all of the Acronis backup images are located.

I tried running the latest MVP Acronis WinPE Media Builder (v 18.6) to inject the necessary SSD drivers. But I can't boot from that WinPE disk. It simply does not appear as an option at boot time. Same thing happens with USB media.

I also tried using the Acronis Media Creation tool to create the "standard" Acronis WinPE. That CD also does not appear as an option at boot time.

Rick, see my reply in your other topic on this same issue.

I've tried so many ways to get Acronis True Image to boot from a USB but can't get it to work. I thought this tutorial would solve my problem but it still won't load. I get error code 0xc000000e and PC doesn't start up Acronis. I created a bootable USB key a few years back and that works perfect with all PC's to date and I've been able to recover whole disks with no problems, but now with the M.2 PCIe NVMe Solid State Drives, the destination folder doesn't show the correct drive. What am I missing with the old USB, or what do I need to do to get the new USB created from this tutorial to boot correctly? 

I'd like to host my local backups on a bitlockered volume, and be able to do bare-metal recovery from said volume.  My operating disks are NOT bitlocked (they're SEDs)--only the backup volume will be.

Questions:

1.  Will this tool do what I want?

2. Will it work with 2016 (how do I find out if my build is latest enough to work with this tool)?  If the script runs without errors does that mean my media will work as well?

3. Do I need to install Windows ADK to integrate BL support?

4. Will it work with TI 2021?

Thanks for all the great work on this.

Above questions replied to in topic: Questions about MVP Win PE Builder

Mustang wrote:

The fix is included in version 19.0. http://www.mechrest.com/plugins/MVP_ATIPEBuilder/Advanced/MVP_ATIPEBuilder_v190.zip

We are still waiting for Acronis to sign the new version. You may get anti-virus warnings because it has not been signed. It is safe to trust.

Hi - this link (from the forum doesn't work) does work when copy/pasting the URL separately.

I was able to struggle thru the creation of v18.6 but would love to use the latest version assuming it helps me overcome some of my observations in the process (e.g. WiFi works but can't connect to a NAS folder; don't find how to change keyboard layout; some "access denied" messages.

Now that I got the build will try and update how it went.

Thank you

David

David, have you tried just clicking directly on the link to the v19.0 version - this is working for me when I do so from my Firefox browser!

David, have you tried just clicking directly on the link to the v19.0 version - this is working for me when I do so from my Firefox browser!

Thanks Steve - yes I tried and that didn't/still doesn't work with Chrome, but workaround copy/paste does work.

--

Anyway, on v19.0 I still have the same issues (main one being WiFi working but cannot map network drives) as with v18.6, although I tried all 3 obvious modes:

1) WinRE-based w/ custom drivers for LAN and WiFi added, Win10 ADK installed, WinRE WIM extracted

2) went on with WinPE-based media, generated on different machine

3) lastly, tried WinPE-based, generated on the target machine - while #3 seemed most logic/likely to work, extracting/adding drivers from the target machine, this still didn't make me overcome the issue.

Also got several "access denied" and "writing to USB failed with diskpart message "-(minus)largenumber" (the USB drive is formatted, but the ISO not deployed (workaround use Rufus or similar tools).

As a result I can start WinPE's network services, can enable WiFi, see all WiFi networks around, can connect. Pinging the server I want to map a drive to also provides responses. But neither in Network Explorer, nor from command line in the media I can map the share (works perfectly from Win10 so no credentials issue) for accessing the TIB image (for future recovery).

My main questions:

a. is there a way to "debug" the scripts, a verbose mode for messages to see which steps actually fail?

b. saw a note about WiFi not working in more recent Win10 versions - what does "not working" mean - are the symptoms I see pointing to this potentially being the reason? I was thinking that if WiFi generally works, finds networks, then this would not be the reason, but of course, what do I know...

c. any other ideas?

Thank you
David

David, more questions than answers here...

When you are booted from the rescue media, are you connected to your wireless network?

Have you tried mapping a network drive manually in a command prompt window in the rescue media environment?

I personally have never bothered with using the option to Map a network drive when creating the rescue media using the MVP tool, but have done this successfully from the rescue media command prompt after confirming that I am connected to my wi-fi network and have been given a valid IP address using 'ipconfig'.

Take a look at forum topic: System error 1231 when in MVP WinPE environment attempting to connect to a network share where another user had problems with mapping network drives from the MVP media and it was eventually resolved!

Thank you all for this excellent project, and thank you Steve for the pointer relative to the map drive problem. Even though my issue was sitting a bit deeper, reading through the reference you gave, somehow encouraged me to investigate more deeply :-).

So hopefully the below can helps others, who as I might be constrained by having only WiFi and no Ethernet connection available on the target machine (HP Envy x360), and landing here only because the default ATI2019 Linux-based recovery medium fails to boot (likely due to dedicated AMD GPU), and none of the existing hints around BIOS settings helped: CSM already was disabled, and the recommended settings simply don't exist on that laptop model.

After going thru all the steps again freshly, here are the key bits that resolved things for me:
- "Access denied"s were caused by Antivirus on top of the already disabled Acronis Active Protection, so disabled it.
- WinPE w/ ADK (and extracting drivers) allowed to switch the keyboard to local language, but failed to lease an IP to the WiFi device (no matter what I tried, PENetMgr would show me the device and available networks, and attempt to connect, however IPconfig would always show "media connected").
- Finally, identified which drivers were extracted by the WinPE/ADK route, got the original driver files from Realtek and prepped WinRE with that - surprisingly this did the trick (while WinPE-created media still got stuck).
- Now in general, MVP PE Builder, at the time it loads map.cmd etc, seems to assume that a network connection is already established, i.e. either assumes Ethernet exists or that Wireless services got the WiFi profile loaded. However in my case, this never worked, though the profile is available and I no longer see any errors. I still need to first go thru several steps in PENetworkManager to connect to the respective WiFi network, get an IP assigned, and thus establish a connection. This isn't solved by increasing the timeout, and loading the map.cmd will obviously fail for no obvious reason presented to the user.

Ideas for MVP PE Builder:
- create an FAQ that brings together the most important steps/prerequisites, and use cases. The documentation seems a bit fragmented, and if the advanced version completely superseded the Basic version then why keep both in first place (maybe it's only me being confused though ;o))
- when a user selects "WiFi support = yes", put a logic to not load "map.cmd" but provide a message to the user to first establish the connection. And if there any tools that make WinRE "push" a wireless connection, trigger these or add some checks whether this completed successfully.
- update the version of PE Network Manager, there have been a couple of releases improving usability
- update the version of gparted, it fails creating USB media (shows error, doesnt deploy files, though formatting worked)
- nice to have: local keyboard support (not sure possible with the WinRE solution)

Thanks again and my case is closed.
David

When I run the tool as Administrator and select "Build from Installed ADK", it says "You chose [1.] ADK Media Builder" and then the program exits.  I have installed the Windows ADK for Windows 10.  Not sure what I'm doing wrong.  I have a SurfaceBook 2 from Microsoft.

Does this work with SnapDeploy6? I'm getting an initialization error when loading it up. No errors during the creation with the tool though. I uninstalled SnapDeploy6 and put SnapDeploy5 back on my machine and it works flawlessly, with the only change being the Acronis version.

This MVP app has been superseded by MVP Assistant - New 2.0 with Rescue Media Builder (New Version 2.6.1). You should also look at this thread as well: How to use the MVP Tool with Acronis Cyber Protect Home Office to create WinPE/RE Recovery Media. Snap&Deploy 6 may have introduced similar changes.

Ian