Guide to building a 64 Bit UEFI Secure Boot WinPE 5.0 CD or USB Flash Drive running TIHome 2014 with or without Disk Director 12

Your guide is great! Thanks for pulling it together. I was hoping you could help me out. I followed the instructions and was able to create the disk from the iso file created by MustangPEBuilder64.exe. When I boot up with the disk in the drive, it doesn't do anything.

In addition, "%SYSTEMDRIVE%\Program Files\A43\a43.exe" to "%SYSTEMDRIVE%\Program Files\Acronis\TrueImageHome\TrueImage.exe", are not located at these locations. The a43.exe is located at "%SYSTEMDRIVE%\Program Files (x86)\Acronis\TrueImageHome\BartPE\Files\a43.exe" and TrueImage.exe is located at "%SYSTEMDRIVE%\Program Files (x86)\Acronis\TrueImageHome\TrueImage.exe".

This is were these installed by default. Does this matter? Could this be why the disk isn't doing anything on boot up?

If you can help, I would greatly appreciate it. Thanks.

See PM.

Mustang-

It is working now. Thank you for all your help.

Mustang wrote:

Guide to building a 64 Bit UEFI Secure Boot WinPE 5.0 CD or USB Flash Drive running TIHome 2014:

IMPORTANT: This will only work on a Windows 8.1 64 bit system.

1. You must have the Premium version of True Image Home 2014 installed on the system you build from. You also need the free plugin "Media add-on" downloaded from your Acronis account and installed. You also need to unzip the WinPE.zip file in C:\Program Files (x86)\Acronis\TrueImageHome\BartPE.

2. Download and install the Windows 8.1 ADK from Microsoft. http://www.microsoft.com/en-in/download/details.aspx?id=39982

3. Download and install MustangPEBuilder 2 ADK 64 from my website. http://www.mechrest.com/plugins/MustangPEBuilder/Downloads/Files/Setup_…

4. You need to copy two Acronis 64 bit driver files named fltsrv.sys and snapman.sys to the Acronis BartPE. First, go to C:\Program Files (x86)\Acronis\TrueImageHome\BartPE\Files\Drivers and create a new folder called X64 under the Drivers folder. Now copy fltsrv.sys and snapman.sys from C:\Windows\System32\drivers to C:\Program Files (x86)\Acronis\TrueImageHome\BartPE\Files\Drivers\X64. You will need to provide Administrative approval to copy the files.

5. Run MustangPEBuilder64.exe from C:\MustangPEBuilder_2_ADK_64 and click the Create WinPE ISO button to generate a WinPE 5.0 ISO at C:\MustangPEBuilder_2_ADK_64\ISO.

6. If you want a USB Flash Drive to boot WinPE, click the Advanced Options button and choose a drive letter where the USB flash drive will be created.

7. Burn the file winpe_amd64.iso at C:\MustangPEBuilder_2_ADK_64\ISO to a CD.

It's that simple! Because it's a 64 bit WinPE, it will be UEFI bootable.

When booted into WinPE, you will start with a file manager open. This is the WinPE shell, so do not close it until you are done. Closing it will issue a reboot. To get to True Image Home 2014, navigate to X:\Program Files\Acronis\TrueImageHome and double click on TrueImage_starter.exe. You may minimize the file manager, but do not close it while you're working in True Image.

Some insight. The WinPE will be built using the standard 64 bit WinPE 5.0 supplied in the ADK. Files will be added to the WinPE from your 64 bit system in order to add support for running the 32 bit version of True Image supplied by Acronis. I was able to add enough of WOW3264 to get True Image to run. Unfortunately, not all 32 bit programs will be able to run. BSExplorer used in the 32 bit version of MustangPEBuilder will not work properly. It will start, but the links do not work. Hence, I'm using the file manager as the shell. If you would prefer to have True Image start immediatele (instead of the file manager), you can open C:\MustangPEBuilder_2_ADK_64\winpeshl.ini and change the last line from "%SYSTEMDRIVE%\Program Files\A43\a43.exe" to "%SYSTEMDRIVE%\Program Files\Acronis\TrueImageHome\TrueImage.exe".

My web pages have not been updated to include the 64 bit version. In the meantime, it will only be available to download from the above link.

Edit:

As of Feb. 10, 2014, a new version is available. If you downloaded prior to that date, please download again and reinstall. See my post # 7 below for details.

Edit Feb. 22, 2014:

If you end up with an empty USB drive, please see the solution provided by Jan Loef at post #16 below.

I'm using dell vostro 1540. When I boot to this iso it shows windows logo for 1-2 mins after that it shows windows error message

Ananda,

I would suggest you contact Dell support and ask the what you need to do to boot a 64 bit WinPE on your computer.

I've created iso using adk 8.100.26629 (for Windows 8.1 update) while starting acronis i got this error code as shown in screen shot

Ananda,

When booted to MustangPE, look at X:\Windows\System32\Drivers\snapman.sys. Right click the file and click properties. Click the Details tab. What is the Product Version Number?

Look at X:\Windows\SYSWOW64\snapapi.dll. Do the same and see what the Product Version Number is. If they do not match, that would explain the error.

Did you install Disk Director 12 on this system?

EDIT:
Assuming you did install Disk Director 12 on your system before you started the process, you should see the following file versions in C:\Program Files (x86)\Acronis\TrueImageHome\BartPE\Files\Drivers\x64 (these are the files you copied from your system):

fltsrv.sys version 1.3.0.2142 116 KB
snapman.sys version 4.5.0.2250 270 KB

If this is true, you can solve your problem by copying C:\Program Files (x86)\Common Files\Acronis\DiskDirector\WinPE\Win32PE.zip\Files\Drivers\snapapi.dll to C:\Program Files (x86)\Acronis\TrueImageHome\BartPE\Files\Drivers\ replacing the existing snapapi.dll.

This is my first experience with a Mustang package so I am not real sure what to expect, but I'm pretty sure what I am seeing is not correct. I just created the WinPE 64 Media with both TIHome and DD12 as per the original post. It boots and what I see is a full screen bitmap of a Mustang and a window of the file manager. I expected a graphical type menu to select what application I wanted to run. Is this normal or should I see some kind of menu? Also a question as to what environment this flash drive will work in. I am Windows 64bit 8.1 but do not have UEFI, so does the drive created as per post 1, work for both UEFI and non UEFI environment? I know half the answer as I indicated I just booted it on a non UEFI machine. By the way Thanks a bunch for your work with this, as I for sure really appreciated it.

What you're seeing is correct. To start True Image 2014, navigate to X:\Program Files\Acronis\TrueImageHome and double click TrueImage_starter.exe. To start Disk Director 12, navigate to X:\Program Files\Acronis\DiskDirector and double click TrueImage_starter.exe. Yes the start program is named the same for both programs.

You can use this 64 bit version on any UEFI or non-UEFI computer that has a processor that will support 64 bit. You can also create a 32 bit version of MustangPE that does have a nice GUI desktop. See http://www.mechrest.com/plugins/MustangPEBuilder/MustangPEBuilderADK.htm . The 32 bit version will only work on UEFI Secure Boot computers if they are set to enable Legacy Boot in the BIOS. You will also need to download the plugins for TI 2014 and DD 12. For your computer the 32 bit version is probably a better choice.

Hey Paul,

Is it possible to add drivers to the image? For example wireless drivers?

Deleted

Hi Pat,

MustangPE allows you to add drivers very easily. However, wireless networking is a problem in WinPE. It requires much more than just installing the driver for the wireless adapter. The infrastructure to support wireless networking is not included in WinPE, so it will not work in MustangPE.

Thank you very much! Ijust created the WinPE and it is awesome. I really like the file manager and its ability to mount shares. Super convenient when you backup to a NAS.

First of all thanks for your work on Acronis WinPE Plugin!

I tried to build a WinPE 5.0 Image under Win 8.1U1 x64(German) but unfortunately got a side by side configuration error when trying to start TI2014.
I tried to export the Winners Key of my registry, replaced \SOFTWARE\ With \PE_Software\ and rebuilt the PE Iso. With this changes the iso hangs in a boot Loop (Bios - Windows logo with cycling dots - black Screen - bios .....)

Any further hints? Thanks in advance

I'm sorry, I never did figure out why it won't work with the German version.

Will this work with TIhome2015?

Yes. See the TI 2015 post here https://forum.acronis.com/forum/71918 .

I got a question need to help here, thanks in advance.
Followed by the post 1, I created usb flash disk, it can normally boot into winpe. BUT when I run TrueImage_starter.exe nothing happened. Only ADD12 3223 run flawless. Don't know how to do next. Please help me out.

FYI, My laptop based on UEFI GPT, windows 8.1 pro & ADK 8.100.26866.0 (ATIH2014 6673 with addon, US, plus ADD12 3223 x64 US).

I'd done some verification myself below but still can't fix the problem:
1. file versions in C:\Program Files (x86)\Acronis\TrueImageHome\BartPE\Files\Drivers\x64 folder,
fltsrv.sys version 1.3.0.2142 116 KB
snapman.sys version 4.5.0.2250 270 KB
c:\Program Files (x86)\Acronis\TrueImageHome\BartPE\Files\Drivers\snapapi.dll (4.5.0.2250 423kb)

Under winpe:
X:\Windows\System32\Drivers\snapman.sys. --4.5.0.2250 269kb
X:\Windows\SYSWOW64\snapapi.dll --4.5.0.2250 422kb

2. Tried add packages(you mentioned in the post) or by default blank;
Tried replace Winners.reg /default

3. Tried change order in
c:\MustangPEBuilder_2_ADK_64\Plugins\
[Plugins]
plugin1=32Bit\32Bit.exe
plugin2=A43\A43Utility.exe
plugin3=TIHome2014\TIHome2014.exe
plugin4=DD12\DD12.exe
plugin5=PENetCfg\PENetCfg.exe
OR
[Plugins]
plugin1=32Bit\32Bit.exe
plugin2=A43\A43Utility.exe
Plugin3=DD12\DD12.exe
Plugin4=TIHome2014\TIHome2014.exe
Plugin5=PENetCfg\PENetCfg.exe

What language is your Windows system based on? There are problems with languages other than English.

My system language is English, Only location set to China, (I'm Chinese). Both the OS and ATIH2014, ADD12's language are English. So I don't know what's wrong out there. Anything more I need to check /fix? thanks!

It looks like you did everything correctly. Try double clicking TrueImage.exe instead of TrueImage_starter.exe. Does that produce an error message?

I'd tried both at the first place, sadly, no any single popup message at all. In fact, all I need is a usb flash disk which can boot both ATIH and ADD on UEFI GPT based pc. is there any alternative method out there?

Try building without the DD 12 plugin to see if TI will run. If it does, we will figure out a solution to get both programs to run together in the same build.

Sorry for the delay, Mustang, and thanks for the advice.
Then I tried delete the DD12 folder, also the item in the plugin line. Even went for the total uninstalling of the ATIH2014 with the official uninstall tool, atih_cleanup_tool_s_e.exe, reboot and reinstall... unfortunately, after rebuilt the usb flash disk, the problem was the same, reboot into winpe, click TrueImage_starter.exe or TrueImage.exe nothing happen. what's the possible reason? What else should I try to fix it?
I did once (only once!) 'luckily' got a message popped up "snapshot manager library (0x100005), the versions of the modules are incompatible(0x9), etc." Then I figured out that was because I forgot replaced the snapapi.dll in C:\Program Files (x86)\Acronis\TrueImageHome\BartPE\Files\Drivers after reinstall. I'd tried copy snapman.sys or snapman.sys plus snapapi.dll from C:\Program Files (x86)\Common Files\Acronis\DiskDirector\WinPE\WinPE32\Files\Drivers to BartPE\Files\Drivers. Didn't work.

Is there anything wrong with the AcronisTrueImage2014_addons_en-US.exe itself?

I have put TI 2014 back on a Windows 8.1 64 bit system fully updated. When I build a new WinPE with only TI 2014, I get the same result as you. It is no longer working! I booted a CD I made in Feb. of 2014 and it works fine.

I am trying to figure out what has changed without any success. My feeling is that something in the system files being copied to the WinPE to add 32 bit application support has been changed by Windows Update. I'll let you know if I get it sorted out.

Sorry, I can't figure out what is going on. TI 2014 will no longer run in the 64 bit WinPE.

Edited Jan. 2, 2015:

See reply #81. Optional Windows updates KB3000850 and KB3013769 must be uninstalled for TI 2014 to run in the 64 bit WinPE.

It looks like the performance and reliability improvements of the November update rollup KB3000850 changes the files necessary for the WOW64 functionality in the WinPE. Uninstalling the update and then running MustangPEBuilder64 produces fully functional Acronis WinPE.

Give it a try, Uninstall KB3000850[KB3014442, KB3003057](detail, download), retry, but failed :(

Joey,

Thank you very much for working on this issue. You must have spent countless hours on this.

I also uninstalled KB3000850 and found, as Ryan did, that TI 2014 would still not run in the WinPE. Next, I restored the test system to a backup that was made on Nov. 5,2014. Update KB3000850 had been installed on my system on Nov. 19,2014. After that, TI 2014 would run in the WinPE! I don't know what, but some other update in addition to KB300850 must be involved.

After further testing on my machine both updates KB3000850 and KB3013769 have to be uninstalled for True Image to function in the WinPE.

I have several virtual machines setup for testing software. Acronis would not run on the WinPE created on the fully updated Windows 8.1 VM, but did on the one created from the VM that had all but the optional updates KB3000850, KB3013769, and KB3013816.

After uninstalling those updates True Image functioned on the WinPE created by that system. I then reinstalled KB3000850 and found that Acronis no longer functioned on WinPE created by that machine. That is where I erroneously concluded it was solely responsible for the issue.

Installing KB3000850 and/or KB3013769 on my test systems breaks the WOW64 functionality of the WinPE created on those systems. KB3013816 had no effect on the WinPE.
Your mileage may vary. :)

Paul, Joey,

A pure guess here on my part but I see where Update KB3000850 included refreshed language packs. Since the language issue exists with the implementation of the 64bit WinPe this refresh may well be the root of the issue.

Joey,

That did it. Removing KB 3000850 and KB3013769 fixes the problem.

Enchantech,

I'm not sure if the language issue has any bearing on the problem or not. I do know, just by watching KB3000850 uninstall, that it is a very large update. You might even compare it to a Service Pack by the length of time it takes to install and uninstall.

It would be nice if I could figure out what modified files and/or registry entries caused the problem. I think it must be a combination of files and registry entries because it does not stop TI 2014 from working in Windows. That way I might be able to fix the problem in my plugins without uninstalling the Windows Updates. I do know that it is something small that TI 2014 is using because I have may other 32 bit programs running in the 64 bit WinPE that will still work with these Updates installed. I'm not sure I will have time to pin it down.

Paul,

You are right, KB3000850 is a very large update and addressed a huge number of issues in both Win 8.1 and Server 2012 R2. I am attaching a link to the Microsoft support site that discusses the update which may be of benefit to you if you can find the time.

http://support.microsoft.com/kb/3000850

I am having some trouble getting a working result and hope for some guidance :).

I would like to produce a WinPE USB that can work on a UEFI system once I have it installed.

Currently I am building the USB off my Win7 x64 Home installation, with Ti 2014.

I installed the Windows ADK 10, Mustang ADK 2 64, Ti 2014 plugin and the Acronis media update for Ti2014.

My acronis installation is in Program files (x86)   not 'program files' so I ammended the pathways in the plugins.ini file and the mustang config file to reflect that.

I find that sometimes the program fails to produce the output. It closes and leaves a directory (the amd x64 directory) but no iso and no USB. Other times it works properly and produces the bootable USB.

UNfortunately the USB boots to a command prompt ina window and has no Acronis installation that I can find.

My question is.... am I seeing a lack of backward compatibility with the Windows 10 ADK and need to install an earlier one?

If I can't get it working properly I can install Ti2016 on my laptop (which is windows 8.1) and generate a WinPE USB off that (any guide on tht one with plugins?) but I'd rather get the Ti2014 one working if I can.

Incorrect post removed.

Still having the same problem - boots to a blue background with a dos box.

Edit: am just  checking which licence I have. It may be TI 2014 not TI 2014 premium...

Inconsistent production of the USB too with Mustang closing and the temp files being left and marked with credentials that will not allow deletion through windows (have to boot into a console).

Not sure what's up. Have stepped through each point of your guide and the only differences are - ADK 10 (not 8), Win 7x64 (not win 8.1) and Mustang ADK (x32 not x64).

Is there a seperate guide for TI2014 and Win 7 you may have or know of? At this point I'll be ok with that as long as I can get access to network shares and my backups :).

Sorry for the incorrrect post earlier.

You can use the 64 bit LaunchBar version of MustangPE from my website. You need to use the Windows 10 ADK. The Windows 10.1 ADK will not work. See my website for the download link to the Windows 10 ADK.

You need the Premium version of TI 2014. You need to see the Free Plugins tab under your account for TI 2014 and you need to download and install the Media add-on.

You need to include the optional 32Bit plugin to add 32 bit app. support to the 64 bit version of MustangPE. You plugin.ini file should look like the following:

[Plugins]

plugin1=32Bit

plugin2=A43\A43Utility.exe

plugin3=TIHome2014\TIHome2014.exe

plugin4=PENetCfg\PENetCfg.exe

Follow the ReadMe.txt file in the TIHome2014 plugin. Also follow the ReadMe.txt filw in the PENetCfg plugin.

Thanks :).

I now have the premium version of TI 2014 (Thank you to Gaider)

I will ammend the version of the ADK to  10... didn't realise I have 10.1 from the MS website.

I had to reinstall Ti after entering the new code that made it premium in order to get th PE ISO maker working. That was a bug in DD and some earlier software Acronis allegedly fixed but still must be present.

Edit:

Reinstalled all components as needed and followed the directions for the guide - includingthe read.me files.

Running MustangPE generates a request for the path for Install.wim which I need for the 32bit plugin - is this an issue of using windows 7? Not sure how I am supposed to generate it or find it....

I now have a correct desktop.

Acronis is present now under \program files\  but states it will not run. Also not linked on the applications off the taskbar.

My network settings and share ern't being detected automatically I can set and access it through the program on the desktop though so that's ok.

Thanks for the advice to this point too..... almost there :)

You need to get install.wim from a Windows 10 installation DVD for build 10240. The instructions are in the ReadMe.txt file in the 32Bit plugin folder.

There is a problem with the link in the ReadMe.txt file because Microsoft has changed the Windows 10 Media Creation Tool. It no longer builds Windows 10 build 10240. You will need to get install.wim from an existing DVD for Windows 10 build 10240. It can be found in the sources folder of the DVD.

Still no success. When I run Acronis in WinPE I get an error regardign teh "subsystem" not being correct.

I have :

-  install.wim from the version of Win 10 you suggested.

- win 10 ADK (not 10.1).

- paths set for ADK (confirmed), 32bit, Acronis.

- ini files set to point to relevant .exe files.

- unzipped the elements indicated and installed the acronis media add on.

I do not have Autoit3 installed.

When I run Mustang ADK it still asks via pop-up for the install.wim location. Does that indicate some sort of error in my pathing? right or wrong it still continues so I can't tell if this is the issue (Tried it as "c:\install.wim" anyway so I can't see the issue).

I don't know how you got install.wim. I had the exe file for the Windows 10 Media Creation Tool for Windows 10 build 10240. I ran it and created the media. It did produce an install.wim. When I tried to mount it with dism.exe, I got an error about it being the wrong format. It looks like Microsoft has made some changes. You should try to mount install.wim as a test. Go to Start Menu/Windows Kits and run Deployment and Imaging Tools Environment "as Administrator." Then enter the following line:

dism /Mount-Wim /WimFile:C:\Temp\install.wim /Index:1 /MountDir:C:\mount  (This assumes install.wim is at C:\Temp and the folder C:\mount exists.)

The file should mount with no errors.

Then enter:

dism /Unmount-Wim /MountDir:C:\mount /discard

The file should unmount without errors.

Install.wim needs to be from the 64 bit English-US version of Windows 10 build 10240.

When I ran this test using the old version of install.wim, it mounted and unmounted without errors.

I have the same problem and don't know the build process went ok.

I got my install.wim from en_windows_10_pro_10240_x64_dvd.iso downloaded on 16/07/2015. Install.wim is dated 15/07/2015. 

The mount command gives an error:

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>dism /Mount-Wim /WimFile:C:\Temp\install.wim /MountDir:C:\mount

Deployment Image Servicing and Management tool
Version: 10.0.10240.16384

Error: 87

A required option is missing from the command-line.
Ensure that /index or /name is specified.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

When I add the /Index:1 parameter, it mounts ok.

dism /Mount-Wim /index:1 /WimFile:C:\Temp\install.wim /MountDir:C:\mount

The unmount ran ok.

Jan54,

Sorry, I forgot to include the /Index:1 in my post. I have edited the post to include it.

What error are you getting when you try to run TI 2014 in MustangPE?

Mustang,

I'm running TI 2016 and DD12 in MustangPE without trouble. (Building it according the 2015 version of this topic)

I wanted to implement 32Bit to be able to run TotalCommander 32bit. But I use a old plugin which creates C:\WinPE directory that is not included in the final ISO.

Also I don't know how to test 32Bit. 

That's why I'm in this topic.

I would suggest you use the 64 bit version of Total Commander.

I have en_windows_10_pro_10240_x64_dvd.

Using DISM in an elevated command prompt from the deployment kit I have no issues mounting and unmounting intall.wim.

Where is Fixwow64 being called from - it does not exist in my c:\windows\system32 directory. Is it being called from the mounted install.wim?

If so I wonder if it's a pathing issue. I'm a bit stumped at this point :).

I think I see the problem here. The mistake is in the ReadMe.txt file for the 32Bit plugin. The path to install.wim should not include \install.wim at  the end of the line.

Example if install.wim is located at C:\Temp:

[Paths]
Install.wim=C:\Temp   (Not C:\Temp\install.wim)

[AutoRun]
Add line to AutoRun.cmd=%SYSTEMDRIVE%\Windows\System32\FixWOW64.exe

The [AutoRun] lins is generated after you run the plugin for the first time. FixWOW64.exe is included in MustangPEBuilder64.exe and is called from X:\Windows\System32 when MustangPE is run.

Making this change should correct the subsystem needed to run this app is not present error.

With the TI 2014 plugin there will probably still be an error when running TI 2014 in MustangPE. The fltsrv and snapman drivers need to be 64 Bit versions. You will need to get snapapi.dll, snapman.sys and fltsrv.sys from a 64 bit system and replace these three files at C:\Program Files (x86)\Acronis\TrueImageHome\BartPE\Files\Drivers. 

cheers.

Almost there now....

1. USB created successfuly.

2. Acronis runs on the USB and functions - however does not show up in the start menu. Adding a shortcut doesn't work in the menu.

3. PeNETcfg isn't mounting my drive. works if I do it manually in the program but I must have an error in my config file...

I want to avoid using a MAC so I can run this on multiple PC's at home.

Should I use "NET" command instead as an entry in one of the scripts?

Do I need to comment out the WINS server?

My config file is:

[General]
AutoStartNet     = No
PromptForProfile = Yes
ShowGUI          = Yes
Timeout          = 30
;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[NetProfiles]
Home Profile = PENetCfg-Home.ini
Work Profile = "%SystemDrive%\Net Profiles\Work.ini"
;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[NetID]
ComputerName     = WinPE
Workgroup        = Home
PrimaryDNSSuffix = microsoft.com
;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[FileSharing]
StartFileSharingService = Yes
AdminAccount            = XXXXXXX
AdminPassword           = XXXXXX
ShareDriveRoots         = Yes
;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[NetAdapter1]
; SpeedAndDuplex = {10|100|1000},{Half|Full}
; SpeedAndDuplex = Default (for default settings)
SpeedAndDuplex   = 1000,Full

;NewMACAddress    = 00-0c-29-8a-d5-aa

EnableDHCP       = no
UseStaticGateway = no
UseStaticDNS     = no
UseStaticWINS    = No

IPAddress        = 192.168.1.25
SubnetMask       = 255.255.255.0
DefaultGateway   = 192.168.1.1
DNSServer        = 8.8.8.8,8.8.6.6
WINSServer       =
;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
; You can map up to 10 network drives: [NetDrive1] ... [NetDrive10];
[NetDrive1]
; Drive     = X:
; Drive     = * (to use the first available drive letter)
Drive       = *
NetworkPath = \\192.168.1.2\Backup-images
UserName    = XXXXXXXXX
; Password  =  (leave it empty to be prompted for a password)
Password    = XXXXXXXX

;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[PostNetAutoRun]
; StartupFlag = CommandLine

; StartupFlag is a bit field that can take the following values:
; 0 = run hidden and wait      (00 00 00 00)
; 1 = run normal and wait      (00 00 00 01)
; 2 = run hidden and don't wait (00 00 00 10)
; 3 = run normal and don't wait (00 00 00 11)

3 = %SystemDrive%\Programs\BGInfo\bginfo.exe %SystemDrive%\Programs\BGInfo\bginfo.bgi /timer:0
0 = %SystemDrive%\Programs\Ghost\Ghost.cmd
;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Notes]
;Computer Name      : WinPE
;Workgroup          : Home
;IP Address         : 192.168.1.25
;Subnet Mask        : 255.255.255.0
;DNS Servers        : 8.8.8.8,8.8.6.6
;Create Admin Account: XXXXXXXX
;Start File Sharing : Yes
;Map drive * to \\192.168.1.2\Backup-Images

;This profile configures network settings for use with Syn.

You can manually add the net use command to the AutoRun.cmd file before you build so the drive will be mounted automatically at boot.

You can add the shortcut during the build. First, plug in a USB drive and assign drive letter X to the drive. Then create the folder X:\Program Files\Acronis\TrueImageHome. Second, copy trueimage_starter.exe to the folder. Third, create a new shortcut to run X:\Program Files\Acronis\TrueImageHome\trueimage_starter.exe and name it True Image 2014. When you build, place a check mark in the pause the build box on the Advanced Options page. When the build pauses, copy the shortcut to C:\winpe_amd64\mount\LaunchBar\StartMenu\Programs. Continue the build. The shortcut should be in the Start Menu when you run MustangPE.