Guide to Add Drivers to WinPE Recovery Media
If you made WinPE recovery media and found that your hard drives are not show in True Image 2016 after booting the media, you may need to add additional drivers to the WinPE to support your hardware. The first thing you should know is that Acronis has you download and install the Microsoft ADK for Windows 8.1. You should uninstall the Windows 8.1 ADK and download and install the Windows 10 ADK from https://msdn.microsoft.com/en-us/windows/hardware/dn913721.aspx . You will find the download link for the Windows 10 ADK at the bottom of the page. This will give you the latest driver support provided by Microsoft. Remake the recovery media and try again. If it still doesn't work, you need to add a driver to the WinPE.
Follow these steps to add a driver to the WinPE recovery media:
1. Create the WinPE media on a USB flash drive. This is much easier to deal with than a CD or ISO file.
2. Create three folders called C:\Temp, C:\Drivers and C:\mount. Copy the boot.wim file from the sources folder of the USB recovery media to C:\Temp. Copy the driver files to C:\Drivers. See Tip 1. below.
3. Go to Start Menu/Windows Kits and right click on "Deployment and Imaging Tools Environment". Select "Run as administrator".
4. Enter these lines (one at a time) in the command window that opened in step 3. See Tip 2. below.
dism /Mount-Wim /WimFile:C:\Temp\boot.wim /Index:1 /MountDir:C:\mount
dism /Add-Driver /Image:C:\mount /Driver:C:\Drivers /ForceUnsigned
dism /Get-Drivers /Image:C:\mount (This line will return 3rd party drivers added for confirmation.)
dism /Unmount-Wim /MountDir:C:\mount /Commit
5. Copy C:\Temp\boot.wim to the sources folder of the USB recovery drive replacing the existing boot.wim.
6. Reboot the USB recovery drive and see if True Image 2016 can see your hard drives.
1. Microsoft can only add drivers from .inf files. You must put the .inf file for the driver and all the files listed in the [SourceDisksFiles] section of the .inf file in the C:\Drivers folder. Inf files can be opened by notepad.exe to look at the [SourceDisksFiles] section. You may add more than one driver to the C:\Drivers folder. Each driver can be in a separate folder. DO NOT PUT ANY SPACES IN THE FOLDER NAMES.
If you are using a 64 bit Windows system, you can find the .inf file or files (there may be more than one) in C:\Windows\INF. There is an easy way to find these files. Start by looking in Device Manager for the device. In most cases you will be looking for a Storage Controller. Also look under System Devices and USB Controllers. You may need to look in more places. When you find the device, right click on it and select Properties. Click on the Drivers tab. Click on the Driver Details button. Write down the name of a .sys file listed. These files listed should be the same as those listed in the [SourceDisksFiles] section of the .inf file. Open Windows Explorer and highlight C:\Windows\INF. Place the cursor in the Search box. Click on the Search tab in the top left section. Click on the Advanced Option button and place a check mark next to File contents. Now enter the name of the .sys file you wrote down. Inf files containing that .sys file should appear. The .inf file will probably have a name like OEMxx.inf, where xx is a number. You can rename the file to match your device if you wish. It will work either way. Place the .inf file and all the files listed in the [SourceDisksFiles] section in C:\Drivers.
2. If you are running Windows 10, you can use the Copy and Paste functions in the command window to enter the lines listed in Step 4. above. In earlier versions of Windows, you must type the line yourself. If you make a mistake and get an error message, you can use the up arrow to display the line again instead of retyping it. Then use the left and right arrow keys to make corrections and try again.
3. There is a guide to produce a French WinPE with or without added drivers at reply #30 below provided by 100PIER.
Nice job Paul, this should prove most beneficial to the user base!
That took a considerable amount of time and detail and not qkuickly thrown together. Thank you and many can benefit.
Grovers status = Inactive 1. Grover's New Revised Guides 4. 2014 Cleanup 2015 Cleanup 5. Attachments/How 7. TI 2015 FAQ.
2. Create BKU Tasks > 2011_2012_2013 2A. Using 2014 6. Help 2016 2015 2014 2013 8. Stop Scan for Backups 8A. ATIH Video's
3. Create new disks-Guides. 9. Register/Downloads 10. Mustang's New Guides 11. Les Seiler's Backup Video
in addition there is an Gui for Dsim available that may save some trouble and give freedom to the Gui friends like me ;-)
Didnt check this with W10 ADK but may worth a try....
"If you are using a 64 bit Windows system..." WinPE and Acronis are still 64bit if created with ATI2016 right?
I tried the GUI DISM under Windows 10 with the Windows 10 ADK. It worked very nicely. I do find it quicker to use the command line under Windows 10 with the copy and paste functions. For those running under Windows 8 or 8.1, the GUI version is worth it to save all the typing at the command line. It certainly is a nice tool. Thanks for pointing it out.
ATI2016 can only make a 64 bit WinPE, so you need to add only 64 bit drivers. For those running on a 32 bit Windows, drivers can NOT be taken from the system.
Created Acronis rescue media per your recommendation, Mustang. Installed Windows 10 ADK, then burned the image. Acronis TI 2016 backs up all partitions of my SSD, but after restoring back, the operation system is missed such as Windows installation directory is locked. Situation confirmed with 3 SSD of different type manufactured by different companies. I have tried to restore the backup images on the same SSD with the same hardware. Skipping new Samsung SSD 950 Pro (we can have a problem with the driver in theory) other two SSD are plain SATA disks, one is Intel 530, another one is SanDisk Ultra II. In my understanding Windows 10 locks SSD due to some unknown reasons - such as no new SSD was used for restoring. Do you have any solutions? BTW I truly believe that Acronis TI 2016, as well as it's predecessors, doesn't function how customers expect it to function, is it Microsoft's problem, Acronis's problem, or cross linked problem between them, I don't know.
I wish I have used Clonezilla and didn't spend $29.99 for upgrade to Acronis TI 2016 and then $29.99 for upgrade to 3 PCs (2 of them are non functional ATM due to locked SSDs). Samsung Migration actually didn't work for my SSD 950 Pro correctly as well - it cloned Windows partition only ignoring 100 MB boot partition and the disk is bootable only manually when CD with boot partition is present.
I truly believe Microsoft has to provide the disk cloning online service for free, locking or erasing data on an old SSD and automatically activating / signing the new one, but it is a dream - they want us to buy as many licenses as possible.
thanks for your help anyway!
I just want to extend an enormous thank you for your clear and methodical guide for making a bootable recovery disc. Although I have never had problems before and am running TI 2016 on a desktop and MSI laptop. The MSI laptop died and I replaced it with an Aorus X7 Pro-sync. That sucker would not boot from a normal Acronis recovery disk no matter what I did. It has a UEFI secure boot that and I variously disabled security keys, turned to legacy OS boot and all combinations thereof. Then when I tried to create a WinPE recovery disk I ran into the problem reported by many running Win10 and the new ADK.
After a load of frustration and web searching (duh!!) I finally came across your fix on the forum. What a great job. I know that many Aorus owners have run into the problem and I hope they turn to this.
Great work, thanks
Thanks for taking the time to write the guide, it has been very valuable.
I followed your instructions by running adksetup on the Windows 10 Kits and Tools page but for some reason after the installation is complete the Acronis WinPE builder doesn't recognise it as being installed and wont let me proceed. The only thing that I can see that MIGHT have changed since you wrote your article is that the ADK version is now at 1511 which has only appeared in the last few days.
Has anybody else tried to build a WinPE envrionment using version 1511 of the ADK?
Acronis doesn't work with the 1511 ADK. You can download the original Windows 10 ADK from post #28 in this tread https://forum.acronis.com/forum/102723 . The Acronis Media Builder will work with the original Windows 10 ADK.
Thanks for the tip! I will give it a try.
This all worked as you described and I even managed to install the storage drivers for my Samsung SM951 NVMe SSD.
The only problem I have now is that the PC in question is a brand new Dell XPS 15 (9550) complete with a 4K UHD screen. Clearly the WinPE environnment was never designed to cater for this resolution so the resulting screen is very hard to use with most drop down menus completely invisible. I suspect that I will need to research this a little more to either add graphics drivers or find a WinPE resolution parameter (if one exists).
Still, I am a lot better off now than when I fisrt started.
thank you so much for your instructions ! You deserve all the merits I can give.
Found this thread just this minute and though still doubtful as to whether - say a person who has worked with PCs for years - but has never created a WinPE boot stick such as myself -stands a realistic chance of getting somewhere in a reasonsably short time.
I'd greatly appreciate your honest feelings whether yes or no.
Yes. It is very simple.
1. Download and install the Media add-on found under the Free Plugins tab in your Acronis account under TI 2016.
2. Download and install the Windows 8.1 ADK. https://www.microsoft.com/en-US/download/details.aspx?id=39982 Install only WinPE and Deployment tools.
3. Run the TI2016 Media Builder and select WinPE. Select your USB stick for destination. You will probably not need to add any drivers.
Perhaps you can clarify a 2016-6027 WinPE point for me. The majority of my PCs run W7 x86 due to the lack of x64 drivers for a ton of periperhal HW w/o x64 drivers. Non the less, I'm confused by a statement about creating a WinPE rescue disk as referenced in the latest 2016 manual. (on page 116 it states "Acronis Media Builder supports only x64 WinPE 3.0, WinPE 4.0 and WinPE 5.0. This WinPE distribution cannot work on x86 hardware). Are they refering to if I want to ADD drivers, or in general. Simply, can it be true that ATI2016 will not allow me to create a "standard" x86 winpe rescue disk?? Or have I misunderstood?
You can't create 32 bit WinPE with either TI 2015 or TI 2016. You would need to go back to TI 2014 to be able to create a 32 bit WinPE. I my opinion, this is a major flaw in the product. Acronis should have provided the option to create both 32 and 64 bit WinPE. They did this with DD12 and Universal Restore. Why not with True Image?
it seem that ATI 2016 Buiild 6027 for Acronis Media Builder it use Windows Kits 10 ADK 10.1.10586.0 and Acronis Universal Boot media use Windows Kits 8.1 ADK 8.100.26866.0 when i run ATI 2016, Tools menu to create the media.
how can i use the menu option to make Acronis Universal Boot media to use Windows Kits 10 ADK and not from command line?
You need to install the latest UR from your account. It has been updated to use the 10586 ADK.
how can i check which UR version i am using and what is the current version?
See reply #8 in this thread https://forum.acronis.com/forum/107262 .
I have Acronis 2016 build 6027 FRench version I have downloaded from my Acronis account.
I run W10 x64 Home FR version, all my internal medias are SSDs devices: (i750 NVMe (OS), SM950 NVME, 840 PRO Raid 0, 850 PR0).
I am trying to build a bootable WINPE USB key using the media builder French version v11.5.40010 I downloaded from my Acronis account..
1) I succeed to create a standard bootable media with Method 'USB key' or 'File .iso + Rufus
Booting succeed only with 'CSM enabled'.
Unfortunatly I always get an english version displayed.
With previous build (5634) i got a french bootable media version.
Do you have an idea why this regression come from, and how to fix it ?
2) The UEFI boot of the USB key never works and I got Error "0xC0000428" Blue Screen.
How to fix this problem ?
3) Trying to build the USB bootable media via "File .wim + ADK W10 + MakeISO + Rufus v2.5" never succeed.
I see no "Trueimage_starter.exe" command line displayed and nothing happen !
Any idea to fix this problem ?
4) If I succeed Step 3, i plan to inject NVMe Samsung driver v1.4.
Before trying to inject drivers i would first valid the ADK procedure, but without success at this day.
1. Are you saying that the True Image 2016 app displays in English. If that is the case then Acronis changed what version they included in the WinPE files. You would need to see if Acronis would send you the French version of WinPE.zip to put in the C:\Program Files (x86)\Acronis\TrueImageHome\BartPE folder.
2. At the blue screen hit the F8 key to see Startup options. Then hit the F7 key to select the Disable Enforce Driver Signature option.
I use W10 x64 Home FR v1511.
I have downloaded the ADK v10.0.26624. Is this the correct version or do I have to uninstall it and then replace it with ADK for v1511 ?
I use "AcronisTrueImage2016_addons.exe" v126.96.36.19927 , is it correct ? I don't see on my account any '.xxx_addons_FR.exe' file. Do you think a specific 'addon' file should exist for each language ?
I have installed "AcronisTrueImage2016_ur_fr-FR.msi" downloaded from my Acronis account. Is it correct ? In 'Properties' of this file there is no version indicated clearly.
When using AcronisTrueImage 2016 under W10 x64, the apps appears properly in french.
Building the Boot media via "Tools" menu is in french.
However, the builded Boot media on USB after booting displays in english. The 'about' displays 'build 6027'. (see "bootedmedia.jpg" attached).
With previous build i got a french display. (see "boot5634.jpg" attached).
When trying to build an USB via the ADK procedure (but without injected driver) the booting of the produced USB key never complete.
The screen stops (see "boot_stop.jpg").
So, what to do ?
On the "428" error i did some progress: the "F8" key, StartUP, "F7" key, "Disable Enforce Driver Signature Option" works fine.
However, I got a new error message when trying "Properties" option whatever the disk is selected. Test done with 5634 build. (see 'propertiesbug5634_x.jpg')
I can't help you with the language problem. As I said the WinPE.zip file includes the TI application. You will need to open a support ticket with Acronis to inquire about how to get the French version. Acronis may have a mistake on the download page in your account where they have supplied the English version instead of the french version.
The ADK you are using is okay.
Don't worry about injecting the Samsung NVMe drivers into the WinPE. The ADK you are using has native NVMe support. You should be able to see your SSD's in the English version you have been able to boot.
Two bugs Win 7 machine and 2016
1.) When upgrading from 2015 to 2016, downloading the latest addons and universal restore install files and applying them, and installing Win10 ASK, got this error during WinPE media creation process:
""X Failed to copy the product files.
Link to KB with error code""
There is no error code when the link is clicked, tried old and new versions of Win10 ASK, no difference, ONLY when I uninstalled the addons and universal install and then applied them again did it work for the DVD.
Your prograsm should properly track versions of these addons and forces an unistall when necessary !!!!
2.) While the DVD works, the USB created does not
A- will not boot when ""Generic Flash Disk "" selected, will boot when ""UEFI Generic Flash Disk"" selected but get error as in attached file.
What does this mean??
It's not my program. I don't work for Acronis. I just try my best to help people.
With the excellent help in this thread and ALOT of reading online, I finally managed to make an Acronis recovery USB boot disk that sees my Samsung nvme m.2 drive!
I made an iso that I still need to test but if others would like it, I'll post a link to download it from my server.
ATI version 6027 was last used. I have moved on to other backup means until (maybe) some day Acronis fixes their software.
System: ASUS Z170 Deluxe and i7 6700K, 16 gig DDR4, Asus GeForce GTX 980 TI, 250 gig M.2 NVME boot
On my side:
I have installed Acronis add-on v11.5.40010, and ADK W10 v1511.
1) I succeed ONLY making USB WinPE boot drive via the 2 possible 'standard' process (from Build Acronis 2016 6027) :
Media Builder -> File .iso -> Rufus -> USB key
Media Builder -> USB key
However the media boot appli is only in english. (Acronis is working on the problem, with previous Acronis 2016 build the boot media application was in the right language).
The boot media detects any NVMe SSD (SM950 PRO, SM951, i750). No need to inject any NVMe driver, the W10 ADK 'in the box' driver is sufficient.
2) I NEVER succeed making USB WinPE boot drive via the 'advanced' process:
Media Builder -> File .wim -> MakeISO command -> Rufus -> USB key.
Even with no injection driver the builded media boots but ATI application never start. (Acronis is working on the problem).
I'm stuck at a point here in testing my recovery of the NVMe because when I recover the image of the NVMe to a SSD drive or a spinning drive, it will boot almost to windows but the screen blinks and never completes booting. I'm guessing this is because I'm trying to restore to a non-NVMe disk but that is really only a guess. What I need is another NMVe disk to plug in, restore, then see if it will boot. I'm not ready to take a leap of faith by restoring the only NVMe drive I have.
Any volunteers to test my iso?
ATI version 6027 was last used. I have moved on to other backup means until (maybe) some day Acronis fixes their software.
System: ASUS Z170 Deluxe and i7 6700K, 16 gig DDR4, Asus GeForce GTX 980 TI, 250 gig M.2 NVME boot
I have send you a PM. I can also test your iso, no problem.
I have produced a specific GUIDE for french people to build a Rescue Boot Media with W10 v1607 WinPE , with or without additional driver(s).
I have UPDATED the Guide according to ACRONIS 2017 Beta 2 Build 3070.
My GUIDE is attached in .pdf format.
'Danfilipi', can you please send a link so I can download your ISO?
Thanks a lot!
Your info was a big help today, thank you Paul!
Process worked perfectly for creating drivers in the media. Great post. No errors. Thank you.
Are you refferring to my guide specific to french versions ?
The very long boot up time I observed (6 to 8 minutes) seems due to USB driver encapsulate in the boot media software.
With USB 3.0 key the boot up time to access to Acronis Media Main Menu is less than 15 s, and with some USB 2.0 key is up to 8 minutes...
Using the direct (no driver injection) method the USB key media boot up is less than 20 s whatever the USB key you use.
Just the first post in the thread - I needed to get this working quickly and that post got my WinPE boot environment with SSD driver up and running ultra quick.
My boot time to Acronis is about 15 seconds - but now I can actually do a backup too. :-)
Great write-up. Thanks for the clear instructions.
I was able to add Intel I217-LM network driver to the WinPE recovery media using your instructions. I am able to boot the updated recovery media in UEFI mode or Legacy mode, but the network driver only seems to work in the legacy mode.
Booting in the legacy mode, the NIC automatically gets a dynamic IP address from a DHCP server. I am able to connect to my Synology NAS using
net use * \\synologynas
Synologynas is the hostname of my NAS. After entering username and password, it mounts the NAS as the next available drive letter.
Booting in UEFI mode, the PC is assigned a 169.254.x.x IP address. My home router is set to assign IP's of 192.168.2.x. The driver seems to be loaded but it can't ping anything outside of the PC's own IP address. See the attached screenshots.
Any idea how to make the network driver work in the UEFI mode? I've tried to manually configure a static IP in the 192.168.2.x range, but the PC still can't ping anything besides itself.
Please can you add in your head threat a reference to my guide wrote in french (see POST #30) , which is specific to W10 French ADK v1511 version ?
FYI Acronis will fix the boot media language issue (only english supported at this day) for the next ATI release.
A reference to your guide has been added.
I don't know why that would happen. When I boot UEFI, I get a 192 based ip. I would be looking at your router for a possible answer.
Has anyone had any luck with using ATI16 to image NVMe in RAID?
I have a ASUS Z170-WS with dual m.2 PRO 950 Drives. I can see them individually when not in RAID. I can see them with AOMEI and Reflect in RAID. But not Acronis , yet. I have used this guide to successfully add the IRST drivers that are needed to WINPE bootable, but still cannot see the RAID in ATI16. Any thoughts?
If I try to understand your message you have build a RAID 0 machine booting well W10 x64 based on dual m.2 PRO 950 SSDs (NVMe).
Is it correct ?
Or do you use the dual RAID 0 SSDs for datas backup/restore only (non booting OS) ?
By the way, do you use a modded BIOS for your ASUS ?
What exact IRST drivers do you use ?
If I understand you can do backup/restore RAID 0 SSDs using AOEMI software (I use also this application) under W10 WinPE.
Is it correct ?
What is Reflect ?
Do you have tried first to build an Acronis WinPe boot media without any iRST additional driver injection ?
I am running Win 8.1 perfectly fine on RAID 0 950 Pros.
I am using a pre-release BIOS 0504, supplied from ASUS themselves (althought it's also fully functional with the 0503 on asus website).
I am using latest IRST drivers 188.8.131.522 form Intel website
I can backup/restore using AOEMI ( or at least see the RAID 0 drive AND Backup , I have not restored yet)
I am reffering to the Macrium Reflect software
I have tried WinPe without iRST drivers. Win8.1 Based, Win 10 based. Pretty much every combination.
Thanks for your reply, I am glad to answer any further questions
Here's something to try. Take boot.wim from the Macrium recovery media and substitue it for winpe.wim in the ADK.
1. Go to C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us and rename winpe.wim to winpe.orig.wim.
2. Copy boot.wim from the Macrium media to the above folder and rename it to winpe.wim.
3. Rebuild the Acronis WinPE media. It should work because all the necessary drivers will be in place.
What ends up loading up, however, is not True Image, but a reflect environment.
I have given up on Acronis for now, since their support claims that this is coming on the next build... Waiting to see. In the meantime I am using Macrium Reflect for my current NVMe raid imaging needs
The last IRST drivers are v184.108.40.2066 (see www.win-raid.com Fernando site).
AOMEI WinPE boot media and ATI2016 WinPE boot media are very similar solution.
The both solutions should work on your system.
Did you try to build an AOMEI boot media (USB key) based on WinPE without iRST driver injection ? and with iRST driver injection ?
Does it work on your system ? You should see the system OS RAID 0.
If AOMEI solution does work there is no hardware/firmware problem and ATI2016 solution should work.
If both AOMEI and ATI2016 solutions does not work the problem is maybe more 'hardware/firmware' than 'software'.
I have no experience on Macrium backup/restore solution.
AOMEI works. ATI does not. I know, it sounds really weird but that's what I see so far
I just tried it. It works.
The Macrium environment loads. You then double click the PE Explorer icon in the lower left corner. Then navigate to X:\Program Files\Acronis\TrueImageHome and double click TrueImage_starter.exe to run TI.
You can make TI open on boot simply by deleting WinPEShl.ini from the Windows\System32 folder of the WinPE. TI will run from X:\Windows\System32\startnet.cmd. I also tried that and it worked.
The reason I suggested this approach was that I thought it would be much easier for you than loading the correct RAID driver to the Acronis image.
Good afternoon all. Great post mustang but i still TI still cant seem to see my drive. I have done your steps 15 times and i still can figure it out. Do you by chance know the drivers that are needed for this to work. Iv been working at this for to long now but i hear that the M.2 drives are worth it. Please and thank you.