When you run the Sysprep MiniSetup Wizard to install a Microsoft Windows XP with Service Pack 2 (SP2) image, the wizard may stop responding after the video driver installation process starts. This problem occurs if the OempnpDriversPath entry in the Sysprep.inf file points to the latest Intel video drivers on the Dell Web site or on the Intel Web site.
You notice this problem if the Intel video driver is set up by using the Services.exe -setup
This problem occurs because of a problem with the graphical user interface (GUI) thread in the Services.exe process. When the Services.exe process starts, the following events occur in the following order:
- All statically-linked .dll files are initialized.
- The Acgenral.dll file loads the Shell32.dll file.
- The Shell32.dll file loads the Comctl32.dll file even though Services.exe never uses this binary.
- When the svcctrlMain thread for the Shell32.dll file runs a \ function, the svcctrlMain thread transforms into a GUI-mode thread. Additionally, the Services.exe process transforms into a GUI-mode process.
- The svcctrlMain thread stops running when the Services.exe process is still running.
When these events occur, all the GUI-mode aspects of Services.exe are ended, but Services.exe cannot return to GUI mode.
When the Intel device driver co-installer is started in the Services.exe process, the UpdateDriverForPlugAndPlayDevices
function calls the Newdev.dll file. The Newdev.dll file runs in the context of Services.exe because it is a plug-and-play process. However, there is no GUI-mode aspect to this process that is visible to the user. Therefore, Newdev.dll creates a silent file that has some default property settings. Then, Newdev.dll tries to run this file silently. However, Newdev.dll cannot run this file silently because Services.exe cannot return to GUI mode.
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.
To apply this hotfix, you must have Windows XP Service Pack 2 with (SP2) installed on the computer. You must have all the latest available Windows updates installed on the computer. You must have the KB883667 hotfix installed on the computer.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
The English version of this hotfix has the file attributes (or later file attributes) 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.
Collapse this tableExpand this table
|File name||File version||File
For more information about standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.