Vjz1
asked on
Windows 7 will not boot after sysprep
Hi,
I am building an image of Windows 7 Enterprise edition. after creating a simple unattend file in WAIK. After running sysprep, when the machine boot up i get the following:
"Windows could not parse or process the unattend file for a pass [specialize]. The Setting specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-S etup]."
If i remove it the image will boot. The problem is i want to use that specialize option.
Have anyone run into this and have a solution for it?
I am building an image of Windows 7 Enterprise edition. after creating a simple unattend file in WAIK. After running sysprep, when the machine boot up i get the following:
"Windows could not parse or process the unattend file for a pass [specialize]. The Setting specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-S
If i remove it the image will boot. The problem is i want to use that specialize option.
Have anyone run into this and have a solution for it?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I also experienced a very similar issue and had to remove a particular piece of software to get the copyprofile command to work during sysprep in Windows 7 Enterprise. If you have the patience I actually recorded 2 videos showing success and failure of sysprep due to the software:
Sysprep failing with error: "Windows could not parse or process the unattended answer file for pass [specialize]."
http://www.screencast.com/t/xZyWWNvUI
Sysprep success! (after software install)
http://www.screencast.com/t/8FMoqHJW7gL
I hope this helps as I have seen ALOT of posts about this error. I tried many many resolutions including rebuilding the XML answer file using different images, removing all accounts except administrator from User Manager, Registry, and from C:\Users all to no avail.
This worked! So lessons learned, it could be a piece of software preventing the copyprofile command from executing properly.
Sysprep failing with error: "Windows could not parse or process the unattended answer file for pass [specialize]."
http://www.screencast.com/t/xZyWWNvUI
Sysprep success! (after software install)
http://www.screencast.com/t/8FMoqHJW7gL
I hope this helps as I have seen ALOT of posts about this error. I tried many many resolutions including rebuilding the XML answer file using different images, removing all accounts except administrator from User Manager, Registry, and from C:\Users all to no avail.
This worked! So lessons learned, it could be a piece of software preventing the copyprofile command from executing properly.
EagleMed-IT:
How were you able to tell if the issue related to that specific piece of software? That was interesting to see and I have alot more software loaded into my image than you do with the same specialize pass error.
Thanks
How were you able to tell if the issue related to that specific piece of software? That was interesting to see and I have alot more software loaded into my image than you do with the same specialize pass error.
Thanks
Hello all first post here. I just spent a little time creating an image and ran sysprep to complete the image for deployment. However I am getting the Windows could not parse or process the unattend answer file for pass specialize..........yada yada yada same as above. I didn't create an image prior to running sysprep. Is there away to get back into Windows or am I looking a starting over?
I would think that you are most like going to get into a "sysprep loop" and wont be able to get past it without disabling the offending service / application.
To address sparky's question, the image didnt contain too many applications so process of elimination. It so happens that was the 2nd or 3rd one that I tried. Pure Luck!
To address sparky's question, the image didnt contain too many applications so process of elimination. It so happens that was the 2nd or 3rd one that I tried. Pure Luck!
Are you using a single word PC name in your unattended setup?
Some, but not very cheerful solution from Microsoft:
http://support.microsoft.com/kb/934308
http://support.microsoft.com/kb/947303
You've probably already read this article, but it might reveal some WAIK issues.
http://technet.microsoft.com/en-us/library/dd349350(WS.10).aspx