Windows installation errors
An installer failed and gave you a number. These pages say what each code actually means, and list the fixes in order of how often each one turns out to be the answer.
We cover installation and file errors, because that is what this site is about. For anything else Windows throws at you, this is not the right place and we would rather say so than pad the list.
- 1603Fatal error during installation
- 0x80070643Fatal error during installation
- 1618Another installation is already in progress. Complete that installation before proceeding with this install.
- 1619This installation package could not be opened. Verify that the package exists and that you can access it.
- 1601The Windows Installer Service could not be accessed.
- 1638Another version of this product is already installed. Installation of this version cannot continue.
- 2502 and 2503The installer has encountered an unexpected error installing this package. Called RunScript when not marked in progress.
- 0x80070570The file or directory is corrupted and unreadable.
- 0x80004005Unspecified error
- 1935An error occurred during the installation of assembly component
- 0x80070005Access is denied
- 0x800f081fThe source files could not be found
- 0x80070002The system cannot find the file specified
- 1722There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected.
- 1327Error 1327. Invalid Drive: X:\
- 1606Error 1606. Could not access network location
- 1310Error 1310. Error writing to file. Verify that you have access to that directory.
- 1402Error 1402. Could not open key: HKEY_LOCAL_MACHINE\...
- 1625This installation is forbidden by system policy. Contact your system administrator.
- 1620This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
- 1721There is a problem with this Windows Installer package. A program required for this install to complete could not be run.
- 0x8007000dThe data is invalid
The step almost nobody takes
Before debugging an installer, confirm the installer is intact. A truncated or modified download produces errors that look like configuration problems and waste hours. Check the file's SHA-256 against our index first: it takes seconds and rules out an entire category of cause.