1803 DISM Issues

Couple of issues.
Recently updated to SCCM 2012 R2 infrastructure 1802 (Server 2012 R2 Data Center) 
Currently running the WADK 1709 with boot.wim(s) of this version. Console reported 1802 available ran the prereq which passed so ran the setup for 1802 which during the middle of the install hung. 

Ended up uninstalling the DP then reinstalling DP as I could not get a TS to properly run nor pixie boot to offer advertisements consistently. It was successful after redistributing the content associated with the TS's I can now deploy .

Uninstalled the 1709 WADK rebooted installed the 1803 WADK successfully rebooted.

Making plans to test Win 10 1803 so downloaded the WADK for 1803 and the .iso for 1803.
Attempted to run the dism cmd's to mount and make the wims available to import into CM console.
Created the appropriate directories  1803_Boot_Wims\ WINPEx86 and WINPEx64 respectively. 
Know that the directories are properly named as running the following cmd; 

Copy "E:\WADK_1803\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim" E:\1803_Boot_Wims\WINPEx86\boot.wim 

Successful copied 

Then ran:

dism.exe /mount-wim /wimfile:E:\1803_Boot_Wims\WINPEx86\boot.wim /index:1 /mountdir:E:\1803_Boot_Wims\WINPEx86\mount
Fails with error:
Deployment Image Servicing and Management Tool
Version 10.0.17134.1
Error: 0xc1420115
The user attempted to mount to a directory that does not exist. This is not supported.
DISM log file blah blah blah.

So performed same procedure for x64 same results?

Been trying to resolve this for a couple of days now without success?

Any Help would greatly be appreciated.

0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ