I have been using a virtual windows 7 machine for testing sysprep scenarios for a rollout shortly. Problem is no matter what configuration i put the machine in (Apps, no apps, updates, no updates), I always get a "windows could not parse or process unattend 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-s
I have also found that the Windows Media Player Network Sharing Service (WMPNetwk.exe) could sometimes cause these types of errors, so i always stop the service and disable before running sysprep with my unnattend file. I have also tried running with a MAK volume licensing key in the unnatend and also without to no avail. Each time, I revert back to a clean image and do my test again so that i don't have to worry about the re-arm scenario with activation.
I'm literally at my wits end with this one. At first, i thought it might be a software App issue so i even tried with a snapshot image with no 3rd party Apps added but still fails.
What's interesting is that i can usually run a 'virgin' sysprep install with the generalize switch and no unnatend file fine most times. It's only when i try to apply the unattend that i get the windows could not parse type error. For this reason, i had created a very skeleton version of the unnatend with just the specialize and oobe passes applied. I really need to get this working in order to apply the CopyProfile setting from specialize in order to build a default profile for the machine that will give users a standard feel when logging in.
I am attaching three files here: the original windows could not parse error, the specialize pass (i had to blur out our product key for privacy reasons) and the oobe pass - all with various settings applied. Can someone take a look at these files and possibly shed some light on what is going on?
500 points to a solution. Thanks again guys