Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. This article is intended for software developers who are using Windows Installer to build installer packages for their applications.
If you need support for a Microsoft product, please go to our technical support site at support. The error codes detailed in this topic are returned by the Windows Installer, and have error codes of or greater. The error codes numbered to are ship errors and must be authored into the Error table.
The error codes numbered greater than are internal errors and do not have authored strings, but these can occur if the installation package has been incorrectly authored.
For error codes specific to the Windows Installer functions MsiExec. For a list of reserved error codes, see Error table. You can search the Internet or the Microsoft support site for solutions to many of the messages in the following table. Developers of installation packages can also test the internal consistency of their packages by using Internal Consistency Evaluators.
Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Note If you need support for a Microsoft product, please go to our technical support site at support. In this article. The file '[2]' is in use. If you can, please close the application that is using the file, then click Retry. A system restart may be required because a file being updated is also currently in use.
For more information, see System Reboots. There is not enough disk space remaining to install this file: [2]. If you can, free up some disk space, and click Retry , or click Cancel to exit. Cannot create the directory '[2]'. A file with this name already exists. Please rename or remove the file and click Retry , or click Cancel to exit. A portion of the folder path '[2]' is invalid.
It is either empty or exceeds the length allowed by the system. Error applying patch to file [2]. It has probably been updated by other means, and can no longer be modified by this patch. For more information, contact your patch vendor. System Error: [3]. A file that is required cannot be installed because the cabinet file [2] is not digitally signed. This may indicate that the cabinet file is corrupt. A file that is required cannot be installed because the cabinet file [2] has an invalid digital signature.
The file '[2]' cannot be installed because the file cannot be found in cabinet file '[3]'. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package. The cabinet file '[2]' required for this installation is corrupt and cannot be used.
There was an error creating a temporary file that is needed to complete this installation. Folder: [3]. System error code: [2]. Could not increase the available registry space. Another installation is in progress. You must complete that installation before continuing this one. Test packages in high-traffic environments where users request the installation of many applications. Error accessing secured data. Please make sure the Windows Installer is configured properly and try the install again.
User '[2]' has previously initiated an install for product '[3]'. That user will need to run that install again before they can use that product. Your current install will now continue. The file [2][3] is being held in use by the following process: Name: [4], Id: [5], Window Title: '[6]'. A system restart may be required because the file being updated is also currently in use.
The product '[2]' is already installed, and has prevented the installation of this product. If rollback is disabled, enough space is available. Click Cancel to quit, Retry to check available disk space again, or Ignore to continue without rollback. Do not list directories in the Directory table which are not used by the installation. Rarely, this message is due to the issue discussed by KB A system restart may be required because a file that is being updated is also currently in use.
Users may be given the opportunity to avoid some system restarts by selecting to close some applications. Could not find any previously installed compliant products on the machine for installing this product. No file listed in the CCPSearch table can be found on the user's computer. An error occurred while applying security settings. This could be a problem with the package, or a problem connecting to a domain controller on the network.
Check your network connection and click Retry , or Cancel to end the install. Unable to locate the user's SID, system error [3]. The setup must update files or services that cannot be updated while the system is running.
If you choose to continue, a reboot will be required to complete the setup. The setup was unable to automatically close all requested applications. Please ensure that the applications holding files in use are closed before continuing with the installation. Admin user failed to apply patch for a per-user managed or a per-machine application which is in advertise state. Configuring [2] cannot be completed until you restart your system. To restart now and resume configuration click Yes , or click No to stop this configuration.
A scheduled system restart message. This message may be customized using the Error table. For the configuration changes made to [2] to take effect you must restart your system. To restart now click Yes , or click No if you plan to manually restart at a later time.
The scheduled system restart message when no other users are logged on the computer. An install for [2] is currently suspended. You must undo the changes made by that install to continue.
Do you want to undo those changes? A previous install for this product is in progress. Server Fault is a question and answer site for system and network administrators. It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search. I have a brand-new machine that we just installed Windows Server Enterprise on about two months ago. In the event log, I am seeing thousands of EventID logged. This is MsiInstaller reconfiguring about a dozen products over and over, looping about every half-hour.
Has anyone seen this? As a beginning, I did a general web search, and most solutions revolved around Dell System Center or Google toolbar being installed as the culprit.
None of this was documented before as a bad thing, actually as the proper way to do it. I think the choice by Microsoft to do a repair check at the same time as responding to the query is just bad design.
A query should never cause changes to a system, that should be a different "function" WMI method. Anyway this was an old server, actually about to be decommissioned Windows 64bit. But it did happen on all of our servers for many years that was a major hit to performance now it's confirmed.
So I'll have to check again on the newer R2 servers to see if this will be an ongoing production issue or not. We've got hundred of scripts and tools written by lots of different people for s of packages.
There's no way it'll ever happen. So this behaviour should be fixed as a critical design fault by MS if it's still occurring in R2 and other supported OS versions. We'll certainly escalate it if it's still the case! Windows Installer features " self repair " for installed applications.
In essence this means that it will keep checking whether the files on disk and settings in the registry match what the respective package originally installed. These checks are generally not performed for everything that the package installed, but for what is referred to as " key paths ".
In situations where you see self repair running in cycles , it generally means that some process on the system or another MSI has changed settings on the system that the package that subsequently self-repairs also changed. Like the guy said, it's like a humidifier and a dehumidifier fighting it out in the same room - or a dog chasing its own tail.
If you have an application that uses the previous class, contact the vendor to get an updated version that doesn't use this class. To narrow down the application that causes the problem, you can follow the Clean boot troubleshooting method.
This process also starts a consistency check of packages installed, verifying, and repairing the install. An account with only user privileges may cause delay in application launch and an event stating an installation failure, as the user account may not have access to quite a few locations.
Skip to main content. This browser is no longer supported.
0コメント