21 August 2014

Home » » Windows Could Not parse or process unattend answer file for pass

Windows Could Not parse or process unattend answer file for pass

  Thursday, August 21, 2014    No comments
This error message was caused, at least in my situation, by the addition of Internet Explorer 11 into the build. It was not integrated, but installed in the golden image as an application. When applying the golden image, the above mentioned error occurred. Luckily, this thread came up with the resolution to comment out <IEWelcomeMsg>false</IEWelcomeMsg> located in the unattend.xml file in the %deployroot%\control\<ImageName> folder. Once I did that, the issue was resolved. You can comment it out by changing the line as follows:

<IEWelcomeMsg>false</IEWelcomeMsg>

TO

<!-- <IEWelcomeMsg>false</IEWelcomeMsg> -->

Related Posts:

  • Windows Could Not parse or process unattend answer file for pass This error message was caused, at least in my situation, by the addition of Internet Explorer 11 into the build. It was not integrated, but installed in the golden image as an application. When applying the golden image, the… Read More
  • Cleaning up old task sequences If you ever go into the Control folder of the deployment share, you will see every task sequence that has ever been created in there. They are listed by sub-folder names. MDT does not delete these when you delete a… Read More
  • WARNING - unable to set working directory: (-2147024894) This error is caused when the working directory no longer exists that is assigned to the application being installed. It would be nice if MDT published which app it is, but it does not. To find the application, open up the B… Read More
  • MDT 2013 and Pentium 4 Systems My firm is getting the first tablet machines in that will be Windows 8.1. This requires MDT 2013 and ADK 8.1. The problem is that we still have a few machines that are Pentium 4 systems, specifically Dell Precision Workstati… Read More
  • Message containing password has been suppressed error In my experience, this error was caused by me manually editing the unattend.xml file associated with an imported operating system. Specifically, I had manually entered the UnattendedJoin credentials within the unattend.xml f… Read More

0 comments:

Post a Comment