Post-installation scripts do not install programs successfully when Windows Server 2003 is installed from a Sysprep image

When you configure a script or a batch file to install programs immediately after Microsoft Windows Server 2003 is installed, the programs that the script or that the batch file installs are not installed correctly.

Note You only experience this problem when Windows is installed from a Sysprep.exe image.

This problem occurs when the script or the batch file installs programs that must register components with the Windows Management Instrumentation (WMI) service. In this scenario, when Windows restarts after being installed from a Sysprep image, and when components try to register with the WMI service, the following behaviors occur:

• The first component registration is successful.
• Subsequent component registrations are unsuccessful.

This problem occurs because the Winmgmt.exe process is not completely initialized when the computer restarts after the installation is complete. Typically, the Winmgmt.exe process requires about 2 to 4 minutes to be initialized when Windows first starts after it is installed from a Sysprep image. When Windows starts, WMI creates an inventory of all the driver additions and class additions to the Web-Based Enterprise Management (WBEM) repository. During the first restart after Windows is installed, there are many driver and class additions. Therefore, the Winmgmt.exe process requires additional time to initialize.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required to install this hotfix.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Microsoft Windows Server 2003, 32-bit editionsMicrosoft Windows Server 2003, 64-Bit Enterprise Edition

To work around this problem, insert a delay in the script or the batch file that starts when the Windows installation is complete. If you insert a delay of about 5 minutes between the time that Windows starts and the time that component registration starts, the WMI service does not hang, and all components are successfully registered.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base: