Select the product you need help with
A Windows Installer Package That Is Installed with Group Policy Does Not Restart the ComputerArticle ID: 811996 - View products that this article applies to. On This PageSYMPTOMSAfter you upgrade Microsoft Windows XP-based computers to Windows XP Service Pack 1 (SP1), a Windows Installer file
that is deployed by using Group Policy may not automatically restart the computer after
the package is installed. The computer may not restart even though the application log contains an MsiInstaller event ID
1005 entry with this message: "The Windows Installer initiated a system restart to
complete or continue the configuration of Update.msi." CAUSEPackages that require the computer to restart may not be able to restart
a computer. This occurs because of a change in the behavior of the InitiateSystemShutdown
function (Advapi32.dll) in Windows XP. The function does not set the last error to
ERROR_NOT_READY when it is called during the logon process in the console session of the Winlogon
process. If InitiateSystemShutdown does not work correctly and the last error is set to
ERROR_NOT_READY, Windows Installer now calls the ExitWindowsEx function to restart the computer. RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for Microsoft Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:322389
(http://support.microsoft.com/kb/322389/EN-US/
)
How to obtain the latest Windows XP service packHotfix informationA 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: http://support.microsoft.com/contactus/?ws=support 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. The English version of
this fix 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.
(http://support.microsoft.com/contactus/?ws=support)
Date Time Version Size File name ---------------------------------------------------------- 17-Feb-2003 09:37 2.0.2600.1168 2,012,160 Msi.dll 11-Feb-2003 14:21 2.0.2600.1168 64,512 Msiexec.exe 17-Feb-2003 09:37 2.0.2600.1168 305,664 Msihnd.dll 17-Feb-2003 09:37 2.0.2600.1168 847,872 Msimsg.dll 11-Feb-2003 14:21 2.0.2600.1168 36,352 Msiregmv.exe 17-Feb-2003 09:37 2.0.2600.1168 39,936 Msisip.dll STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows XP Service Pack 2. PropertiesArticle ID: 811996 - Last Review: August 29, 2007 - Revision: 3.2 APPLIES TO
|
Back to the top
