This article was previously published under Q254382
This article has been archived. It is offered "as is" and will no longer be updated.
This article may contain a link to the Windows Installer Cleanup utility (MSICUU2.exe). If you were directed to this article to solve a problem by using the Windows Installer Cleanup utility, please contact your software manufacturer for installation support on the product, or see the following Microsoft Knowledge Base article for steps to troubleshoot uninstallation issues with products that use Windows Installer:
How to troubleshoot problems that may occur when you install, uninstall, or upgrade a program on a Windows-based computer
Windows 2000 includes a Winnt32.msi file that you can use to upgrade previous versions of Microsoft Windows NT and Windows 2000. This file is used as a wrapper to start Winnt32.exe.
Typically, a Group Policy object (GPO) is created that assigns Winnt32.msi to computers in the domain to upgrade the operating system. This works as long as a user does not experience any unforeseen problems. If there is a problem (for example, not enough disk space) Microsoft Software Installer (MSI) still pushes the installation to the client, but the installation does not succeed. In this case, the installation may seem to succeed even though it does not. When the user corrects the problem and restarts the computer, the Winnt32.msi part of the policy is not reapplied because the installation appeared to be successful.
To correct this, the administrator must remove the registry entries from the client so that the policy is reapplied, or use the Windows Installer CleanUp utility from the Customer Support CD-ROM.
The Winnt32.msi file was created only to install Windows 2000, it does not check for disk space. It checks only for a 16-KB temp file to start Winnt32.exe.