question

obujuwami avatar image
0 Votes"
obujuwami asked SimonRenMSFT-3639 commented

Odd MDT errors

Hey all, I've never seen these errors before when updating my deployment share, and I am hoping someone can explain what is going on here:

=== Making sure the deployment share has the latest x86 tools ===
=== Making sure the deployment share has the latest x64 tools ===

=== Processing LiteTouchPE (x64) boot image ===

Building requested boot image profile.

System.Management.Automation.CmdletInvocationException: Unable to open the specified WIM file. ---> System.Exception: Unable to open the specified WIM file. ---> System.ComponentModel.Win32Exception: The system cannot find the path specified
--- End of inner exception stack trace ---
at Microsoft.BDD.Core.BDDWimFile..ctor(String wimPath, Boolean forUpdate)
at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.UpdateBootImage(String template, String platform, String dpPath, Boolean createISO, String isoName)
at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
--- End of inner exception stack trace ---
at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
at Microsoft.BDD.Wizards.UpdateProgress.WizardProcessing()
at Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()

mem-mdt
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

A bit of an update. I read the output file and it seems like the issue here had to do with a wim not being found/generated. I dug deeper into the properties of the deployment share and discovered that when I go to the WIndows PE section, I get an unhandled exception error in managed code snap-in: Could not find a part of the path 'C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs'. Specifically, the WinPE folder seems to be missing from the Assessment and Deployment folder, which is causing the x86 area of the WinPE tab to bork.

I did recently update my ADK to the latest version as to resolve a restarting black screen issue when capturing an image. I'm guessing this may be the source of the problem, but I'm not sure. Thoughts?

0 Votes 0 ·

1 Answer

SimonRenMSFT-3639 avatar image
0 Votes"
SimonRenMSFT-3639 answered SimonRenMSFT-3639 commented

Hi,

Thanks for posting in Microsoft Q&A forum.

1,What version of MDT and Windows ADK you are using? Have you uninstall the Windows ADK and WinPE add-on, and then install the latest version of Windows ADK and WinPE add-on? Starting with Windows 10, version 1809, the Windows Preinstallation Environment (PE) is released separately from the Assessment and Deployment Kit (ADK), so we also need install WinPE add-on.
Similar thread for your reference: Unable to open the specified WIM file – error in MDT after upgrading to ADK 1809

2, Maybe the error is caused by antivirus software prventing access to the files. Please disable the antivirus software and restart your MDT server to have a try. Similar thread for your reference: Getting caught by your own permissions!
Please note: The links are not from Microsoft, just for your reference. Thanks for your time.

Best regards,
Simon


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Simon,

Thanks for responding. I didn't realize MS had separated the WinPE install from the ADK. Thank you for your help, it looks like that was the missing puzzle piece.

0 Votes 0 ·

Hi,

Thanks for your feedback. If you have any questions in future, we warmly welcome you to post in Microsoft Q&A forum again.

Have a nice day!

Best Regards,
Simon

0 Votes 0 ·