MVP Tool - CUSTOM ATI WINPE BUILDER
14.3 Advanced (12/27/2017)
5.9 Basic (11/26/2016)
Changelog - check out the 14.3 Advanced improvements! **** Supports all versions of Acronis True Image Home 2018 (Backwards compatible with 2017/2016) and the new Acronis Revive file recovery application!
Due to the larger size of the Advanced version, (about 70Mb), we are unable to post it directly in the forums so everything has been moved to the Acronis MVP Google Drive.
Basic is no longer supported and considered deprecated with the release of Acronis True Image Home 2018. Please use the advanced mode; trust us, you’ll like it!
Advanced - just as easy to use to build your WinPE rescue media as the old Basic version! It does everything that Basic did, but also includes options for Bitlocker support, ISCSI support, a web browser, file explorer, explorer shell, 7zip association, PDF association, tools, screen resolution, customizations and more!
It is also possible to use WinRE to incorporate Wi-Fi support if desired. What’s even cooler, is that it will automatically include Universal Restore, Disk Director 12 and/or Acronis Revive if they are also already installed on the machine that the rescue media is being built from.
WHAT IS THIS?
MVP ATIPEBuilder is essentially a batch script tool designed by MVP's: Bobbo_3C0X1 and Mustang, with collaboration from Steve Smith and Enchantech and testing by other MVP's.
This tool can be run on any 32-bit or 64-bit system that is using Windows 7, 8, 8.1 or 10, as longs as there is a compatible version of Acronis True Image Home (2018/2017/2016) installed on it already. As of build 14.2 and newer, you may also build recovery media without having an existing installation of Windows ADK (5.x, 6.x or 10.x), so long as the default Windows Recovery Environment (WinRE) is active on the machine.
This tool does NOT work with legacy versions of Acronis True Image Home (2015 and earlier) and there are no MVP plans to provide support for them, due to variations in the Acronis provided WinPE content. Additionally, newer Acronis products are designed to have better compatibility with newer hardware technologies and current Operating Systems and we believe that using more current versions of Acronis products is beneficial for users looking to migrate to these newer technologies.
Anyone with a Windows 7 or newer Windows OS, that has a current version of Acronis 2016 or newer, may use this tool to build CUSTOM 32-bit or 64-bit Acronis Bootable Rescue Media. This will be especially useful for those of you that have 32-bit only UEFI systems or the OEM manufacturer has set the SATA mode to RAID in the BIOS and it cannot be changed. This tool supports automatic driver injection in both the 32-bit and 64-bit media creation process.
Whether using this tool to build 32-bit or 64-bit customized WinPE Acronis Bootable Rescue Media, the resulting media can also be booted in legacy mode for ANY system (32-bit or 64-bit), where the bios supports legacy/CSM booting and/or UEFI mode for ANY system where the bios supports UEFI booting.
WHY DO WE NEED IT?
If you have a 32-bit only UEFI tablet or laptop that came with an eMMC flash hard drive, or any system that came with a PCIE NVME hard drive, you may have found that 32-bit/64-bit Linux Acronis Bootable Rescue Media and/or the default 64-bit WinPE Acronis Bootable Rescue Media won't detect your hard drive. This is because the manufacturer has set the bios SATA mode to RAID and/or:
01) Prior to the release of Acronis True Image Home 2018, the default version of the Acronis Bootable Rescue Media was based on Linux and typically did not have RAID controller drivers such as Intel Rapid Storage Technology (IRST), which are needed to detect newer hard drives when the SATA mode in the bios has been set to RAID by the manufacturer. Although Acronis True Image Home 2018 has options to build rescue media with WinPE or WinRE, and also has driver injection, it still has some limitations compared to this tool.
02) The current Acronis Bootable Rescue Media Builder only creates 64-bit WinPE and will not be bootable on a 32-bit only UEFI system.
03) Driver injection is now built into the tool and additional drivers can seamlessly be added "on-the-fly". By default, we provide the latest Intel Rapid Storage Technology (IRST) drivers (if you choose to run the driver injection option) so that anyone using the latest NVME PCIE hard drives can create media that will support it out of the box - even if the manufacturer has set the SATA mode to RAID in the bios. (Note: if your system has a custom RAID controller such as LSI or Rocket-RAID, you may still need to add those drivers into the driver folder before running the tool).
HOW DOES IT WORK?
What we've done with this tool is simply emulated the Acronis default media builder process, but enhanced it. We take full advantage of the provided 32-bit and 64-bit WinPE tools that Acronis provides
(Acronis currently only builds 64-bit WinPE rescue media with the default media builder). We have added a section for CUSTOM / AUTOMATIC driver injection too! The entire process is handled with Microsoft DISM commands from the WinPE ADK packages so that we can include the ability to add custom drivers, copy drivers from the local system into the build, include Bitlocker support, ISCSI support and native OS language support. Furthermore, instead of limiting the WinPE media to just True Image Home, it will search the system for Universal Restore, Disk Director 12 and Acronis Revive and include them in the recovery media if they are already installed on the system being used to create the recovery media.
CAVEATS / CONSIDERATIONS / RECOMMENDATIONS
01) This is not an official Acronis tool, but they like it a lot. It has even been integrated into the application for easy access. However, we recommend checking the MVP Google Drive to ensure you are getting the latest version. We've tested it thoroughly and feel that it is not only useful, but safe to use. If you do have issues, please be sure to post here in the forums for assistance.
02) The tool should always be run with Administrative Privileges to ensure that the script has the proper access for making changes where necessary. We've taken precautions to ensure that the script is always run with admin access (even if you forget). 1) All current advanced versions are now an EXE that forces admin access before launching. 2) The older versions use a shortcut to require admin privileges by default. 3) The older version scripts will prompt for UAC access if it is not launched with the shortcut and detects it has been run with a regular user account. Please still try to always right-click and "run as administrator" whenever possible - just to be sure though.
03) On some machines, the tool may flag as an untrusted file under Windows Smart Screen. This is because it includes A43 file explorer, 7zip and is a .bat script downloaded from the Internet without a digital signature. This tool is not malicious and contains no malware. You can safely run it without fear, but please do so only if you are comfortable doing so.
04) UPDATE 12/13/2017 - you can now use this tool to build custom Acronis rescue media, even if you don't have Windows ADK installed. As of version 14.2, it is now possible to build rescue media with the local system WinRE (Windows Recovery Enviroment) if they are on the local system. Alternatively, if you prefer to use Windows ADK (traditional Windows PE) to create your 32-bit or 64-bit WinPE Acronis Bootable Rescue Media, please do so before running the tool.
05) As of 9.5 advanced and newer, the tool is strictly self-sufficient and no longer needs the Acronis media builder. However, it goes through the same process of checking for licenses to ensure proper activation in the WinPE. Additionally, it will look for other installed Acronis products (Universal Restore, Disk Director 12 and/or Acronis Revive) and automatically add those too.
If your customized WinPE Acronis Bootable Rescue Media boots successfully, but still does not detect your hard drive, you will need to re-run the tool and make sure to have the drivers ready to include them in the automated driver injection process. Alternatively, you can still use the DISMGUI tool and instructions in this thread to inject drivers manually, after you've created WinPE Acronis Bootable Rescue Media
(01). MVP WinPE Builder (02). MVP LogViewer (03). MVP Google Drive (04). Clone Correctly (05). Clone vs Backup (06). MBR vs UEFI (07). TibMount Patch (08). Locate Last Volume Fix (09). Cleanup Utility (10). DISMGUI (11). ADK WinPE10 (12). Contact Support
True Image and Snap Deploy
Motherboard: GA-Z170X-Gaming 3 / CPU: i5 6600K (OC 4.3Ghz) / Memory: 16GB Corsair Vengeance DDR4 (OC 3000 Mhz) / NVMEs: Samsung 950PRO, MyDigital BPX / SSDs: OCZ Vertex 4, PNY XLR8 / HDs: WD Black / OS: Win 10 Pro x64 / NAS: WD MyCloud
This would be great, but it doesn't work for me:(Win pro 64 last level, Ati 2018)
-It doesn't find my ATI version,
-It is unable to create an ISO disc it says "bad image"
-It is unable to create a WinPE key, it says "it is not a disc".
Any help, please ?
Daniel, welcome to these User Forums.
Have you tried using the normal Acronis Rescue Media Builder tool in Simple mode before doing anything else?
If this doesn't work for you either, then please open this problem as a New Topic rather than complicate this topic which is purely for the MVP tool script.
If opening a New Topic, then please also provide more basic information:
Windows version (7, 8.1, 10)?
Did you upgrade from an earlier version of ATI to the 2018 version, if so, which one?
What size of USB stick did you use to try to create a WinPE key?
What version of Windows ADK do you have installed?
Thank you for you quick answer. I have still done and often used the Basic Media tool. I decided to create a WinPe tool with your script to make a Universal Support to be able to restore on a different disk drive as I was never able to make this successfully with the explanation given in Acronis (drivers trouble).
Finally I was able to burn a DVD picking up the .ISO file and using another Image Burner. I am currently making a standalone backup and it seems to work well. Next step will be to restore with the same system. I am not sure, not to make myself a mistake, in answering the message of the USB Key letter address, so I will try tomorrow again and see what happens.
To Answer your questions, I use Windows 10 pro 64 bit system version 1703 15063.608. I had uprgraded ATI to version 2018 from version 2016. I am not able to give you the windows ADK version installed as currently, I don't have access to my working system. But it should be up to date as I downloaded and installed late in October 2017.
Creating USB key didn't work, (unable to format (?)), so I used Rufus to install the .ISO file on the key. Up to now backup with CD and restore with USB key worked well.
So I'll investigate about other errors, but for now I considere the problem as solved.
Daniel, thanks for the update/feedback.
Please see KB 58108: Acronis products: using USB sticks with more than 32GB capacity to consider when choosing USB sticks.
The other known issue in this area is that USB sticks should be fully formatted if you find they will not boot when created, doing a quick format is not sufficient, plus they must be FAT32 formatted.
FYI, I"m using a 128GB drive with many .wim files that I've customized as a multiboot tool for my own purposes as a swiss-army approach to IT support functionality, so it is possible to use a larger drive. That said though, please heed Steve's advise and try a smaller drive to test with first to rule it out. Bootability of larger drives may be dependent of your hardware's bios firmware capabilities (if your bios doesn't even have a UEFI option - I doubt it would ever work).
Secondly... how many times have you formatted/built that drive with Rufus or another media builder? That could be your issue as it changes the partition table and we can't see it in Windows. I used to praise Rufus for this task, but have grown apart from it due to inconsistencies with bootability since it seems to generally want to build all drives as
GPT NTFS now. Instead, myself, and other MVP's will often recommended to fully format your USB drive first (not a quick format) with diskpart (diskpart /clean) or a 3rd party tool like Minitool Partition Wizard Free. That will ensure that any modified partitions (including the hidden ones) are wiped out so the next go-a-round when you use Acronis media builder or the MVP media builder has a completely blank slate to work with no behind the scenes linux paritioning or whatever it is Rufus uses to work its magic during the build process.
Third - there is a known bug in the ADK prior to Windows 10 1607 which can cause the drive to not format or build correctly. I would recommend that you use the latest Windows 10 ADK (if you're not) which will help with bad USB builds since it already includes the fix. We do provide and use a copy of the fixed version of the file for all builds now, but only as of the MVP mediabuilder 12.1 - if you're using an older version, get that one. For reference here is the thread where user Jan54 found the issue and identified a link with the fix
The problem lies with the MakeWinPEMedia.cmd
After the script partitions and reformats the flash drive, the disk appears offline for about 10 seconds (can be verified if you have Explorer open). This for some reason messes up XCOPY in the way the command is written.
Open MakeWinPEMedia.cmd using notepad ( notepad "C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\MakeWinPEMedia.cmd" )
xcopy /herky "%WORKINGDIR%\%TEMPL%" "%DEST%\" >NUL
xcopy /herky "%WORKINGDIR%\%TEMPL%\*.*" "%DEST%\*.*" >NUL
notice the \*.* at two places, thats what somehow makes XCOPY wait for the disk to be ready and then copies the files.
Rookie here. I have a Windows 7 system with ATI 2018 and Universal Restore installed. I have gone through the instructions and installed WAIK and the supplement to it. I downloaded the latest MVP_ATIPEBuilder files.
I RMB and run as Administrator the MVP_ATIPEBuilder.exe. It goes for a bit and then gives me a screen that says it can't find the kitsroot. Press any key and program will exit.
I am running exe from a subfolder where I extracted it. It appears to me, without knowing anything further about it, that the program can't find the WAIK?? Do I need to run this from a main folder under C:\??
Anyone run into this?
Yes, that would be my recommendation. I would remove WAIK through control panel and install ADK (Windows 10 1709) from Microsoft instead:
Once installed, reboot for good measure and then try running the tool again. I think you'll be fine after that. Keep in mind that with Windows 10 ADK, you'll be building Windows 10 WinPE so if you need to add any additional drivers (you really shouldn't need to, but if you add custom drivers, use Windows 10 ones to match the WinPE).
We include the latest Intel RAID controller drivers, but other than that, the latest Win10 ADK has enough generic drivers that things should work just fine as is.
A new version of MVP_ATIPEBuilder is available. Anyone wishing to try it can download it at http://www.mechrest.com/plugins/MVP_ATIPEBuilder/Advanced/MVP_ATIPEBuilder_v142.zip
The new version provides the option to automatically build from the WinRE found in the recovery partition of the system being used for the build. It is not necessary to have a Microsoft WAIK or ADK installed. There are less features included with the WinRE option. This new version still includes the option to build from an installed ADK for those needing the features not available when using the WinRE option.
Version changed from 14.0 to 14.2 on 12/16/2017. Onlt minor changes.
Rob, Paul, sorry but the WinRE option is not working for me and I don't get a log file to help show what is / is not happening?
I am able to use the Acronis Rescue Media Builder Simple method to create WinRE media that way.
The only error I am given says "Windows RE is diabled. Script will terminate."
In reply to Any way to get this topic… by Patrick O'Keefe
The only way you could get that result is if WinRE is actually disabled on your system. Enchantech has given the correct solution. The MVP Tool uses the output from reagentc /info to get the path to winre.wim on your system. Acronis must be using a different method to locate winre.wim. That would explain why TI can build a Simple WinPE and the MVP Tool fails. Try entering reagentc /enable followed by reagenct /info to see if WinRE can be enabled.
I had the same issue on one of my systems recently. I unexpectedly found WinRE was disabled. It may have been the result of a Windows upgrade to a new version.
Paul, Bob, thanks for your comments / advice. I was able to do some quick checks over the holiday break and WinRE was disabled but this was complicated by the computer in question being dual-boot with 2 different copies of Windows 10 (one Insiders, one Fall Creators), and where the RE was owned by the Insiders OS, so wouldn't enable on the second OS.
See the output of the reagentc commands below from the 2 OS's.
Microsoft Windows [Version 10.0.16299.125] (c) 2017 Microsoft Corporation. All rights reserved. C:\Windows\system32>reagentc /info Windows Recovery Environment (Windows RE) and system reset configuration Information: Windows RE status: Disabled Windows RE location: Boot Configuration Data (BCD) identifier: 581fa3fb-b8f0-11e7-815e-a8c0509ccd86 Recovery image location: Recovery image index: 0 Custom image location: Custom image index: 0 REAGENTC.EXE: Operation Successful. C:\Windows\system32>reagentc /enable REAGENTC.EXE: Unable to update Boot Configuration Data. ---------------------------------------------------------- Microsoft Windows [Version 10.0.17063.1000] (c) 2017 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>reagentc /info Windows Recovery Environment (Windows RE) and system reset configuration Information: Windows RE status: Disabled Windows RE location: Boot Configuration Data (BCD) identifier: 9a98d614-e5df-11e7-80c7-940e5cf82fd0 Recovery image location: Recovery image index: 0 Custom image location: Custom image index: 0 REAGENTC.EXE: Operation Successful. C:\WINDOWS\system32>reagentc /enable REAGENTC.EXE: Operation Successful.
The next issue is that trying to run the MVP Custom ATIPE builder after enabling WinRE gave the following messages then 'died'...! No log was produced to show what service didn't exist?
================================================================= ***************************************************** ** Administrative privilege confirmed. ** ***************************************************** ================================================================= ***************************************************** ** System scan and preparation in progress. ** ** ** ** Please be patient. ** ***************************************************** ================================================================= ERROR: Description = The specified service does not exist as an installed service. ERROR: Description = The specified service does not exist as an installed service. ERROR: Description = The specified service does not exist as an installed service. ERROR: Description = The specified service does not exist as an installed service. ERROR: Description = The specified service does not exist as an installed service. ERROR: Description = The specified service does not exist as an installed service. ERROR: Description = The specified service does not exist as an installed service.
I haven't been able to do further testing since encountering the above due to family commitments that involved a lot of unexpected travel, but try to find time soon.
Bob, I can create the ADK version of the MVP media with no issues (on both OS versions) but guess this is because the ADK is installed to both too.
The TI Media Builder also fails to build the WinRE media taking the Simple option on the 2nd OS system. Will need to reboot to the 1st OS to check this on the other 'side' since using reagentc /enable on this OS.
I thought probably so. I think the issue is that the media builder tools do not look for the Active partition on disk to determine which OS installation from which to create the WinRE. Your probably right about the ADK to build the WinPE.
I do not have a solution for you with this but I can provide some interesting reading.
If you enter the Advanced Boot of Windows 10 (hold down shift key, click restart) do you find 2 defferent WinRE options? I think you should, one for each install but I might be wrong about that.
Bob, just to confirm, the TI Media Builder runs fine in Simple mode on the 1st OS system where WinRE was enabled.
The MVP builder WinRE option does not seem to recognise that WinRE is enabled, probably due to being a dual-boot system, but the ADK option works fine! So no big issue here, I was just giving the new RE option a run through but will do it on a different single OS system when I have a little time to do so.
Thanks for the link to the Recovery Environment repair webpage.
Thanks Steve, I think that The Media Builder tool being able to create WinRE and the MVP tool is not is revealing that the Media Builder is looking for the Active partition when building the media whereas the MVP tool is not. It is possible to change Active partition using Diskpart but that is probably not necessary. Guess we'll see what Paul says.
I still have no idea why those errors are occurring on the system with WinRE enabled. At this point I can only assume it has something to do with the system being an Insiders build. I don't have any Insiders build systems to test with. I know it works with Windows 10 1709. I take the same approach as Acronis does regarding Insiders builds. Too many things can change or be corrected before they become release builds.
The MVP Tool is recognizing that WinRE is enabled. Otherwise the script would terminate as it did before WinRE was enabled. Something is going wrong after that. Some function being called seven times is failing to recognize a services that it depends on.
If it works for me but not for Steve in the next Windows release version. I'll investigate further.
Jose, welcome to these User Forums.
Please create a New Topic in the ATI Forum that matches your product version for this question as it is unrelated to this topic about a MVP tool.
More information will be needed in your New Topic to help us to understand the context for your question, i.e. what exactly are you trying to do here, are you backing up to the NAS or making a backup of the NAS, what version / build of ATI are you using, what Windows OS version etc?
WinRE has native MSiScsi support. WinPE does not. If you build the recovery media using the TI 2018 Acronis Media Builder, select the Simple method. This will use WinRE from your system to build the media. If you use the MVP Tool, select the option to build from WinRE.
After you boot the media, go to a command prompt and enter the following line to start the MSiScsi service:
net start MSiScsi
You will see a message that the MSiScsi service has been successfully started. After that I can't tell you what is needed to see the iscsi volume on your NAS. I have never used iscsi or a NAS. I tend to stay away from things that are going to make life difficult in the recovery environment.
I recommend you use the MVP Tool to build the recovery media. This will give you easy access to the A43 File Manager program. See if you can see the volume on your NAS. Even if you can connect to the volume on your NAS in the A43 program, True Image may not see the volume. TI 2018 is having problems seeing mapped network drives even though they are visible in A43.
Technically yes. Mustang and I have been able to successfully add multiple Acronis products into WinPE at the same time. HOWEVER...
Snap Deploy tends to use an additional version of a .dll and sometimes a different snapman driver than True Image. They often conflict and have to be installed in a particular order.
It's do-able, but we were really focusing on a home-user tool when we developed this and the amount of time to update and code in spare time is pretty time-consuming.
Also, a major downfall for the Snap Deploy winpe is that you can't do a "stand-a-lone" deploy because it has been ommitted by Acronis (only available in the Linux version). So that kills some of the usefulness of it compared to the Linux version in that regard.
Also, Snap Deploy seems not support more current versions of ADK (natively) as fast as True Image. This can be problematic with the native build process. I think it wouldn't be an issue with the way we build the WinPE with this tool, but something else we'd have to test and consider.
Maybe one day, but for now, you'll still want to create the snap deploy media separately for the home vs business products.