1628 Failed To Complete Installation | Fix It Fast

If you’re staring at the message “Error 1628,” you’re not alone. It pops up during installs, repairs, and uninstalls, and it feels unfair because the app never even gets a chance to run.

This error is tied to the installer layer on Windows, not one single app. The good news is that most fixes are quick, and you can work from the safest moves to the deeper ones without risking your system.

What 1628 Failed To Complete Installation Means

In plain terms, the setup program started, tried to run its scripted steps, then stopped before it could finish. You’ll see this with installers built on InstallShield, plus some older game installers and business apps.

A lot of these setups use a helper process named iDriver.exe to run the script. If that helper is stuck, blocked, or running from a broken cache, the installer can exit with 1628. Revenera, the company behind InstallShield, calls out stuck iDriver processes as a common trigger.

On some PCs the Windows Installer service (the MSI engine) is the piece that’s out of shape. Microsoft notes that this error can show up when the installer service isn’t configured right or when the package expects a newer installer service than the PC has.

When This Error Shows Up

• During a fresh install — You double-click setup, it starts, then stops with the 1628 message.
• During an uninstall — You try to remove an app and the uninstaller quits before it finishes.
• During a repair or update — A patch runs, then bails out with the same code.

Fast Fixes That Work On A Lot Of PCs

Start here. These steps don’t change drivers, don’t touch the registry, and don’t remove system files. They just clear roadblocks that keep InstallShield and Windows Installer from doing their job.

1. Restart Windows — A full reboot clears hung installer tasks and releases locked files.
2. Run the setup as admin — Right-click the installer, pick Run as administrator, then try again.
3. End stuck installer tasks — Open Task Manager, end iDriver.exe and ISSetup.exe if you see them, then relaunch the installer.
4. Move the installer to a simple folder — Put it in C:\Install or your Desktop so it isn’t running from a long path or a network share.
5. Temporarily pause real-time antivirus scanning — Turn it off only for the install attempt, then turn it back on right after.

Quick Checks That Save You From A Redo

A failed setup can leave half-written files behind. Before you rerun the installer five times, take thirty seconds to check these basics.

• Free up disk space — Leave a few gigabytes open on the system drive so the installer can unpack files and write logs.
• Close overlay apps — Screen recorders, game overlays, and RGB tools can hook installers and cause odd exits.
• Disconnect extra drives — Unplug unused USB storage to rule out drive letter mix-ups in older setups.
• Check the file’s source — If it came from email or a browser, right-click the file, open Properties, then click Unblock if you see it.

Try A Clean Boot When Something Keeps Interfering

If the same installer fails at the same point and antivirus pausing doesn’t help, a clean boot can show whether a background service is getting in the way.

1. Open System Configuration — Press Win + R, type msconfig, then press Enter.
2. Hide Microsoft services — On the Services tab, tick Hide all Microsoft services, then click Disable all.
3. Disable startup apps — Open Task Manager from the Startup tab, then disable non-Microsoft startup items.
4. Restart and install — Reboot, run the installer, then restore your normal startup settings after.

If the install works after step three, you’ve confirmed it was a stuck InstallShield run. If it still fails, keep going. The next section targets the cache and temp folders that installers lean on.

Clear Temp Folders And Reset The InstallShield Cache

Installers write a lot of scratch files. When those folders get messy, you can end up with a half-built installer cache that keeps failing in the same spot.

Clean The Two Temp Locations

1. Empty your user temp folder — Press Win + R, type %temp%, then delete what you can. Skip files that say they’re in use.
2. Empty the Windows temp folder — Press Win + R, type C:\Windows\Temp, then delete what you can. Skip anything locked.
3. Try the install again — Relaunch the installer right after the cleanup so Windows isn’t filling the folders back up.

Reset The InstallShield Engine Folder

If the setup is InstallShield-based, resetting its shared engine folder can break a bad loop. Some vendors document a rename of the common InstallShield folder as a fix, then letting the installer rebuild it on the next run.

• Close all installers — Make sure no setup windows are open.
• Rename the InstallShield folder — In File Explorer, go to C:\Program Files\Common Files\ and rename InstallShield to InstallShield.old if it exists.
• Retry the installer — Run setup again so it can recreate what it needs.

If you’re working with a game installer from a disc, copy the entire disc to a folder on your drive and run setup from there. That can prevent read errors.

If you can’t find that folder, that’s fine. Some systems don’t have it until the first InstallShield app runs.

Repair Windows Installer And Related Services

When the error keeps coming back across multiple apps, the Windows Installer service may be the piece to fix. You can reset it without reinstalling Windows.

Re-register The MSI Engine

Microsoft’s own guidance and many vendor KBs use the same two commands: unregister, then register again. You’ll see no message when it works, so don’t panic if the screen stays quiet.

1. Open an elevated Command Prompt — Search for cmd, right-click Command Prompt, then pick Run as administrator.
2. Unregister Windows Installer — Run the first command below.
3. Register Windows Installer — Run the second command below.

msiexec /unregister
msiexec /regserver

Check The Windows Installer Service State

1. Open Services — Press Win + R, type services.msc, then press Enter.
2. Find Windows Installer — Scroll to Windows Installer in the list.
3. Set Startup type to Manual — Open Properties, set Startup type to Manual, then apply.
4. Start the service — Click Start in the same window, then retry your installer.

Create A Log So You Can See The Failing Step

When you’re dealing with an MSI installer, a log turns guesswork into clues. You’ll see the exact action that failed, plus the error right before it.

1. Copy the MSI to a folder — Put the .msi file in a simple path like C:\Install.
2. Run an install with logging — Use the command below and swap in your MSI name.
3. Open the log — Look near the end for the first line that mentions “Return value 3.”

msiexec /i "YourInstaller.msi" /L*v "C:\Install\install-log.txt"

If your setup is a .exe wrapper, many vendors still let you pass logging switches, but they vary by product. In that case, check the vendor’s install notes or look for a log file created in %temp% during the failed run.

If your installer is old, Windows compatibility settings can also help. Right-click the setup file, open Properties, then try Compatibility mode for an older Windows version.

Fix 1628 During Uninstall Or Repair

Uninstalls and repairs can fail with 1628 when the original installer files are missing, the cached package is damaged, or the uninstall entry points to a file that no longer exists.

Try Microsoft’s Install And Uninstall Troubleshooter

Microsoft provides a tool called the Program Install and Uninstall troubleshooter. It targets broken uninstall entries and damaged registry keys that stop installs or removals. You can grab it from Microsoft’s site and run it as a normal app.

• Download the troubleshooter — Get it from Microsoft’s site.
• Pick Install or Uninstall — Choose the option that matches what you’re doing.
• Select the problem app — If it shows in the list, pick it; if not, use the Not Listed path if offered.
• Apply the fixes — Let it repair the entry, then retry your uninstall or install.

Search for the Program Install and Uninstall troubleshooter on Microsoft’s site, then run it from your Downloads folder.

Use Safe Mode For Stubborn Removals

If background apps keep grabbing the files you’re trying to remove, Safe Mode can cut the noise. It loads fewer startup items, which can prevent file locks during an uninstall.

1. Boot into Safe Mode — Open Settings, go to System, choose Recovery, then use startup options.
2. Run the uninstaller — Use Programs and Features or the app’s uninstaller in Safe Mode.
3. Reboot normally — Restart back into normal Windows after the removal.

Use A Simple Triage Table Before You Spend An Hour

This quick table helps you match what you’re seeing to the best first move.

Prevent The Error From Coming Back

Once you’ve cleared 1628, a few habits keep installs calmer the next time you add or remove software.

• Keep Windows updated — Updates include installer fixes and security patches that reduce install failures.
• Install from local storage — Copy setup files to your PC before running them.
• Use short folder paths — Simple locations reduce path and permission glitches.
• Clean temp folders now and then — Disk Cleanup or manual deletes keep installer scratch space sane.
• Avoid running two setups at once — Let one installer finish before you start another.

If you still see 1628 failed to complete installation after every step above, the installer itself may be broken. Try a fresh download from the vendor, and if you have a log file, share it with the vendor’s help desk so they can spot the failing step.

One last check: if the installer is coming from an old CD or DVD, copy the whole disc to a folder on your drive first. Scratches and slow reads can make script-based installers quit early with vague codes.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback