Tip

Fatal error when using Sysprep utility to clone Windows Vista machine

The few systems administrators who are already deploying Windows Vista are brave; they're the ones taking the arrows, running into problems the rest of us haven't seen yet.

One such intermittent problem occurs when an admin uses the Sysprep utility to prepare a Windows Vista system (typically for cloning). The error message that comes up simply reads: A fatal error occurred while trying to sysprep the machine.

Open up the Setupact.log file generated by Sysprep, and you'll find a bit more information: 0x80070020 / ERROR_SHARING_VIOLATION. This message is generated by the Microsoft Distributed Transaction Coordinator (MSDTC), a Windows component that shows up in nearly every Vista installation out there.

Microsoft's take on this is that the problem is more the fault of Windows Vista than Sysprep. Why? Here's my guess: When the MSDTC tries to reset its log, it discovers it can't do this because Sysprep has locked the log for exclusive access. Hence the error, and Sysprep itself aborts as well. Essentially, the two programs interfere with each other's operation. The problem appears to affect all SKUs of Vista.

There is a solution, but today it's only available as a free hotfix from Microsoft's Product Support Services. Call them and refer to

    Requires Free Membership to View

Knowledge Base article 930193. The solution involves patching two files: Msdtcprx.dll (to version 2001.12.6930.20502) and Xolehlp.dll (2001.12.6930.20502). Both 32-bit and 64-bit editions of the fix are available as needed.

Note: A vaguely similar error sometimes occurs when you run the sysprep -reseal command in Windows Vista, which logs the following error in Setuperr.log: Failed to delete reg value SystemIndexNormalization under reg key. A hotfix is available, but, again, only from Product Support Services. Refer to Knowledge Base article 929913.

Note: If you're not experiencing these problems with Sysprep and Vista, the hotfix isn't required. For now, this fix is only for people who are actually experiencing the issue. A fully regression-tested fix for everyone to use will show up in Service Pack 1 for Vista, which, by all accounts, will be out in the second half of 2007.

About the author: Serdar Yegulalp is editor of the Windows Insight, (formerly the Windows Power Users Newsletter), a blog site devoted to hints, tips, tricks and news for users and administrators of Windows NT, Windows 2000, Windows XP, Windows Server 2003 and Vista. He has more than 12 years of Windows experience under his belt, and contributes regularly to SearchWinComputing.com and SearchSQLServer.com.

More information on this topic:

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.