Is the problem of loading DISM after launching an MSHTA, described here 
https://blogs.technet.microsoft.com/mniehaus/2015/12/31/updated-remove-apps-script-and-a-workaround
fixed by that Hotfix for WinPE 1511 ADK 
https://support.microsoft.com/en-us/kb/3143760 - or is that an entirely 
separate problem?

I have been reading a bit on this and can't figure out what the best way to 
correct this problem of DISM not loading correctly during MDT.

Some say that that creating a .config file as Micahel's post suggests is not 
enough.  Other blogs say you have to copy a DLL out of the WAIK toolkit.

I see that the copy of Microsoft.Dism.PowerShell.dll included in the 1511 ADK 
at "Program Files (x86)\Windows Kits\10\Assessment and Deployment 
Kit\Deployment Tools\amd64\DISM" has an MD5 hash of 
31632e90280046d2efb020f7dcb23ab5

The copy of Microsoft.Dism.PowerShell.dll that gets installed by importing the 
DISM package into the WinPE image using the component import - and gets stored 
in the x64 WinPE.WIM at Windows\System32\WindowsPowerShell\v1.0\Modules\Dism is 
a different MD5 hash  71316d0f6f255f59efbe601f7dc33a58

The rest of the files in the WinPE 
Windows\System32\WindowsPowerShell\v1.0\Modules\Dism - the MD5 hash does match 
what is in the ADK.

People mention that it works to copy the version of the DLL that is included in 
the ADK over the top of what is in the WinPE boot once the computer is booted 
into WinPE - so that leads me to believe there is a problem with DISM component 
that makes it import the incorrect copy of the DLL.

The post Michael made about fixing this is from New Years Eve  - so has there 
been any update on the best way to correct the DISM vs MSHTA problem?

Not sure which thing to try... they are all kind of a pain to implement so I 
would like to fix it the best way first rather than try a bunch of things.

I tried mounting my LiteTouch WIM and then copying the 
Microsoft.Dism.PowerShell.dll file from the ADK over the top of the one in the 
WinPE's WIM file but I'm getting access denied - it is owned by Trusted 
Installer.  And even when I took owenership, I still couldn't delete or replace 
the file in the WIM and I tried lots of ways...

Anywho - Ideas?



________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the 
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is intended only 
for the use of the individual or entity to which it is addressed, and may 
contain information that is privileged, confidential, and exempt from 
disclosure under applicable law. If you are not the intended recipient, any 
dissemination, distribution or copying of this communication is strictly 
prohibited. If you have received this communication in error, please notify the 
sender immediately and delete or destroy all copies of the original message and 
attachments thereto. Email sent to or from UI Health Care may be retained as 
required by law or regulation. Thank you.
________________________________

Reply via email to