Sysprep errors are logged in the Setuperr.log file when you run the “Sysprep /generalize /oobe” command on a Windows Vista-based computer
Consider the following scenario:
- You are running a Windows Vista-based computer.
- You run the following command:
Sysprep /generalize /oobe
In this scenario, Sysprep errors that resemble the following are logged in the Setuperr.log file:
SYSPRP MSS: Error 0×0 occurred while stopping service WSearch.
SYSPRP MSS: _StopService exits on timeout.
SYSPRP MSS: Plugin failed to stop Windows Search service, trying to kill it…
SYSPRP MSS: Error 0×425 occurred while stopping service WSearch.[gle=0x00000425]
SYSPRP MSS: _StopService exits on timeout.[gle=0x00000425]
SYSPRP MSS: Failed to kill Windows Search service![gle=0x00000425]
Additionally, you must now restart the Sysprep tool.
Note: The Setuperr.log file resides in the following location:
Windows\System32\Sysprep\Panther
For more information on this issue, including potential causes, workarounds, and resolutions, see: Microsoft KB Article KB941821.

Start
About
FAQ
Blogroll
Shop
Tips and Tricks
Windows Updates
Hotfixes
Keyboard Shortcuts
Vista's Services
Vista's Commands
Product Reviews
Glossary
Videos
Web Links

Comments
There are no comments yet...Come on, share your thoughts!
Leave a Comment