Windows 10 ADK for PE boot image

In my tests it used the Win 10 ADK.

Hmm...

I made the non-PE ISO boot media, but when making the PE version I got an error.

There was a display of mounting and updating the WIM file, then 'Failed to create bootable media'.

There was a link to click for the KB but that also got an error.

The link resolved to:
https://kb.acronis.com/errorcode/bookmark/term-not-found/term-not-found…

No errors were listed in the Event Viewer for System or Application events.

The same, or similar, thing happened when I tried it on my laptop.
No errors logged in Event Viewer.
The last system event is:

File System Filter 'WIMMount' (10.0, ‎2015‎-‎07‎-‎09T20:13:18.000000000Z) has successfully loaded and registered with Filter Manager.

Where did you download the Win 10 ADK? I used the link at the bottom of this page https://msdn.microsoft.com/en-us/library/windows/hardware/dn914754%28v=… .

I am having the exact same problem.

Any further information about this? I don't want to create a backup and find I cannot restore it to my win10 PC.

Well you can make the standard restore disk, just cannot make the Win PE environment one.

Mustang wrote:

Where did you download the Win 10 ADK? I used the link at the bottom of this page https://msdn.microsoft.com/en-us/library/windows/hardware/dn914754%28v=… .

Yes, that was the place.

The file was adksetup.exe version 10.0.26624

The installer shows the same version for the kit.

I installed two options, the Deployment tools and the PE environment.

For my Desktop and Laptop, both show 3.41 GB for the install size.

It was pretty much the same process for the Windows 8 and 8.1 ADKs. But prior to that it was different.

joelbb wrote:

Well you can make the standard restore disk, just cannot make the Win PE environment one.

Yes, I made a standard boot rescue disk and put it on a bootable flash drive.
I booted into it and tested it by validating my previous image.

It seems to work fine.

I'll do some more thorough tests and a recovery when the dust settles. But it's nice to have a PE version.

I have no idea why it doesn't work for you.

I tested in a Windows 10 Enterprise 64 bit system that was upgraded from Windows 8.1. I made three tests:

1. With only the Windows 8.1 ADK installed.
2. With only the Windows 10 ADK installed.
3. With both the Windows 8.1 and Windows 10 ADK's installed.

All three tests worked. In test 3. above when both ADK's were installed, Acronis used the Windows 10 ADK.

Maybe you should try uninstalling the Windows 10 ADK and installing the Windows 8.1 ADK.

Well I actually tried it with the 8.1 ADK and it didn't work. I installed the 10 ADK (so had both) and it didn't work. I uninstalled the 8.1 and it didn't work. It seems like Mustang is the only one who can get it work...

The only thing I can suggest is to uninstall the Media Add-On and then uninstall TI 2016. Then install both again. Perhaps installing one or the other as an upgrade without unistalling first had some bad effect on the WinPE Media Builder.

I have both 8.1 and 10 ADK installed.

I was planning to uninstall the 8.1 ADK - it's pretty big.

If this doesn't get resolved soon I might just live with the Linux boot rescue media.

I just spent about an hour or two looking over the PROCMON trace of the MediaBuilder run.
It looked to me like it was building the WIM quite nicely and then just gave up for some reason near the very end.
The last few things were writing to a log file and looking for a kb_link library.
The last was probably to set up the error condition in the knowledge base in the form of a URL.

The log file looks like this: (attached)

Hopefully that makes sense to someone.

The error message in the file is basically: "Error 0x180023: Failed to copy the product files."

The area in Procmon's trace where product files were copied to the WIM did not yield enlightenment. At least I didn't spot any error reading or writing a product file.

As a followup to my last post, I should also mention that I have Acronis Disk Director 12 Suite version 3223.

I saw that the MediaBuilder was making references to that product - maybe that is the product file it could not load.

I have made a Rescue Disk for DD12 (quite a while ago) and it boots and runs fine - I tried it today.

Prior to ATI 2015 it was possible to make both (ATI + DD) in one ISO, but that stopped happening at some point in the ATI2015 development.

This is sheer speculation on my part.

And another followup.

I just ran Disk Director 12's Media builder and it uses the Win 8.1 ADK.

It built the ISO successfully.

Perhaps ATI 2016 is trying to add on the DD12 product but that is not compatible with the Win 10 ADK?

Again, sheer speculation on my part.

You may be correct about the problem being DD12. I don't have it installed on my system.

Question? Did you install TI 2016 to the default location? The product files for TI 2016 WinPE should be found at C:\Program Files (x86)\Acronis\TrueImageHome\BartPE\WinPE.zip on a 64 bit system. If WinPE.zip is not at that location, you would get an error.

WinPE.zip is in the correct location that you describe. I do have DD12 installed but haven't even used it in months.

Mustang wrote:

You may be correct about the problem being DD12. I don't have it installed on my system.

Question? Did you install TI 2016 to the default location? The product files for TI 2016 WinPE should be found at C:\Program Files (x86)\Acronis\TrueImageHome\BartPE\WinPE.zip on a 64 bit system. If WinPE.zip is not at that location, you would get an error.

Yes, I'm aware that Acronis bundles together the 32-bit and 64-bit components.

The WinPE stuff is there, this is a standard installation with no alterations. There's lots of stuff in the Common Files, too.

There is a registry setting in the Mediabuilder that refers to Disk Director and has some configuration paths to the splash screen and startup logic.
The attached image shows the details.
These seem to be properly installed.

I would try uninstalling DD12, but I fear I might need to run the cleanup tool and screw up ATI 2016. I don't think the cleanup tool is ready for Windows 10 yet.

Perhaps renaming some of the DD12 registry keys might fool the MediaBuilder, but I've spent too much time on this already.

I hope the devs are looking over these forums.

Hi arachnaut, joelbb, Michael,
please send us your system reports through in-product feedback form. We'll need info from particular systems for investigation, because as for now it hasn't been reproduced in our lab.
Thank you in advance for cooperation!

Mustang, thank you for your help!

Anna Trifonova wrote:

Hi arachnaut, joelbb, Michael,
please send us your system reports through in-product feedback form. We'll need info from particular systems for investigation, because as for now it hasn't been reproduced in our lab.
Thank you in advance for cooperation!

Mustang, thank you for your help!

OK, I sent two - one for the desktop and one for the laptop and referred back to this forum URL.

OK, done.

Well, I actually finally got this to work, but not sure what change I made did the trick. I realized I did not have the newest version of Disk Director, so I uninstalled the old one and installed the new one. I tried to burn a PE boot disk, but it insisted that I have the Win 8.1 ADK, would not use the Win 10 one. Interestingly, although it refused to burn the disk without the ADK installed, it was giving me options to burn a disk with both Disk Director and True Image. I installed the 8.1 ADK and now it burned the disk but gave me no options to include True Image. And now when I ran True Image it gave me an error message regarding the scheduler service. I uninstalled Disk Director, but the error message persisted. So I uninstalled the media addon and then True Image 2016, then rebooted and deleted the True Image folder, then reinstalled True Image and then the media addon. And now lo and behold, I can burn a PE boot disk. I think maybe there is just some issue with Disk Director, which hasn't been updated in forever and I prefer the Paragon product anyway, so I am leaving it off my computer.

joelbb - I have encountered stuff like this with just about every release of Acronis products in the last decade.

It works well and wonderfully when it does and it is well worth the effort to install and make work.

But if you look through my forum postings throughout the years you will get a tiny glimpse into the problems I have run into.

Acronis hooks itself deeply into the OS and is very sensitive to the hardware and software environment.

I suppose those that have a clean install or an OEM computer have little trouble, but those of us that build and customize our system have a bit of a problem when things don't work.

By the way, I personally don't use any feature of Acronis except for full disk and partition backups.

No incrementals, nothing scheduled or non-stop, no cloud.

I run a backup when I have made significant changes to my system and find that everything is stable.

I have 14 logical volumes and 8 physical drives and a substantial amount of time and effort to make a system that I use effectively.

I would be very happy with a streamlined, slim, single purpose application.

All. I develop for Windows 10
I can tell you that after installing the ADK for Windows 10
Then starting the create Winpe disk part of Acronis that the Windows 10 ADK installation is ignored and insists on downloading the Windows 8.1 version
If you use the 8.1 adk it will work but who wants too create a recovery disk that does not match the O/S and risk a none recovery
ok the Linux based recovery disk works. So I would use that

So from my point Acronis 2016 is at fault and should be updated to ask for and download the correct files for the Win PE recovery disk

Sorry to say this but a backup program called REFLECT will create the correct WinPE boot disk without downloading masses of files from Microsoft

http://forum.macrium.com/Topic3141.aspx

Reflect is still using the Windows 8.1 ADK on Windows 10 systems.

Arachnaut, joelbb, thank you for sent reports! They are being investigated now.

arachnaut, I see that you have already collected a ProcMon trace during issue reproduction.
May I ask you to share this log with us for investigation?
I have sent instructions on how to upload it via a personal message.

Hello Dmitry,

I re-generated the tracefile and uploaded it.
It is compressed with RAR.

hi
me bug to create Cd-r acronis cloud 2016 winpe boot
echec create iso or CD-R
+50%

me adk win10 and adk win 8.1

WinPE creation under Windows 10 64bit
Ok sorted this out but takes time that should not be require
Start the create from under tools. Allow it to download and install the acronis file it requires
Ignore the bit about download the microsoft Winpe files.
This version of Acronis will enforce a download of version of 8.1. Version that you do not want to use for Win 10
Closedown Acronis and download the ADK from Microsoft.run the adksetup latch file downloaded and from selection select only the WinPE part
allow to load. Restart system the run Acronis recovery disk to run again. Select the create WinPE dvd/cd or dump either the Windows 10 PU iso or .wim file. Yes it works this time without asking for any other downloads
NOTE: this is what happens when you rush a release of software without fully testing it out. My view is (right or wrong), that this software was release to quickly without proper complete testing. You can see that from the blogs arriving within the last few days
No doubt at all until this is stable i wont be using it for real backups/restores

hello thank you for information but with me it does not work always the same mistake with Winpe 10

me installed wdk10

re all
voici l'erreur

no code error

i have WDK
donwload ADK 10 or WDK 10?
you link ADK 10 please
adk 8.1 echec

Thanks for the link Mustang! Have you already elaborated if it is it still so complicated to put DD12 and ATIH 2016 into one Windows PE (UEFI)?

I have just noticed an anomaly, if I use the Media Builder from TI 2016 then the W10 ADK is not recognised and the Builder only offers to download W7 -> W8.1 ADKs, however, if I use the Universal Restore Builder, it automatically finds the W10 ADK and works correctly.

Just a heads up, don't try and add too many drivers to the UR, it freezes after reaching 50%. How many is too many drivers I hear you ask, hmm, when you try to add your complete Windows driver folder to the media. Obviously not how it is meant to be used, but interesting that there would seem to be a limit.

Hmm, might this limit referenced by Colin be available space on the media being used has been reached?

hello, I test all solutions winpe with adk or wdk 8.1 and 10 nothing works I plant to around 40-50% without error code

[url=http://terriers.vraiforum.com/image/110/4/6/5/2015-windows10-ac...-erro…]

Didier,

I get the same error message if I try to create a WinPE to a USB drive that has an earlier version of WinPE on it. If I delete the FAT32 partition and create a new FAT32 partition on the USB drive, it works with no error.

I just tried a usb fat32 it is the same error

upgrade acronis 2016 build 5576 ok
creates winpe echec
it is the same error
echec 40-50%
create iso or dvd

The changelog on the Hotfix version 5576 does not mention anything about the WinPE problem.
While the update for True Image and the corresponding add-ons went well, the problem remains unchanged.
The Linux-based boot ISO was made OK and works fine.

yes iso to linux is ok for me

Version 5586 is out today, but still this issue exists.

hi
yes 5586 installed
but still this issue exists
acronis 2016 addons is changed 300ko +
windows 10 stop acronis 2016 addons dangerous files !!!!

if I want to reinstall the files "AcronisTrueImage2016_addons" which has a 300ko difference compared to the old, the windows 10 block me executions and I have no choice there tell me it's dangerous files

acronis cloud 2016 build 5586 and new AcronisTrueImage2016_addons.exe + 300ko
the creation of a cd under WinPE works well now,
so everything is ok in 2016 acronis for me,
I just have to test both size on another if the SSD restoration no error,
do not forget in the build downloaded 5586 + AcronisTrueImage2016_addons.exe
who change
goood job to programmers

with winpe in version 8.1
of Windows 7
it works,
no needs or WDK10 ADK10
or c +++ 2015 or Visual Studio 2015

since Windows 8, Windows will warn users about files that haven't been downloaded many times (Smarscreen filter) and so flagged as potential insecure.

In this warning dialogue choose > more information (left bottom) and proceed with your download.