Reboot Required?: could this be a simple "reboot required issue". 1603 can mean "reboot required" in batch files.
- Did you run the batch file with admin rights?
- Does this MSI have any custom actions? If so, where are they located in the
InstallExecuteSequence? - There are other possibilities (resurrected from WayBack Machine). Inlining the main section here for the future:
From link above: The following is a non-exhaustive list of known causes for this error:
- Short file name creation is disabled on the target machine.
- An Install Script custom action is prototyped incorrectly.
- A file is locked and cannot be overwritten.
- The Microsoft Windows Installer Service is not installed correctly.
- The Windows Temp folders are full.
- The setup was corrupted after installation and, therefore, fails with this error during un-installation.
- An older version of Install Shield Developer is being used.
- A general error occurred during the installation.
- Print and File sharing is not installed or enabled when installing MSDE 2000.
Proposed solutions in linked document above:
1)Make sure short file name creation is enabled on the target machine,2)Make sure Windows Installer is properly installed,3)Empty all temporary folders,4)Close all running applications and utilities, and launch the installation again - especially antivirus tools, and5)a couple more options.
You need to gather more information - which leads to checking for logs:
Standard debugging:
Event Logs: What does the
event logssay? (Windows + Tap R. typeeventvwrand press OK). Check the different logs.MSI Log File: Did you create an MSI log file?
There could be policies in effect to automatically create one. Check in the
TMP folder, sort by date and check recent files for any*.log files.Also check in the batch file if it hard codes a location for the MSI log file.
If you find an MSI log file, try searching for "value 3" (without the quotes) to find any actions that failed.
- Windows Installer Error Messages.
- MsiExec.exe and InstMsi.exe Error Messages.
How to create an MSI log file:
- How to create an MSI log - short version
- Long answer with MSI logging tips
Reddit
reddit.com › r/pdq › msi 1603 error via pdq, but works when run manually
r/pdq on Reddit: MSI 1603 error via PDQ, but works when run manually
January 10, 2024 -
Hello,
I posted this same question on the PDQ forum's but thought I might get more responses here.
Full details and screenshots in the link above, but essentially I have Deploy package with step to install an MSI, which is failing with error code 1603. The output log suggests this is due to a file in use, which might be related to Windows Search service. Creating a pre-step to stop this service doesn't help.
Also, what I find odd, is running this same exact command logged in locally as the same PDQ deploy user, completes this install with success code 0.
Seen anything like this before?
Top answer 1 of 2
1
You should also try PDQ’s Discord server. Edit: have you tried adding a reboot and sleep step before 15 to see if a reboot might “unlock” the .dll
2 of 2
1
Go to the Options tab of the step that is giving you trouble. Try changing "Run As" to Deploy User (Interactive). Error 1603 is a very generic error code. Looking at the logs you posted in the PDQ forum, it looks like it is failing due to Solidworks DLLs that are locked. From your post, I'm not sure why you think Windows Search service is the culprit. If Deploy User (Interactive) doesn't work, you should look at killing whatever process has those DLLs locked.
Microsoft Learn
learn.microsoft.com › en-us › troubleshoot › windows-server › application-management › msi-installation-error-1603
MSI installation error 1603 - Windows Server | Microsoft Learn
Error 1603: A fatal error occurred during installation.
Problem: MSI installer Error - MSI installer failed with exit code: 1603
Running installer : SetupChipset.msi ERROR : MSI installer failed with exit code : 1603 ERROR : MSI installation failed with exit code : 1603 Failed to install INF files More on github.com
11
February 18, 2026SCSM Install - 1603 Error
error i'm getting is 1603, i dont see much about this. error in scsminstall.log: MSI (s) (78:9C) [15:00:55:661]: Note: 1: 1708 MSI (s) (78:9C) [15:00:55:661]: Product: Microsoft System... More on forums.prajwaldesai.com
4
0
January 5, 2024Windows Installer error 1603
I'm getting the following error: failed to load dll: IS32Util, Object reference not set, fatal error 1603 consult Windows Installer Help (msi.chm) or MSDN I am running windows xp home, I have no trouble with other systems installing the SAME file (a different home xp system), I've cleaned out ... More on experts-exchange.com
MSI Error 1603 - Uninstalling Exchange 2010
Having a bit of trouble uninstalling it and only getting the generic 1603 error. I have the exchange 2010 msi install available and have tried running it from the CLI and GUI in Add/Remove programs. Permissions are correct for the AD account I am using and looking at the ... More on community.spiceworks.com
7
3
October 9, 2023What is MSI Error 1603, and what causes it?
MSI Error 1603 is a generic Windows Installer error indicating a fatal error occurred during installation. This error can be triggered by various issues, including: · Attempting to install a program over an existing version without proper removal. · Insufficient permissions to access certain files or folders. · The installation path is encrypted or inaccessible. · Conflicts with running background applications. · Custom actions in the installer failing due to incorrect sequencing or conditions. · Identifying the specific cause requires examining the installation logs and system configuration.
advancedinstaller.com
advancedinstaller.com › msi-error-1603-fatal-error-during-installation.html
How to Troubleshoot MSI Error 1603: Fatal Error During Installation
How can I troubleshoot and resolve MSI Error 1603?
To address MSI Error 1603, consider the following steps, which can help resolve the error and allow the installation to proceed successfully: · Review Installation Logs: Search for "Return value 3" in the MSI log files to pinpoint the action that failed. · Check Custom Actions: Ensure that any custom actions in the installer are correctly sequenced and have the necessary conditions met. · Verify Permissions: Confirm that the user has sufficient permissions to install the application and access required directories. · Close Background Applications: Terminate unnecessary background processes tha
advancedinstaller.com
advancedinstaller.com › msi-error-1603-fatal-error-during-installation.html
How to Troubleshoot MSI Error 1603: Fatal Error During Installation
How can I identify the specific cause of Error 1603 in the installation logs?
To pinpoint the exact cause of Error 1603, use this approach to help you diagnose the issue by revealing the exact step where the installation encountered a problem: · Enable Verbose Logging: Run the installer with verbose logging enabled to capture detailed information. · Search for "Return value 3": In the generated log file, search for the phrase "Return value 3" to locate the point of failure. · Examine Preceding Lines: Review the lines above "Return value 3" to identify the custom action or process that failed. · Analyze Error Messages: Look for specific error messages or codes that provi
advancedinstaller.com
advancedinstaller.com › msi-error-1603-fatal-error-during-installation.html
How to Troubleshoot MSI Error 1603: Fatal Error During Installation
Videos
Top answer 1 of 2
6
Reboot Required?: could this be a simple "reboot required issue". 1603 can mean "reboot required" in batch files.
- Did you run the batch file with admin rights?
- Does this MSI have any custom actions? If so, where are they located in the
InstallExecuteSequence? - There are other possibilities (resurrected from WayBack Machine). Inlining the main section here for the future:
From link above: The following is a non-exhaustive list of known causes for this error:
- Short file name creation is disabled on the target machine.
- An Install Script custom action is prototyped incorrectly.
- A file is locked and cannot be overwritten.
- The Microsoft Windows Installer Service is not installed correctly.
- The Windows Temp folders are full.
- The setup was corrupted after installation and, therefore, fails with this error during un-installation.
- An older version of Install Shield Developer is being used.
- A general error occurred during the installation.
- Print and File sharing is not installed or enabled when installing MSDE 2000.
Proposed solutions in linked document above:
1)Make sure short file name creation is enabled on the target machine,2)Make sure Windows Installer is properly installed,3)Empty all temporary folders,4)Close all running applications and utilities, and launch the installation again - especially antivirus tools, and5)a couple more options.
You need to gather more information - which leads to checking for logs:
Standard debugging:
Event Logs: What does the
event logssay? (Windows + Tap R. typeeventvwrand press OK). Check the different logs.MSI Log File: Did you create an MSI log file?
There could be policies in effect to automatically create one. Check in the
TMP folder, sort by date and check recent files for any*.log files.Also check in the batch file if it hard codes a location for the MSI log file.
If you find an MSI log file, try searching for "value 3" (without the quotes) to find any actions that failed.
- Windows Installer Error Messages.
- MsiExec.exe and InstMsi.exe Error Messages.
How to create an MSI log file:
- How to create an MSI log - short version
- Long answer with MSI logging tips
2 of 2
0
While installing on windows sometimes get 1603 error because Visual C++ RunTime Library and Microsoft .Net problems.
Try reinstall Microsoft Visual studio redistributable package or uninstall original installed versions.
Advanced Installer
advancedinstaller.com › msi-error-1603-fatal-error-during-installation.html
How to Troubleshoot MSI Error 1603: Fatal Error During Installation
The Microsoft Windows Installer (MSI) generates error code 1603 when it has trouble installing a software package due to an issue with either the Windows Installer or the software package.
GitHub
github.com › FirstEverTech › Universal-Intel-Chipset-Updater › issues › 14
Problem: MSI installer Error - MSI installer failed with exit code: 1603 · Issue #14 · FirstEverTech/Universal-Intel-Chipset-Updater
February 18, 2026 - Running installer : SetupChipset.msi ERROR : MSI installer failed with exit code : 1603 ERROR : MSI installation failed with exit code : 1603 Failed to install INF files
Author FirstEverTech
Prajwal Desai
forums.prajwaldesai.com › home › microsoft cloud › sccm
SOLVED - SCSM Install - 1603 Error | Forums on Intune, SCCM, and Windows 11
January 5, 2024 - Counter after decrement: -1 MSI ... servers. got other issues now, but this is done! ... 1603 error appears when antivirus software blocks the installer....
Apptimized
apptimized.com › home › blog › packaging pitfalls part 1: how to fix msi error 1603 – fatal error during installation
1603 MSI Error – How To Fix Fatal Error During Installation
May 30, 2025 - Check the vendor documentation for required runtimes or dependencies. Missing frameworks, runtimes, or OS requirements are common root causes of a 1603 MSI failure.
Experts Exchange
experts-exchange.com › questions › 20538606 › Windows-Installer-error-1603.html
Solved: Windows Installer error 1603 | Experts Exchange
March 5, 2003 - They involve the source DCOM as well as Service Control Manager. The user is listed as one of three.. Admin, System or N/A. (there's about 10 errors). In the event viewer for applications, there are 2 warnings : Userenv (user system) and MSI Installer, the user being N/A.
PDQ Help Center
help.pdq.com › hc › en-us › articles › 220531027-MSI-Fatal-Error-Error-1603
MSI Fatal Error - Error 1603 – PDQ Deploy & Inventory Help Center
December 8, 2022 - Error 1603 is a catch-all error used by Microsoft Installer when an unexpected failure is encountered during an installation. Quite often this occurs when a file that is needed for an installation is not found (perhaps it was deleted by an antivirus ...
Red-Gate
productsupport.red-gate.com › hc › en-us › articles › 360019619137-MSI-returned-failure-code-1603-Fatal-error-during-installation
MSI returned failure code 1603: Fatal error during installation – Support
"MSI returned failure code 1603: fatal error during installation. The installer has encountered an unexpected error installing this package. This may indicate a problem with this package.
Splunk Community
community.splunk.com › t5 › Installation › How-do-I-fix-this-automatic-installation-fails-with-1603-error › m-p › 629370
How do I fix this automatic installation fails with 1603 error?
August 15, 2024 - Installation by domain admin with current UF fails on the domain controller with error 1603 and there are additional loglines that may be usefull: MSI (s) (F0:34) [08:38:07:344]: Note: 1: 1708 MSI (s) (F0:34) [08:38:07:344]: Note: 1: 2205 2: 3: Error MSI (s) (F0:34) [08:38:07:344]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708 MSI (s) (F0:34) [08:38:07:344]: Note: 1: 2205 2: 3: Error MSI (s) (F0:34) [08:38:07:344]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (s) (F0:34) [08:38:07:344]: Product: UniversalForwarder -- Installation failed.
Spiceworks
community.spiceworks.com › software & applications
MSI Error 1603 - Uninstalling Exchange 2010 - Software & Applications - Spiceworks Community
October 9, 2023 - Having a bit of trouble uninstalling it and only getting the generic 1603 error. I have the exchange 2010 msi install available and have tried running it from the CLI and GUI in Add/Remove programs. Permissions are correct for the AD account I am using and looking at the ...
Intuit
accountants.intuit.com › support › en-us › help-article › install-products › resolving-windows-installer-error-code-1603 › L6bT3EXeS_US_en_US
Resolving Windows Installer Error code: 1603
March 30, 2026 - Part 4 - Software Restriction Policy. X:\programpath.msi is not digitally signed. This error occurs when the MSI isn't signed, and you're using policies that are preventing it from running.
BigFix
forum.bigfix.com › content authoring
MSI execution error 1603 - Content Authoring - BigFix Forum
July 7, 2021 - Msi is working fine silently with /qn swithch. While deploying through Bigfix action completed with exit code 1603 and software not installed. tried to execute this batch file as well but no luck. wait cmd.exe /c “cd …
YouTube
youtube.com › watch
How To Fix Error 1603 Fatal Error During Installation in Windows 10 Step By Step Full Guide - YouTube
Learn how to fix the 1603 Fatal Error during software installation on Windows 10. Follow these steps to successfully install programs without interruptions.C...
Published December 20, 2025
PDQ
pdq.com › blog › windows-installer-error-1603-behind-the-rage
What is the Windows Installer Error 1603? | PDQ
February 1, 2021 - Microsoft has stated that there are three primary reasons for 1603: You are attempting to install to an encrypted drive or directory · You are attempting to install to a substituted drive · SYSTEM account does not have necessary permissions ...
Autodesk
autodesk.com › support › technical › article › caas › sfdcarticles › sfdcarticles › Error-1603-during-installation-of-Autodesk-software.html
"Install error 1603: Fatal error during installation" while installing Autodesk software with legacy installer
During the installation of an Autodesk product, the install wizard stops, and reports: Installation incomplete. Some products failed to install. Install error 1603: Fatal error during installation. Install error: The install couldn't Finish. Error 1603 The following are common examples of the 1603 error: Setup Logs: Install Failed Installation aborted, Result=1603.
PSAppDeployToolkit Community
discourse.psappdeploytoolkit.com › the toolkit › general discussion
v4.06-Errors while installing MSI - General Discussion - PSAppDeployToolkit Community
July 5, 2025 - Hi, I’m still pretty new to the App Deployment Toolkit. I’ve already packaged and deployed two apps using it through Intune, and those went smoothly. But of course, on the third try, I hit a wall. Here’s the deal: I’m using version 4.06 and trying to deploy an MSI installer.
Blue Prism Community
community.blueprism.com › t5 › Product-Forum › Blue-prism-HUB-Installation-Prod-1603-MSI-error › td-p › 125237
Blue prism HUB Installation Prod|1603 MSI error - SS&C Blue Prism Community
April 8, 2026 - We've seen in the past that '1603' errors can occur when installing Hub if the appropriate Domain is not specified within the config.json file. Please have a look at this Knowledge Base article, "Hub error "Installation success or error status: 1603" when attempting to install" for details.
Adobe
helpx.adobe.com › creative-suite › kb › error-1603-install-cs3-cs4.html
Error 1603: A fatal error occurred during Adobe Creative Suite installation
1 week ago - The 1603 error is an MSI error code indicating a failure that is generic, but computer-specific. This document lists possible suggestions to solve this error.