Setup.exe Fails With Error 1603 Midway: Printer and GPU Driver Fixes I Use First

Error 1603 hits you at the worst possible moment. The progress bar has been sitting at 40 or 60 percent for a few minutes, then the installer rolls back, throws a dialog with a bare number, and leaves you with either a half-installed driver or nothing at all. Both printer installers and GPU driver packages do this, and the causes overlap more than you’d expect. These are the fixes I try first, in the order I try them.

What 1603 actually tells you

1603 is a Windows Installer error code. It means a fatal error occurred during installation. That’s it. Microsoft never built a more specific meaning into it, so the installer is telling you “something broke” and nothing else. The useful part is context: what was on screen when it died, and what driver stack you’re replacing.

Before you touch anything, open Event Viewer. Go to Windows Logs, then Application. Look for the red error entries timestamped at the moment the install failed. The installer’s own log is more useful still. Printer packages from HP, Brother, and Epson write logs to the Temp folder, and NVIDIA‘s package drops logs under ProgramData. Read the last twenty lines before the rollback. Nine times out of ten the actual failure, a locked file, a missing service, a permissions error, is named right there. Error 1603 is just the wrapper.

If you skip this step, you’ll spend an hour reinstalling things that were never broken.

Fix one: kill everything holding the old driver open

This is the most common cause I run into, and it applies to both printers and GPUs. The new installer needs to remove or replace files that are currently in use, and Windows won’t let it. The installer doesn’t warn you. It just fails.

For GPUs, overlays and monitoring tools are the usual suspects. MSI Afterburner, RivaTuner, EVGA Precision, NZXT CAM, ASUS Armoury Crate, and Discord’s or Steam’s in-game overlays all hook into the graphics driver and keep handles open. Close them, then check your startup entries and disable them for the next boot too. Some of them leave scheduled tasks behind that fire mid-install, which is worse than leaving them running.

For printers, close the spooler-dependent apps. Print and scan utilities, the manufacturer’s status monitor, anything sitting in the system tray with the printer’s name on it. If the old driver won’t release, stop the Print Spooler service, set its startup type to Manual temporarily, and run the installer again. You can put it back to Automatic afterward.

Fix two: remove the old driver properly, not just “uninstall” from Settings

A normal uninstall leaves pieces behind. That’s true of printer drivers and it’s definitely true of GPU drivers. When the installer finds remnants it doesn’t recognize, the rollback begins.

For a GPU, this is the case where I reach for Display Driver Uninstaller. It was built for exactly this situation: wiping the driver stack when a normal uninstall won’t cooperate. Wagnardsoft’s own guidance is to run it from Safe Mode where possible, though Normal mode works if you clean, reboot, clean again, and reboot once more. Either way, download the new driver before you go offline, disconnect from the network so Windows Update can’t sneak its own version in mid-process, and run the tool for your vendor, NVIDIA, AMD, or Intel. Screens go low-res during the process. That’s normal. Then install the fresh package and reconnect.

For printers, the equivalent is the Print Server Properties route. Open Control Panel, go to Devices and Printers, then Print Server Properties, and delete the old driver from the Drivers tab along with the printer itself. Then reinstall. If the driver is stubborn because a port is still bound to it, delete the port after removing the printer and reboot before trying again.

Fix three: the installer needs an administrator session, not just an admin account

Error 1603 lands on people who double-click the setup file from a standard user session and rely on the UAC prompt to elevate. Some driver installers half-elevate and then can’t write to the folder they created. The fix is unglamorous: right-click the installer and pick Run as administrator. If that still fails, copy the whole installer folder to a local drive first, such as C:Temp. Guru3D’s notes on DDU make the same point for that tool. Running anything from a network share or a USB drive adds permission issues on top of the usual ones.

Check the Temp folder and WindowsTemp permissions too. A locked-down Temp folder is rare but it happens after some cleanup utilities run.

Fix four: clear the installer’s own leftovers

When an install fails midway, the Windows Installer cache can be left in a state where every subsequent attempt fails at the same point. The symptom is telling: same error, same percentage, every time, even after a reboot.

Two things to try. First, run the Windows Installer troubleshooter from Settings, System, Troubleshoot. It rewrites the installer state without you intervening. Second, if you have the installer’s .msi copy, open a command prompt as administrator and try the package in repair mode. If the installer is an .exe wrapper, look for a disable-cleanup command-line switch, but this varies by vendor and I won’t invent one for you here. Read the installer’s help output rather than guessing.

On really stubborn cases, create a new local administrator account and run the installer from that session. If it works there, the original profile’s permissions are the problem and you’ve narrowed the hunt considerably.

Fix five: deal with the antivirus before the installer runs

Security software intercepting the driver files is a quiet killer. Some tools quarantine a freshly extracted driver binary, then let the install continue until the missing file causes the rollback. Exclude the installer’s extraction folder and DDU’s folder from real-time scanning before you start. Defender’s exclusion list is under Windows Security, Virus and threat protection, Manage settings. Third-party suites have their own exclusion dialogs, and some of them require you to rebuild the list rather than add to it. Then re-run the installer.

If the driver installed correctly but the device still won’t start, and Device Manager shows a yellow mark with the message that the device isn’t working properly, that’s a different problem, a driver or hardware fault that needs the device’s driver uninstalled and rescanned rather than reinstalled wholesale. Right-click the device, Uninstall, then right-click your PC name and choose Scan for hardware changes. Once the status reads “This device is working properly,” the install side is done and you’re looking elsewhere.

What I check last, and what it usually means

If all five fixes fail, the installer isn’t the problem. Your Windows install has a servicing issue, likely from a failed cumulative update or a corrupted component store. Running the deployment image servicing and repair tool over the Windows image and then the system file checker is worth twenty minutes. It has fixed exactly this kind of recurring 1603 on two machines I’ve worked on. It has also done nothing on plenty of others, so treat it as a coin flip rather than a cure.

When even that comes up empty, a clean Windows install is the honest next move. Before you go there, though, confirm the installer actually matches your Windows version and architecture. A 32-bit package on 64-bit Windows, or an installer built for a Windows version you’ve since moved off, can produce 1603 at the same point every time. That’s not a bug. It’s a mismatch.

The pattern across all of this is the same. A 1603 is almost never a mysterious Windows Installer defect. Something is in the way, or something old is still holding on. Find out which, and the number stops being scary.