Guide to building a 64 bit UEFI Secure Boot WinPE 5.0 CD or USB Flash Drive running TI 2015 and Universal Restore with DD12

Can WinPE be built on Win 7? Once this is built on Win 8, will the CD/USB Stick work on Win 7?

It has not been tested on a Windows 7 system. It may work.

Once built on a Window 8 system, it will work on any system using a 64 bit capable processor.

Hello Mustang,

Thank you for the great contribution in making our lives simplier. I did recently purchase a Microsoft Surface Pro Win 8.1 x64 Tablet, but I found out that the normal Acronis Boot Disks don't work at all - obviously due to drivers missing. I then came across your post on how to create a winpe secure boot x64 usb for uefi systems and I must say it helped a lot. In working with your instructions I found the following discrepancies:

In DiskDirector "\Files\snapapi.dll" is actually located in "\Files\Drivers\snapapi.dll" so the renames should happen within the "Drivers" subfolder. I kept both snapapi32.dll and snapapi64.dll in that folder instead of the upper level one indicated in your instructions and I must say DiskDirector worked just fine.

However when it comes to TrueImage 2015 v18 Build 6055, I must confess I've hit the wall. It opens just fine, but when I instruct it to run the backup operation it suddenly pop-ups an Application Error warning that says the following:

"The instruction at 0x14975190 referenced memory at 0x00000000. The memory could not be read"

See images:
http://imageshack.com/a/img903/2703/hXmbxg.jpg
http://imageshack.com/a/img901/8128/u6TOPP.jpg

It's an odd situation, because as much as I checked and double-checked and retried building my winpe iso I receive the same exact memory access error.

I booted using secure boot, then I disabled secure boot, I also deleted the Microsoft boot keyes to make sure nothing was interfering with my acronis winpe iso, but the same error occurs anytime I try to run a partition backup in True Image. I was merely testing the smallest of partitions 200MB and even in that circumstance I received the same error.

I did also follow the correct order in the plugins folder to make sure TrueImage is placed before Disk Director.

Overall I must say the usb boots just fine and Microsoft Surface 3 is not acting up like it did with other USB boot disks. However, the fact that TrueImage isn't working correctly is a big drawback. Any idea what might be causing the memory access error?

I just made a new win pe using the same settings but different drivers for my sony vaio windows 8.1 x64 MBR and the boot went fine, disk director works just fine, PENetCfg works flawlessly, but Acronis True Image 2015 doesn't work. It experiences the same memory access error:

See images:
http://imageshack.com/a/img673/1811/0Eb1yq.jpg

This definitely confirms my suspicion that it may be an issue related to the Acronis True Image Plugin. You might want to look into that.

Hi Heather,

Thanks for the feedback, I really appreciate it.

I have a suggestion. Try building MustangPE again. This time click the Advanced Options button and change the "Set WinPE scratchspace" to 64. See if that corrects the memory could not be read error. I've been making successful full disk backups with this setting.

I've corrected the Disk Director 12 instructions.

Hello Paul,

Ti ringrazio per la risposta tempestiva. Thanks for the prompt reply. Greatly appreciated. I tried as per your suggestion: setting WinPE "scratchspace" to "64", but I still keep having the very same memory access error. I thought perhaps it may have to do with the way the USB is formatted, so I then burnt the ISO into a CD. Yet another disappointment the CD Boot gave the same result.

Check the screen shots below:

USB BOOT
http://imageshack.com/a/img674/2656/GzEY1l.jpg

CD BOOT
http://imageshack.com/a/img673/158/ofrY21.jpg

Also I think there might be a problem with the settings in "MustangPEBuilder 2 ADK 64 LaunchBar", because anytime I select the USB drive to be created at advanced options, it doesn't actually apply it. The USB gets formatted but in the end is blank. So instead I would use rufus (rufus.akeo.ie) to burn the ISO into the USB.

Is there any alternative suggestion you might have? I am also thinking of wiping clean my windows 8.1 pro system and reinstalling windows, acronis and "MustangPEBuilder 2 ADK 64 LaunchBar" from scratch just to see whether that would make any difference.

Also if I sent you the Microsoft Drivers package and the ready organized "adddrivers.ini" could you create an iso in your system and forward it to me, so I could test that?

Sorry for taking your time with this, but I genuinely believe there's a bug somewhere and I would love to help out in creating a more robust solution, as your tool is much needed with the new PC systems out there.

Hi Heather,

The empty USB drive problem was reported here https://forum.acronis.com/forum/54130 see reply #16 for the solution.

What build of TI 2015 are you using? It should be build 6055. Make sure you uninstall the Media add-on and reinstall the Media add-on for build 6055 if you installed build 6055 over the top of a previous build. Check the build number of TI 2015 while booted in WinPE to be sure it is build 6055.

You should try building MustangPE with only the TI 2015 plugin. Do not include DD 12 or Universal Boot. If that makes a difference, it was a driver version issue.

Building MustangPE on my system should make no difference. Also, I doubt wiping your system and reinstalling the apps would make any difference.

Hello Mustang,

Thank you for your suggestions. I re-installed my windows 8.1 x64 system from scratch and installed the latest versions of Acronis True Image, Media-Add On, Universal Restore and Disk Director. I did run some tests and Acronis True Image 2015 v18 Build 6055 works just fine in my WinPE USB Key if I prepare it only with TrueImage and Universal Restore. Anytime I try this configuration, no matter what drivers I add to the WinPE True Image 2015 is working flawlessly and I leave "scratchspace" to "default", no need to change it to 64.

However, when I add DiskDirector 12 Build 3223 as the last plugin to be compiled (according to your instructions), TrueImage stops working properly and keeps giving to me the memory access error.

So, one, can certainly deduce that there's a driver issue in-between Disk Director and True Image that causes such an issue.

Having that in mind, I tried sorting the plugins differently. I put Disk Director first and then Universal Restore and True Image. And to my wonder, everything worked just fine. So I would suggest changing your guide accordingly, so that other people don't encounter the memory access anymore. The correct order should be:

plugin3=DD12\DD12.exe
plunin4=AcronisUB\AcronisUB.exe
plugin5=TI2015\TI2015.exe

Thanks,

Hi Heather,

Thanks for your testing on this. The solution is very simple. Put the TI 2015 plugin last in Plugin.ini. Let me know if all of the plugins work. If they do, I'll change the instructions in the DD12 ReadMe.txt file.

It's always been tricky to put DD and TI together due to Acronis changing the drivers from one version to the next. I wish they would stop having DD and TI share the same drivers. It's been a bad idea for a long time, but they just keep doing it.

Hello Paul,

You were right. I tried that before reading your reply and it worked. So I would suggest changing your guide accordingly, so that other people don't encounter the memory access anymore. The correct order should be:

plugin3=DD12\DD12.exe
plunin4=AcronisUB\AcronisUB.exe
plugin5=TI2015\TI2015.exe

Hi Heather,

I'm glad it worked. I'll work on the wording as it was necessary to put DD last with previous versions of TI. Now with TI 2015, DD needs to be before TI 2015.

Hello Mustang,

I have installed all the points of your guide (last release) and just before to run MustangPEBuilder64.exe, I had a look on the Windows events:

I have a lot of SideBySide errors in relation with DiskDirector.exe, SystemInfo.exe and RecoveryExpert.exe (see attachment).

Have got an idea to solve these errors?

abbreizh

Hi abbreizh,

I see two problems.

1. The Disk Director WinPE files need to be in the xxxx\Plugins\DD12\Files folder not the xxxx\Plugins\DD12\Files\Files folder.

2. It looks like you double clicked DiskDirector.exe to run it from the plugin folder. It won't run from there. I think that is why you got the SideBySide errors.

Hi Mustang,

I tried again to build a new C:\MustangPEBuilder_2_ADK_64_LanchBar program following your instructions and errors SideBySide occured when I renamed C:\MustangPEBuilder_2_ADK_64\Plugins\DD12\Files\Drivers\snapapi.dll to snapapi64.dll.

I also never double clicked DisDirector.exe to run it from the plugin folder.

abbreizh

I don't understand your situation. Please show me a screenshot of the folder C:\MustangPEBuilder_2_ADK_64\Plugins\DD12\Files\Drivers.

Do any error messages show on the screen when you rename snapapi.dll to snapapi64.dll?

Have you copied the 32 bit version of snapapi.dll to C:\MustangPEBuilder_2_ADK_64\Plugins\DD12\Files\Drivers and renamed it snapapi32.dll?

Are you able to run MustangPEBuilder64.exe?

- I don't understand your situation. Please show me a screenshot of the folder C:\MustangPEBuilder_2_ADK_64\Plugins\DD12\Files\Drivers.

See attachment: DD12 Files Folder.JPG

- Do any error messages show on the screen when you rename snapapi.dll to snapapi64.dll?

YES

- Have you copied the 32 bit version of snapapi.dll to C:\MustangPEBuilder_2_ADK_64\Plugins\DD12\Files\Drivers and renamed it snapapi32.dll?

YES

- Are you able to run MustangPEBuilder64.exe?

YES but I have errors too and can't generate WinPE 5.0 ISO. See attachment: DISM.log

I have no idea why you would get errors by renaming snapapi.dll to snapapi64.dll.

You found an interesting line in the Dism log:
Store: PID=4496 TID=5904 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

Are you able to create any WinPE disk on your computer?

Can you create a WinPE recovery media using the TI 2015 Media Builder?

Yes I can create a WinPE recovery disc using Ti2015 Media builder. See Attachment.

It runs very well .

Sorry, I have no idea what the problem is.

Hi Mustang,

Good news.

In order to solve SideBySide errors, I uninstalled then installed again Visual C++ 2005 Redistribuable packages (VCRedist.exe x86 and X64) and I was able to correct these problems .
Then, I tried again to run MustangPEBuilde64.exe to generate a WinPE 5.0 ISO on a CD and on USB Flash Drive.

It's Ok. Cd an dUSB Flash drive run very well.

The only problem I have, it's a language problem. Keyboard and regional settings from your WinPE media are English/US (qwerty) and I want French settings with Azerty keyboard.

To resolve that: I created a folder C:\Packages which contains all files coming from "C:\Program files (x86)\Windows kits\8.1\Assessment and deployment kit\Windows preinstallation Environment\x86\WinPE_Ocs\fr-fr".
I think "lp.cab" is the necessary file.

Question: How to configure, in your Advanced options, AddPackages.ini (package1=) and AddLanguages.ini (Langpath1=, Language= and Default language=)?

Thanks for your help.

Abbreizh

Hi abbreizh:

Very good. That's great news.

To add French language support and set French as the default language, configure AddLanguages.ini as follows:

[Language Paths]
langpath1=C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\fr-fr\lp.cab

[Languages]
language1=fr-fr

[Default]
Default Language=fr-fr

I tested the above and it worked.

If you want to add additional WinPE packages, other than language packs, specify the full path to the package you want to add in AddPackages.ini.

Example:

[Packages]
package1=C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-WMI.cab
package2=C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-EnhancedStorage.cab
package3=C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-SecureStartup.cab

The above would add support for Microsoft's Bitlocker.

Hi Mustang,

Great! It's Ok.

(amd64 folder for language path: I also have seen it).

Thanks a lot for your help.

Abbreizh

wow, interesting to read this thread, but, despite not being a rank amateur with computers, I'm having trouble even understanding the issue with this thread- is it relevant to all who have Win 8x and ATI 2015 or just some people with special needs?

I just purchased a new Dell with 64 bit Win 8.1. I currently own a family pack for ATI 2013. One of those 3 older PCs is now dismantled so I thought I'd install the 3rd on the new Dell, but read in another thread that 2013 won't work with Win 8x. Now I read all these complaints about ATI 2015.

Meanwhile, I'm trying to get a grip on the meaning of "64 bit UEFI Secure Boot WinPE 5.0 CD ". What exactly is that?
Joe

-
"It has not been tested on a Windows 7 system. It may work.
Once built on a Window 8 system, it will work on any system using a 64 bit capable processor."

This was a quote by Mustang from post #2 in this forum, in response to a question in post #1.

Is there any further information about possibly performing this build on a Win 7 system?? I really love the idea of this PE tool, but don't plan to move my two PCs to Win 8.1 for awhile yet!

I have attempted the Mustang PE Builder 2 with ATI2013 and DD11, but without success. I now have DD12, and if the build discussed here is possible on Win 7, I will buy ATI2015. (I hadn't planned on that yet, either.)

Thanks for advice..... Robert

I have tested the build on a Windows 7 Pro 32 bit system with the Windows 8.1 ADK, DD 12, TI 2015 (with the Media add-on and Universal Restore) installed. It worked as expected. I was able to build a 64 bit WinPE on a USB flash drive that booted the Windows 7 system and all three Acronis programs worked.

Mustang,

I was having trouble downloading your plug in and went looking at my SonicWall firewall. In the log it said the file was infected with Inject.FMKJ_9
It's probably a false positive but others may be having issues pulling the file.

Thanks for the guide!

Hi Walter,

It is definitely a false positive. The programs are written with the AutoIt 3 programming language. Anti virus software can't see inside, so a number of them brand all AutoIt 3 programs as a virus.

Hi Mustang,

A new version, build 6525, of Acronis True Image is available.
Does your Ti2015 plugin take into account the new version ?

Abbreizh

It works with the new version. All you need to do is extract the Files and Files64 folders from the new WinPE.zip file at C:\Program Files (x86)\Acronis\TrueImageHome\BartPE and replace those folders at C:\MustangPEBuilder_2_ADK_LaunchBar\Plugins\TI2015. Then build the recovery media again.

Ok, thanks a lot.

Abbreizh

Hi Mustang,

for your information, since the last version TIH2015 6525, Bitdefender Total Security 2015 (build: 18.19.0.1369) detects your plugins as virus.

The applications AcronisUB.exe and TI2015.exe have been deleted as potentially malicious. Active virus Control has blocked these process using this type of action. The behavior of these applications can damage your PC. (see attachments).

What do you think?

Abbreizh

As I mentioned in reply #26, anti virus companies have a problem with programs written in the AutoIt 3 language. There is a high level of encryption when the programs are compiled. They can not be decompiled, even by me. Earlier versions of AutoIt 3 used to compile using a password and could be decompiled using that password. That feature has been removed. Because the anti virus companies can't see inside the files, they report them as potential virus. This results in all the companies reporting a different virus signature.

I went through dealing with an anti virus company with the 64 bit version of the TI 2014 MustangPE plugins. See reply #31 in this thread https://forum.acronis.com/forum/54130 . It was a lengthy process that I am not willing to repeat. MustangPE is something I now do for free to help the community. I could just stop offering MustangPE to solve the problem. Let's hear from some users. If the consensus is the false positives age too scary, I'll withdraw MustangPE.

Hi Mustang,

It was just an information.

I understood it as false positives and I had already excluded the analysis of these processes in my Bitdefender Total Security.

I really appreciate your work and it would be a shame to deprive us of MustangPE.

Kind regards.

-
Certainly don't pull it! Many of us are very thankful for the efforts of yourself and others who provide many useful tools and procedures, and offer assistance with the problems so many of us encounter.

Speaking of which, I finally have this procedure running to what seems to be a normal completion. For a long time I kept getting a window asking for information about the DD12 plugin, and regardless what I entered, the procedure would finish and create a USB bootable. That would boot nicely and display the result screen as expected, except never include DD12 in the menu! Other menu item worked fine.

At some point I realized the apparent conflict involving a "files" folder within a "files" folder, reworked the DD12 plugin, and the procedure then ran to a normal completion without stopping!! However, the resulting generated boot fails, from both the DVD and USB! After about 20 seconds with the small blue window in center of the screen, a command window opens and shows these line.

x:\windows\system32\wpeinit
x:\windows\system32\

It seems to be looking for wpeinit, but can't find it. Neither can I find it on my system. Is it something that should already be there, or added by some step in this process?

I am not sure what to do next. I very much like to get this WinPE working!!
Please advise.... Robert
Windows 7, DD12, ATI2015-6525

Hi Robert,

I'm not sure what's happening. It looks like wpeinit is running. Wpeinit is a Microsoft program to initialize network services and other tasks in WinPE. It runs silently and takes a few second before displaying the next command prompt. You won't find it on your system, but it is built into WinPE. It would seem like the problem is that winpeshl.ini is not present in your WinPE.

Are you running MustangPE from an account with administrative privileges? Try right clicking MustangPEBuilder64.exe and select run as administrator. See if winpeshl.ini is in your WinPE. When you run MustangPEBuilder64.exe, click on the Advanced Options button and put a check mark in the box to pause the build. When the build pauses, leave the message box open and look at C:\winpe_amd64\mount\Windows\System32 and see if wpeint.exe and winpeshl.ini are present. Then close the message box and let the build finish. Let me know what you find.

Mustang, Thanks much for the reply and the help.

Running as administrator does not change anything.

As to "see if winpeshi.ini is in your WinPE", I'm not sure where to look for that, except for the following.

The folder "C:\WinPE_amd64" does not exist prior to running the build, but does at the time of the pause you requested!! However, at that time "C:\winpe_amd64\mount\" only contains "launchbar" and "program files" folders, but not "Windows\System32" folders which you requested me to look into.

I have screenshots showing all that, but could not figure how to attach them here. If you wish, I will pursue learning how to do that, as I see others do!!

Again, very grateful for your help....... Robert

You need to go to Control Panel/Folder Options. Click on the View tab at the top. Scroll down and click the radio button next to Show hidden files. Uncheck the box next to Hide extensions for known file types. Uncheck to box next to Hide protected operating system files. Click Okay to save the changes. Now repeat the request in reply #34.

-
I made the requested changes to file options, but saw no difference in results. I did get screenshots attached this time (at least I hope they show below).

One other bit of information -- may or may not mean anything, but just in case!! Earlier, after a few tries of the build when still trying to work out the DD12 plugin, one run terminated early and I don't remember what caused it.

However, the next attempt ended with a message:
"WinPE_amd64 already exists. Either delete, rename or move it and try again"

I tried again, but same message! I then attempted to delete it, but got a message:
"You need to provide administrator permissions to delete this folder"

I tried to continue but was told:
"You require permission from System02\Robert to make changes to this folder"

Well, guess what!! I AM System02\Robert, the only user and the administrator! Cannot explain that!!
So I moved it off to the desktop just to get it out of the way, and that allowed the build to run, but with the trouble described in #33.

Also, just as a trial, I uninstalled and reinstalled Windows 8.1 ADK. Should I try doing the same with your MustangPEBuilder 2 ADK 64 LaunchBar ??

Thanks again in advance ......... Robert

I'm trying to help you with only bits and pieces of information. Each post just gives me a little more.

Why do you have so many WinPE build environments????

I do understand that if the build gets interrupted then the mounted image get corrupted and will not unmount. This will prevent you from being able to delete the folder. To correct this issue, run the Deployment and Imaging Tool command prompt from the ADK start menu as Administrator. Then enter the following line:

dism /Cleanup-Mountpoints

If this succeeds, you should be able to delete the winpe_amd64 folder and try to run MustangPEBuilder64.exe again. My program uses commands including dism that require Administrative approval. If your system will not grant you Administrative rights, this will never work.

-
BINGO!!!
As you suggested, that allowed the winpe_amd64 folder to be deleted. That, in turn allowed the build to run with the results you wanted to see in #34! When completed, the build produced 100% desired results. The USB flash drive boots nicely, with all three Acronis products on the menu and functioning nicely!!

As described earlier, that corrupted folder had been moved out of the way in order to allow the build to run, and it was just setting on the desktop, but would still not delete until now. Strange that it was still causing this trouble, but at this point I want ask! As you mentioned, perhaps I should have provided you more details sooner, but the trick is to recognize at the time what bits of info are possibly meaningful.

The PE build environments you ask about are from a couple of prior attempts at PE building, using "Windows Automated Installation Kit (AIK) for Windows 7". Neither went well, and I need now to clean all that stuff off my system.

Again, I can't thank you enough for both the product you built, and then for the time you spent assisting me, and others, to enjoy the benefits of your work.

Hope you enjoy the Christmas season ........ Robert

I'm glad we got it sorted. Do you remember how the build got interrupted? I've gone to great lengths to avoid this issue by locking the GUI after the Create WinPE ISO button is clicked. It is not unlocked until after the WinPE image is unmounted and the ISO is created. This way users can't stop the program before the image is unmounted and create this problem.

Mustang wrote:

I'm glad we got it sorted. Do you remember how the build got interrupted? I've gone to great lengths to avoid this issue by locking the GUI after the Create WinPE ISO button is clicked. It is not unlocked until after the WinPE image is unmounted and the ISO is created. This way users can't stop the program before the image is unmounted and create this problem.

During that time -- middle of last week -- I was doing so much testing and re-running the build, working with the DD12 plugin, I'm uncertain how that may have happened! Up to that point, the build would go to completion and create final results nicely except never include DD12. That is what I kept playing games with, until suddenly the message about the file already existing that needed to be deleted. You were in the game with me after that!

No doubt I did something to "shoot myself in the foot", and if I can replay the events in my mind enough to remember what, I will send you a note or post here.

Meanwhile, thanks again for all your help ....... Robert

Hi Mustang,

Following step by step the building of the Secure Boot WINPE 5.0, I also note that I never had the option Disk Director available in the menu of Acronis programs despite the fact that the installation seems to be going normally. (see attachments 1 and 2)

Trying to add driver for USB3 Renesas Controller I have the following error: "The driver package contains boot critical drivers x 64, but the drivers are not signed correctly. Use/forceunsigned to install". (see attachment 3)

How could I solve these errors?

Abbreizh

Open DD12.ini from the Plugin\DD12 folder and change the Program Files line to the folder where you find TrueImage_starter.exe.

Try putting both Renesas drivers (nusb3hub.inf and nusb3xhc.inf) in the same folder and specify that folder in the [Driver Folders] section of AddDrivers.ini. The [Driver Folders] section is using the /ForceUnsigned option.

Hi,

thanks for your help, all is running well now.

True Image 2015, Universal Restore and Disk Director are fully functional.
- TrueImage_starter.exe is located at "C:\MustangPEBuilder_2_ADK_64_LaunchBar\Plugins\DD12\Files" instead at "C:\MustangPEBuilder_2_ADK_64\Plugins\DD12\Files" as indicated in ReadMe.txt (DD12 plugin).
- For Renesas USB3 driver, only one is accepted "nusb3hub.inf" but it is necessary to have also "nusb3hub.sys" in the same Driver Folder to achieve the integration. Without "nusb3hub.sys" I had an error.

Abbreizh

You need to have all the Renesas USB 3 driver files in the same folder including nusb3xch.sys.

Do I need to do all that if I just want to create a bootable media (USB Flash drive 64GB USB 3.0) with ATI2015 and my backup(s)?

Maybe and maybe not. You may be able to just create the standard Acronis recovery media on the flash drive and then copy your backup to the drive. The first maybe is will the standard recovery (Linux based) media boot on your computer. If it does, the next question is does a recovery happen at USB 3.0 speed or USB 2.0 speed. If you are successful on both counts, you are all set. If not, you need to move to a WinPE recovery media.

With a WinPE recovery media, you can add any necessary drivers to support all of your hardware including USB 3.0 drivers. The Linux recovery media does not allow you to add any drivers. If the Linux kernel doesn't support you hardware, it will not boot.

Thanks for this great thread Mustang. Very appreciated.

You're welcome.

Mustang:

Hi, Paul. I just did a 64-bit WinPE5.0 build using the information in your first post. Terrific job, by the way. The build contains all three Acronis programs and all three of them worked first time, as did PENetConfig, A43, and even the added 64-bit driver for the troublesome network card in my newest PC. The only thing I am unable to get working is the Opera web browser. There are no error messages during the build process but there is no trace of Opera in the resultant ISO and no menu entry in the LaunchBar for it either.

The version of Opera used is 12.17 build 1863 and the Opera Plugin is from http://www.mechrest.com/plugins/MustangPEBuilder/Downloads/Files/Opera…
The Opera.ini file and the Plugins.ini files are attached (with their extensions changed to .txt).

Builds were done in a VM running 32-bit Windows 7 and when I boot the ISO it is indeed x64. Have you ever gotten a web browser to work in a 64-bit build?