Louis, the tool works well if you use the Windows 10 ADK rather than SDK - the ADK will work with Windows 7, 8.1 and 10 for this purpose of creating the MVP Custom ATIPE media.

When launched the media will bring up a WinPE desktop and defaults to launching the ATI main GUI but with Start menu options to launch other applications you may have included.

I'm not sure what you've done.

Did you place the Tool folder in the root of your C Drive. If you didn't, there could be permissions problems. The command window you see should be running winpeshl.ini. That will launch the custom shell and start the Acronis program. When you boot the first media you created, enter notepad.exe. Then try to open X:\Windows\System32\winpeshl.ini. Do you see the file and its contents?

As Steve said, the Tool uses an ADK not an SDK. Did you mean to say 8.1 ADK and 10 ADK instead of SDK? If you did use ADK's, please uninstall the 8.1 and 10 ADK's. Then reinstall the 10 ADK. Also check to make sure you have the following reg key:

HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows Kits\Installed Roots. You should see KitsRoot10 on the right side with a data value of the path to the ADK. You may need to delete any left over key of KitsRoot81 with the path to the 8.1 ADK.

Thanks for the quick responses - 

It is ADK, not SDK .... sorry for the confusion.

So on my 2nd attempt (from my previous post) with ADK10, ADK10 was installed after I completely uninstalled ADK8.1.  In addition, the tool folder was placed in the root of the C drive from the very beginning.

I won't be able to check the other items until Monday as it is my machine at work, but will post that information when I get back to it.

Thanks again.

You need to be on a computer where your account has administrative privileges. Do you have this on your work computer? 

Hello,

My computer : ADK 10.0.16299.15 and windows 10 1709 (16299.431)

I just try the advanced version 182 signed of the  ATI PEBUILDER and find out a problem I'll describe here after

I built the following , asking for system language (French). At the end of the process I put the resulting files (of acronis_x86.iso)  on a bootable USB key. Then I boot from the key.

Result of the boot
------------------

MVP_ATIPEBuilder_v182 signed
    Remains in English despite the log and informations displayed during built
    indicating that everything was correct.
I will join the corresponding log
#
MVP_ATIPEBuilder_v182    unsigned
    same result

***
As I  previously used MVP_ATIPEBuilder_v121 I tried to built with some older versions
Here after the results after USB boot :
#
MVP_ATIPEBuilder_v121     
    language is French OK
#    
MVP_ATIPEBuilder_v143     
    language is French OK
 

Thank you for reporting this issue and for your detailed description. I have found the problem. The next release will have the problem fixed.

EDIT:

In the meantime, you can boot the media for v 182 and follow these steps to get TI 2018 to run in French:

1. Close TI 2018.

2. Open regedit.exe and delete this key:

HKLM\SOFTWARE\Acronis\Global

3. Restart TI 2018.

TI should now run in French.

Hello,

Thanks for your quick response (I think you're talking about version 182)
I followed your advice and I have recovered the French version
Regards

Thanks for confirming. I edited the post to refer to version 182.

I am currently downloading the ATI-PE_Builder-2xxxxxxx file from the Google Drive.  My angst so far is that the Google Drive shows that this file has not been updated since Nov 23, 2016.  Although the first numbers in the downloaded file are 2018.  Given all the work that has gone into this (Thank you very much btw) hopefully the download is the updated version.  Also given that the authors are having considerable trouble getting it to work please wish the rest of us luck.

So far it appears to be working with ADK and the downloaded file was 18.2.

Guys, your script ran great, thanks!  Didn't do a USB drive but that was the fault of the thumb drive I used and it did a good iso for a DVD boot disk.  Most importantly I believe it picked up all the drivers it will need should something happen.  I will make another for my new XPS 9670 and load its appropriate drivers up.

Thanks guys,  was able to easily create CDs for both of my newest computers with appropriate drivers.  Have been unable to create a USB drive however, both with the MVP script and with the Rescue Media Builder even on newly formatted (full format as you suggest not quick).  I would appreciate a link to any detailed article you may have written on the subject.  Unfortunately the actual Acronis authored directions and help sections are not very well written and are far from complete, leaving many necessary steps to the imagination.  Thanks in advance.  BTW, the USB drives are easily accessible on the computer and accessible by windows and the bios and most everywhere else you might expect to see them so it is not a computer problem.

Edit:  I found a solution in Knowledge Base Art 1526.  Used Diskpart to clean and format the usb stick.  Worked where a full format with Win Explorer did not.  Thanks.

William,

You should make just one disk with all the drivers for both computers. That one disk will then work on both computers.

Good idea, thank you.

"You should make just one disk with all the drivers for both computers. That one disk will then work on both computers."

On the other hand, if you make a hardware change to one of the computers you then have to run a regression test on the other computer(s).  If you have one recovery device per computer you have to recreate only the one for the computer whose hardware changed. 

Perhaps I am less coordinated that others but when I was trying to make a single recovery device for 3 computers I inevitably got something wrong such that the backup would work on only 2 of the 3 computers (with a different computer the loser each time).  For some reason I had trouble with the drivers for the wireless adapters but that was probably coincidence.)  I finally decided it was easier and quicker to just create a separate backup medium for each computer.

Given the price of thumb drives and CD-R disks that was my concern.  It was just easier to do 2.  Also one is a Dell XPS 9570 and the other is a build I did from an Asus Rog Strix Z370 mobo.  Maybe many of the same drivers but maybe not.  And given the excellent script the guys have written it just seemed as easy to make a CD and a UBS stick for both.  Interestingly enough in my testing a good number of my media creations mostly made directly with the Acronis Media Builder ended up being corrupted and would not work.

In theory you could download and run the Double Driver utility, run in on both (or all, in my case) your computers, merge the drivers into one directory, and use that as the list of custom drivers for the Builder.  In theory.  I always messed something up.  It was a fun exercise but, as you said, the script is so easy to run and the storage devices are so inexpensive that it really isn't worth the bother.

Until I did some recent Ethernet wiring I needed wireless support so the Acronis Media Builder was not an option.  Even now when I no longer absolutely need the wireless support (which nevertheless comes in handy for my laptop), I really appreciate having a usable Windows environment.  Bottom line: I haven't even tried using the Acronis Media Builder for the past few releases of ATI; the recovery medium built by the Custom Builder is far more flexible.

Many thanks to the MVP team that built the Builder!

Let me take this opportunity to make some comments about handling drivers. The MVP Tool has tried to make driver injection automatic for the computer being used to build the media by using a third party program called Double Driver to pick up the needed drivers from the running Windows system. This is done in the add System drivers section and the drivers are stored in the Drivers_Extracted folder. The Drivers_Custom folder is supplied for the user to add drivers for other computers he wants the media to support. It is always possible to make one media to support all the computers you have.

Double Driver does not succeed to picking up all the drivers properly. This is because some OEM's modify how the inf file needs to see the files needed by the driver. For example, some put the needed files in a subfolder under the inf file. This causes the driver injection to fail. You can see which drivers succeeded and failed by looking at the log in the Logs folder. Having the program analyze the inf file to make corrections proved far too difficult, so we gave up. We also looked for other methods that would work better than Double Driver. No method we investigated worked any better.  I have been able to look at the inf file for all drivers that failed to install and manually make corrections to get them working. The bottom line is the user still needs to take some responsibility for getting all the drivers to work.

Personaly, I think the best approach is to add System drivers one time and then copy the drivers you need from the Drivers_Extracted folder to the Drivers_Custom folder. Then skip the add System drivers section on subsequent builds. Always check the log to make sure the drivers you added are being successfully added.

Agree with Paul on this.  There is no single "one size fits all" solution to adding drivers.  For some hardware it is trial and error to get things working.  The recommended approach offered above is the "best case" scenario at the present time! 

While I'm sure what you've both said is true, for my computers your Builder does a far better job by default than my trial and error does.  I've had no trouble when I've run the Builder on each of my computers to build a Recovery medium for that computer.  I created a series of messes when trying to combine the 3 sets of drivers into one recovery package in hopes it would work on 3 computers.

You may be right that your technique isn't perfect, but it sure works better by default than when I try to help it along!  :-)

Lol! Fair enough!

Great work folks.

I was able to easily create a USB boot drive containing TI, DD, and UR - works great and the additional utilities are terrific.

I used the ADK for Windows 10.  I actually have deleted the WINRE partitions from all my systems so the standard media creation tool wouldn't even work.

One question - which specific components of the ADK are required? I took the default when I installed, but would like to remove those that aren't required.

Thanks for the super addition to the tool kit!

Thanks for the quick reply Steve!

Note for Newbies who function on a more basic level:  

This WINPE Builder worked perfectly with Windows 10 and a  Lexar 16GB USB Flash-drive, on an HP Spectre X360 (256SSD HD), with ATI 2018. 

I just followed the prompts and did not add any additional custom drivers, wifi, bitlocker etc. I elected to NOT rely on the WinPE and I downloaded and installed Windows ADK (took about 5 hours with my lousy internet connection).  The boot USB drive does take a long time to boot past the MVP Acronis Forum logo (quite a few minutes) but it gets there eventually and works (be patient).  This boot USB drive also works on my Desktop with ATI 2017, and boots past the logo MUCH quicker on the Desktop.

This HP originally had ATI 2017 on it and last year, from within ATI  2017, I had generated a Rescue boot media (Linux- on a cheap Verbatim 16GB flashdrive)  that worked OK (also worked on my Desktop).  However, when  I later tried to generate a WINPE boot disk with ATI 2018 on the HP (on a 16GB Samsung flashdrive), the resulting USB Boot disk would not boot past the CMD screen, so I used this Tool so generously provided by the MVP's. (Many thanks)  

Interestingly, the ATI 2018 generated rescue WINPE rescue disk that would not work on the HP that created it does work on my Desktop.

Question for the gurus:  Can I now uninstall ADK?  My HP has a relatively small hard drive and the 3GB ADK takes up might come in handy later on.

"Can I now uninstall ADK?  My HP has a relatively small hard drive and the 3GB ADK takes up might come in handy later on."

The answer is 'Yes' - you can uninstall the ADK but would need to reinstall it if you want to update the MVP rescue media at any time in the future, i.e. should you want to add device drivers or update because Acronis release a new update etc.

For years I've been using the Custom WinPE Builder using with with the ADK and WinRE.wim from Build 10.0.14393, version 1607.  While my recovery media work fine I think I'll update to verion 1803 on at least one PC.  Want to make sure I get this right.  As I understand it, I need to

1. download and install the 1803 ADK
2. extract the WinRE.wim from an 1803 installation medium and put it in the appropriate Builder folder.

If that is correct then I guess I cannot use a shared copy of the Builder unless I have the matching level of ADK installed on each computer where I might run the Builder.  Did I understand correctly?
 

Hi Patrick,

Your understanding of the build process is correct. However, you should be able use the new media to boot on all of your computers. You would not be able to build new media using the 1803 WinRE.wim file on computers where the 1803 ADK is not installed. The ADK version must match the WinRE.wim version during the build.

I am running Windows 10 (1803) and plan on upgrading from ATI2018 to the new 2019. I understand that i have to create new recue media, but didn't think of downloading the new 1803 ADK. Is that neded?

I've used my ATI 2018 recovery medium built with a 1607 ADK to recover systems lately.  I also used an ATI 2019 (Beta) recovery medium built with the 1607 ADK but I won't swear to its success.

I think the point is (and I'm sure the MVPs will correct me if I'm wrong) that if your version of ATI (2019 in this case) will run on your ADK's version of Windows you should be fine.

In my case I suspect my ATI 2018 and 2019 would have no trouble running on Win 10 1607, but I can't remember much about 1607 so I thought it was time to upgrade my recovery media.

Hi Patrick,

My concern is that the rescue media might not work if created on a Windows (1803) system using the (1709) ADK, or should i replace it with the (1803) ADK?

Steven,

It would work with either ADK. However, you will get more options during the build process if the Windows version and ADK version match. It would be better to upgrade to the 1803 ADK.

Thanks

Sorry if this it not the right place to ask...

I am trying to restore an win10 image from dissimilar hardware. Normally this is not a problem with the MVP tool and Acronis Universal restore but when I deploy the IMG from the tool I get this warning:

Iv never seen that before. Initially I thought it was because AHCI was disabled in BIOS on the destination PC but even after enabling it in BIOS all I boot into is a black screen with a blinking prompt in the top corner.

Source CPU: intel Celeron n3060

Dest. CPU: ATOM D525

As mentioned it has never been a problem deploying images to dissimilar hardware but I noticed one difference this time and that is i am also restoring a recovering partition - I dont know if that matters?

Is there anything I can dpo to get this to work?

Best regards! 

Peter, this issue is caused by booting the rescue media in Legacy/MBR BIOS mode for a UEFI OS being restored.  You need to match the BIOS mode to that used by the OS - you second image shows you have an EFI partition, so you need to use the UEFI option when booting the media.

See the following forum topic where this has been discussed previously.

This might be a stupid question, but does this MVP tool, support ATIH 2019?

Yes, it works fine with ATI 2019 and is my own default rescue media.

Possible effects of MS W10-1809 ADK/WINPE on Acronis &/or MVP Win PE creation?

Background: The Acronis, or MVP variant, WinPE builder uses Win ADK components.  Until now, after the user (WIN10) initially installs the ADK (normally prompted by the ATI builder if not in place) as MS updates Win 10 major versions (e.g. 1607/1709/1803 etc), the Win updater does not update the ADK that was installed earlier.  For example, my Win10, at V1803 is still using ADK V10.1.14393, circa W10 Ver 1607.

That is, I haven't manually taken steps to update my ADK...as all works fine.

Now: As can be found on these MS URL's:

https://docs.microsoft.com/en-us/windows-hardware/get-started/what-s-ne…

https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-insta…

https://docs.microsoft.com/en-us/windows-hardware/customize/desktop/una…

MS has separated the WinPE component from the ADK Package.  This was ,apparently done, so that when a Win 10 major upgrade is released, post RTM, MS would be ABLE to include (upgrade) a users WinPE as part of the Windows Update (auto) process.

I can imagine that this change might effect how ATI's WinPE Rescue media builder downloads and installs the (to be) ADK and WinPE (now separate downloads)?  Likewise, I can imagine some potential impact regarding the MVP software.

Comments from the MVP team Please!

Thx

Bob

Bob, with the new split ADK approach from Microsoft, both files are needed if using the ADK with the MVP tool.  The WinPE part is obviously needed for the PE components, but the other, smaller ADK file is needed to provide the DISM component used by the tool to perform the actions in updating the boot.wim file(s).

If only the separate WinPE ADK components are installed then the MVP tool will fail with errors because DISM is not found.

Will a new version of the MVP Tool be announced in the Acronis True Image 2019 Forum?

This is the only forum that I follow.

Thx Jan
 

The tool works with newer versions of ATI; it is to a significant degree version independent when it come to ATI. Some components are updated from time to time, but they are external to ATI. As I understand it the tool copies the Acronis recovery *.wim file to the recovery media, so it uses the version installed on the system. This *.wim file should be updated with each new build of ATI (although, if memory serves me correctly, there was one build where this did not happen).

Ian

PS I am not an expert on this just what I have learnt from using the tool and following discussion on the Forum.

Ian, is this a answer to my question?

I only want an announcement of a new version of MVP Tool in the Acronis True Image 2019 Forum.

Jan, now that you have posted a comment to this post, you will be notified if there are further updates here unless you have turned off notifications from the forum.  There hasn't been a new version of the MVP tool since September when 18.2 was released and announced in the initial post for this topic.

As Ian has said, there hasn't been a need for a further update as the current version works fine with all the versions that it supports to date, so unless Bobbo or Mustang deem there is a need for a further version or want to introduce a new feature, there is unlikely to be another one till next summer when Acronis announce the beta testing phase for their next version of ATI, and we get to confirm if the MVP tool still works with the same.

Thanks Steve, I will not turn off notifications.

Jan brings up a good point, though.  There are certainly others who have no reason to look at the ATI 2018 forum so don't know about the MVP WinPE builder.  It would be good to have a pinned posting on the 2019 forum mentioning the Builder and perhaps providing a link to this thread.

I have sent a PM to Ekaterina about this issue. There are several threads on the ATI 2018 and 2017 Forum that are generally applicable and it may be worthwhile having them in a separate Forum. The MPV tool, how (not) to clone and disk, and how to uninstall prior version of ATI. There may be some other sticky threads that should be treated in the same way.

Ian

I can provide a few notes just to clarify. As Steve mentioned above, both the ADK and WinPE components need to be downloaded and installed for version 1809. Luckily, WinPE ends up in exactly the same place in the ADK as it was in previous versions. This meant the MVP Tool did not need to be updated to accommodate version 1809. There were also no significant changes in TI 2019 so the MVP Tool didn't need to be updated for that either.

I do have a new version(18.4) that makes two minor improvements. The build from WinRE option currently doesn't work on Windows 7 systems. This has been fixed. There was also a change needed to support Acronis Revive 2019 because of changes made over Acronis Revive 2017. I'll submit the new version to Acronis for their review and to have a digital signature added. After I get it back, I'll post an announcement in the TI 2019 forum and get it uploaded to the Google drive. I don't know how long that will take. 

Thanks for the update Paul. Users, such as myself, greatly appreciate the effort that has been put into the ongoing development of the Tool.

Ian

Just a side note.  I've been pretty inactive for some time and had previosly updated the stickies. I will try to keep up with the Google Drive updates when new versions are officially released. Please note that Acronis has added an MVP link at the top of all threads that go straight to the Google Drive location. Maybe not exactly what was asked a few posts up above, but  might be useful for those looking for updated info on the MVP tool outside the existing stickies.

I have ATI 2019, Univ Restore and DD 12.5 Workstation, I used the MVP Builder latest version 182 and added ATI2019, Univ Resotore and DD12.5. All seemed to go well without errors, but upon  booting the finished media WinPE only shows that ATI 2019 is installed, no sign of DD or Univ Restore. I see that 182 says that ATI2019 and DD12.5 aren't supported.... but ATI 2019 did get installed... so I take it I need to wait for a newer release of MVP builder? 

Or can I modify something to make it work? or something else?

Thanks!

I just found Disk Director 12.5 and tested it. It is fully supported by the MVP Tool. So is the latest version of Universal Restore.

Did you click the blue Start Menu icon in the lower left corner and select Programs?

If you truly don't have these programs in the MVP Tool media, please post your log.

I also tested with DD 12.5 and it worked fine.  Make sure to grab the 18.6 version that was uploaded today for good measure.

As Mustang mentions, you need to use the programs button from the start button when multiple items are installed.  By default, you'll only see True Image in the task bar.  The other items will show up in program files though if they were licensed and installed at the time of build.