create-a-windows-10-reference-image
prepare-for-windows-deployment-with-mdt
With reference to the article mentioned above, I was making a custom image for MDT, and after being going to carry out Update Deployment Share, the following errors occurred.
== = =
== = Making sure the deployment share has the latest x86 tools = = =
== = Processing LiteTouchPE (x86) 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: An appointed pass is not found.
-- - End - - - of the internal exception stack trace
Place Microsoft.BDD.Core.BDDWimFile..ctor(String wimPath, Boolean forUpdate)
Place Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.UpdateBootImage(String template, String platform, String dpPath, Boolean createISO, String isoName)
Place Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.ProcessRecord()
Place System.Management.Automation.CommandProcessor.ProcessRecord()
-- - End - - - of the internal exception stack trace
Place System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
Place Microsoft.BDD.Wizards.UpdateProgress.WizardProcessing()
Place Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()
== = =
I tried following coping that check it, and seemed to correspond to a cause, but am not settled without error contents changing.
・Installation of WinPE and .NET Framework 3.5.1
・Reinstallation of MDT, ADK, WinPE
MDT reads Windows 11 ,so it is slightly different from the contents of the article that I referred to in environment.
But I think it is the environment factor , not Deployment Share setting error.
Because it is occured a similar error even if I do Update in empty Deployment Share which does not read the OS and the application.
I do not know whether it is related to this question, but wear the following errors when I cut a tab of WinPE open with a property of Deployment Share which I made.
For your information.
"an error of the snap in was detected by MMC, snap in is unloaded."