While testing unattended Windows deployment I encountered another problem.
After the first installation reboot, Windows setup would fail with the error message:
Windows could not parse or process unattend answer file [C:\Windows\Panther\unattend.xml] for pass [specialize]. The answer file is invalid.
When closing the dialogbox the computer restarted.
Then it failed with this error message:
The computer restarted unexpectedly or encountered an unexpected error. Windows instalation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the installation.
Started troubleshooting by booting into Windows PE.
Started examining the log files under:
Found these error messages in setupact.log:
IBS The provided unattend file is not valid; hrResult = 0x80220005 IBS Callback_Unattend_InitEngine:The provided unattend file [C:\Windows\Panther\unattend.xml] is not a valid unattended Setup answer file; hr = 0x1, hrSearched = 0x1, hrDeserialized = 0x0, hrImplicitCtx = 0x0, hrValidated = 0x1, hrResult = 0x80220005 IBS UnattendErrorFromResults: Error text = Windows could not parse or process unattend answer file [C:\Windows\Panther\unattend.xml] for pass [specialize]. The answer file is invalid. IBS Callback_Unattend_InitEngine:An error occurred while finding/loading the unattend file; hr = 0x1, hrResult = 0x80220005
This didn’t reveal the exact cause of the error, but it inspired me to examine unattend.xml.
I transferred unattend.xml to my work computer and then tried opening the unattend.xml file with Windows System Image Manager.
However this failed with:
Validation error on D:\ToBeDeleted\Fail_Info\Panther\unattend.xml, line 18, column 32. Details: The 'wasPassProcessed' attribute is not declared.
Opened the unattend.xml file in an editor and removed all instances of:
After that the file could be opened in Windows SIM, which now displayed the real error:
The 'ComputerName' element is invalid - The value 'DeployTestPhysical' is invalid according to its datatype 'ComputerNameType' - The actual length is greater than the MaxLength value.
So the problem was that computer name was too long…
The unattend.xml file was modified by a custom program just before deployment on the target computer.
This custom program did not prevent computer names longer than 15 characters.
The problem was fixed by updating the custom program.
Special care should be taken when modifying unattend.xml by scripts or programs.
An invalid unattend.xml file may cause problems during Windows setup, which are not immediately obvious.