VMware: Windows could not parse or process the unattend answer file for pass [specialize]
Today I deployed my new created Citrix XenDesktop 7.6 base image with Windows 8.1 u1 template and Customization file, during the customization process I received this error message:
Windows could not parse or process the unattend answer file for pass [specialize]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup].The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click “OK” to restart the computer, and then restart the installation.
This issue can have multiple causes. Some common causes include, but are not limited to:
- Bad Product Key
- Invalid Device Drivers
- Invalid Computer Names
- Issue with the Admin Account being used
- An installed application breaks the unattended install process
This resolution is based on the source of the error, to troubleshoot this issue, review the Microsoft Setup log setupact.log file.
Note: The Microsoft Setup log file is located at c:\Windows\Panther\unattendGC\setupact.log.
To view the log file from a computer currently displaying the error, press Shift + F10 to open a command prompt and run this command: notepad c:\windows\panther\unattendGC\setupact.log
In my case I configured in the Customization Wizard a Windows 8.1 MAK license key, the configured template OS was an VLK edition…
8 thoughts on “VMware: Windows could not parse or process the unattend answer file for pass [specialize]”
As soon as the error appears, Hit Shift+F10 to get a cmd prompt
then open up regedit
Look for HKEY_LOCAL_MACHINE -> SYSTEM -> Setup ->Status -> ChildCompletion
Now look in the right hand pane for setup.exe, if the REG_DWORD value data is set at 1 then change it to 3
Reboot and hopefully the OS installation will pick up as normal.
Thanks! It was the wrong license key for me.
cool, thanks was looking for this
Thanks, it was my computer name that had too many characters
Many thanks for your post. In my case it was a wrong license key!
That’s what I needed! Had a wrong character in the product key.
Changing that setting in the registry worked but, why? I can’t do that with every deployment.