MVP_ATIPEBuilder_v186 Problem
Hi. Tried running MVP_ATIPEBuilder_v186 a few times, but it always fails - I think because of DISM. Herewith the latest log, Can you spot the problem?
Also, herewith a png which shows relevant error actions when running the Builder.
Regards
Allegato | Dimensione |
---|---|
MVP_ATIPEBuilder_12-10-2019_09.15.36.txt | 6.52 KB |
2019-10-12_12-16-17.png | 19.36 KB |

- Accedi per poter commentare

WAS, the key error that I see in the MVP log is:
Deployment Image Servicing and Management tool Version: 10.0.17134.1 Error: 50 DISM does not support servicing a Windows Vista RTM or earlier operating system. If the operating system is supported check that SSShim.DLL is present. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
Have you followed the advice given above, i.e. checked that SSShim.DLL is present in your Windows 10 OS (C:\Windows\System32 folder)?
What is shown in the DISM log at the location shown above?
Have you tried running the MVP builder tool without injecting any device drivers?
Are you using Acronis Mobile backup on your system? The reason for asking is that your destination for the ISO & WIM files is on drive M: which is 'stolen' by Acronis Mobile for use by Acronis Drive to show mobile backup data.
- Accedi per poter commentare

Where is the tool being run from? It seems to either not like your username in your profile (it is not using the full path and is instead using a ~ in the path where your appdata folder (temp directory) should be and seems to be hanging there.
Make sure you are not running it from your user profile. Instead, copy the builder to the root of your C: drive or your M: drive and run it from there and see if that helps.
Also, I'd try it without using the local system drivers injection (which uses a third party tool doubledriver). Hopefully, just moving the start location will help out... if not then, on top of that, leave double driver out and see if that helps.
Last... the ADK you're using is 1803 but your OS is 1809. Although this usually doesn't matter, may be causing a issue. I'd remove ADK 1803 and install 1809. Keep in mind, you need to download the ADK and the WinPE add-on separately and install them both since 1803 too.
- Accedi per poter commentare

Bobbo_3C0X1 wrote:I'd remove ADK 1803 and install 1809. Keep in mind, you need to download the ADK and the WinPE add-on separately and install them both since 1803 too.
What's the right way to remove the old ADK. I know I have not updated mine to 1903.
Looking at the Control Panel->Programs and Features, I see...
Windows Assessment and Deployment Kit - Windows 10 (Version 10.1.17763.1)
Windows Assessment and Deployment Kit Windows Preinstallation Environment Add-on - Windows 10 (Version 10.1.17763.1)
Am I correct that these are the two things you mention and I should just uninstall from Control Panel?
I also have the following three things listed, all with an install date about two weeks after I got the PC 2.5 years back...
Windows Deployment Tools (Version 8.59.25584)
Windows PE x86 x64 (Version 8.59.25584)
Windows PE x86 x64 (Version 8.59.25584)
Should they be there?
EDIT: I'm not 100% certain, but I believe these 8.59.25584 items may have been installed when I installed Avast Free Antivirus, in order to create the bootable AV drive.
- Accedi per poter commentare

Just a quick note. I got the versions mixed up earlier.
Your OS is 10.0.17134 - 1803
Your ADK is 10.0.17763 - 1809
Your ADK is actually pretty new - 1903 is the latest, so shouldn't hurt to upgrade to get the best driver compatibility (10.0.18362 - 1903)
--------------------
If you are going to upgrade, yeah, remove the 2 entries listed above
- Windows Assessment and Deployment Kit - Windows 10 (Version 10.1.17763.1)
- Windows Assessment and Deployment Kit Windows Preinstallation Environment Add-on - Windows 10 (Version 10.1.17763.1
The other 2, not sure about those - it's odd that another program would specifically have it's own ADK in control panel. It's not entirely odd that other tools have ADK builders - other tools have them embedded into their program or will use the system ADK. That version is from an older ADK for Windows 8 and I believe that could be your issue now.
Windows ADK for Windows 8 | 8.59.25584 | Dec. 2012 |
Personally, I'd remove all of them, reboot, then grab the latest 1903 (both the deployment kit and preinstallation add-on again) and install them, reboot for good measure again (to finish up any registry changes) and try to build the rescue media again after that. Remember to run the MVP tool from somewhere other than your user profile too - it's best to run it from the root of the drive or some other folder that is not in any user profile, not in program files, or any Windows system folders to avoid issues in the script that may try to use the shortname of the userprofile instead of the full path.
- Accedi per poter commentare

Rob, thanks for answering me... but I'm not the OP.
Slight typo above. It's three things for the old ADK
Windows Deployment Tools (Version 8.59.25584)
Windows PE x86 x64 (Version 8.59.25584)
Windows PE x86 x64 wims (Version 8.59.25584)
So if, through Control Panel, I remove all five of these things I should be good to go, right? I can then load the latest 1903 stuff.
I also notice that I have two folders
C:\Program Files (x86)\Windows Kits\8.0
C:\Program Files (x86)\Windows Kits\10
I'm assuming the version 8.59.25584 is what's in the 8.0 folder and the version 10.1.17763.1 is in the 10 folder. Does that makes sense? And if I remove all five, the folders should hopefully be removed?
- Accedi per poter commentare

Thanks Bruno - apparently I'm mixed up. I got your PM today and think you're on the right track with removing the old versions and installing 1903.
For OP (was): if you return to the thread... same question as before, where are you launching the MVP tool from? It seems like it may be running under your user profile (desktop, downloads, etc) and could be the problem as the script sets the run path to the local folder, but Windows tends to use the short path there
Andrew~2
instead of the full name and that can break the variables in the script.
- Accedi per poter commentare