How to fix "Error 1628: Failed to complete installation" error in Windows?

Error 1628 comes from programs whose setup is built with InstallShield, not from Windows itself. It usually appears when you uninstall, repair or update a program, because the setup engine cannot run its script. End the leftover installer process in Task Manager first, then try again.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What "Error 1628: Failed to complete installation" means

Many desktop programs are installed and removed by an InstallShield setup engine. When you uninstall such a program, Windows starts that engine, and it runs a script that reads the program's own uninstall log. The InstallShield maker says error 1628 appears at run time, normally during uninstallation, repair, or when applying a patch.

That is why the box says "installation" even though you asked to remove the program. The same engine does both jobs, and the message names the engine's task, not yours. A typical box has the program's name and "InstallShield Wizard" in the title bar and reads: 1628: Failed to complete installation.

• 1628: Failed to complete installation. The usual wording on Windows 11 and Windows 10.
• Error 1628: Failed to complete script based install. The older wording that the InstallShield maker's own articles quote.
• 1628: Failed to complete scripted install. Another variant one software maker's support page reports for its own product.

Why the 1628 error failed to complete installation

Most often an earlier run of the setup engine did not close, so IDriver.exe or ISSetup.exe still runs, and the uninstall log can be damaged. Less often a leftover file in the TEMP folder clashes with the files the setup unpacks. Rarely the Windows Installer service or old registry data blocks the script.

How to fix error 1628 failed to complete installation

Fixes 1 to 3 follow the InstallShield maker's own resolution and solve most cases. Fix 4 rebuilds the program's setup data. Fixes 5 to 7 are for the cases that remain. Try the uninstall, repair or update again after each fix.

Fix 1. End IDriver.exe or ISSetup.exe in Task Manager

3 minutesNo riskEveryone, first. Especially if an earlier setup or uninstall froze, crashed or was cancelled.

The InstallShield maker says error 1628 is often caused by IDriver.exe, called ISSetup.exe in InstallShield 12 and later, not closing at the end of a previous run. The stuck engine keeps the uninstall log busy, so the new run cannot read it.

1. Close the error box and every setup or uninstall window.
2. Press Ctrl + Shift + Esc to open Task Manager. Select More details if you see only a short list.
3. Open the Details page and sort by Name.
4. Look for IDriver.exe or ISSetup.exe. Select each one you find and select End task.
5. Open Start > Settings > Apps > Installed apps, select the three dots next to the program and select Uninstall again.

If neither name is in the list, restart the PC once, which closes every leftover process, and try the uninstall again before you go on.

Fix 2. Move the program's damaged uninstall log out of the way

10 minutesLow riskThe error comes back every time you uninstall one program, even after Fix 1 and a restart.

The InstallShield maker's resolution for a corrupted uninstall log is to end the engine and delete the .ilg file from the program's folder under InstallShield Installation Information. We move it instead, so you can put it back if the program's maker asks for it.

1. Do Fix 1 first, so no IDriver.exe or ISSetup.exe is running.
2. Press Win + E to open File Explorer.
3. On Windows 11 select View > Show > Hidden items. On Windows 10 open the View tab and tick Hidden items.
4. Open the folder below. For a 64 bit program, look in the same folder under C:\Program Files instead.
5. Each subfolder is named after a program's product code in braces. Open the one whose Date modified matches the day you installed the program.
6. Find the file that ends in .ilg, cut it with Ctrl + X and paste it on your desktop.
7. Try the uninstall again.

Where InstallShield keeps uninstall logs of 32 bit programs

C:\Program Files (x86)\InstallShield Installation Information

If several folders share the same date, open each one. Many contain a setup file or setup.ini with the program's name inside. Leave the folders of other programs alone, because their uninstallers need them.

Fix 3. Empty the TEMP folder and run the setup again

5 minutesLow riskMore than one InstallShield program fails, or Fix 1 and Fix 2 did not help.

The InstallShield maker lists a file in the TEMP folder that conflicts with the files the setup extracts or uses as a cause of error 1628. Its fix is to delete the contents of that folder and run the setup again.

1. Close every open program, so none of them is using a temporary file.
2. Press Win + R, type %temp% and press Enter.
3. Press Ctrl + A to select everything in the folder, then press Delete.
4. If Windows says a file is in use, tick Do this for all current items and select Skip.
5. Restart the PC and try the uninstall, repair or update again.

Files that are in use stay behind, and that is fine. To clear more temporary files with Settings instead: Free up disk space and delete temporary files

Fix 4. Repair the program, or reinstall the same version over it

15 minutesLow riskThe error appears when you install a patch or update, or Fix 2 left the uninstaller without a log.

The InstallShield maker says a patch fails with 1628 when the base installation is not on the PC, and that the error is often caused by the installation itself. Repairing or reinstalling writes a fresh uninstall log, which the next uninstall can read.

1. Open Start > Settings > Apps > Installed apps and find the program.
2. Select the three dots next to it. If Modify or Advanced options is there, open it and choose Repair.
3. If there is no repair option, download the same version of the program from its maker's own site.
4. Run that setup and install the program over the existing copy, in the same folder.
5. Restart the PC, then uninstall the program again or install the update you wanted.

Repair and reset in Settings, with screenshots: How to repair or reset an app in Windows. Not every desktop program offers repair. Microsoft notes the same in its own help page on blocked installs.

Fix 5. Run Microsoft's Program Install and Uninstall troubleshooter

10 minutesLow riskYou only want the program gone, and the program's own uninstaller keeps failing.

Microsoft says this troubleshooter fixes corrupt registry keys and problems that block a program from being completely uninstalled. It can remove the program's Windows Installer records without running the broken InstallShield script.

1. Open Microsoft's support page Fix problems that block programs from being installed or removed and switch to its Windows 10 tab.
2. Select Download troubleshooter and open the downloaded MicrosoftProgram_Install_and_Uninstall.meta.diagcab file.
3. Select Next, then Uninstalling.
4. Pick the program from the list and select Next.
5. Follow the prompts to remove the program and wait for the tool to finish.

Fix 6. Restart the Windows Installer service

5 minutesNo riskPrograms from different makers fail to install or uninstall, not only one.

The InstallShield maker says error 1628 can occur when the Windows Installer service is not properly configured. InstallScript MSI setups hand part of their work to that service, so a hung service stops them.

1. Open Services. Press Windows+R, type the command below and press Enter. You can also type Services in the search box on the taskbar and open the app.

   services.msc

2. Find the service. The list is sorted by Name. Click any row and type the first letter of the service to jump to it. Check the Status column (Running or empty) and the Startup Type column.

   

3. Restart the service. Right-click the service and select Restart. If the service is not running, select Start instead. Wait until the progress window closes.

   

These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Check and restart Windows services

In the list, the service is called Windows Installer. Its normal startup type is Manual: Windows starts it when a setup needs it. Leave it on Manual; there is no need to set it to Automatic.

Fix 7. Remove the program's leftover InstallShield registry key

15 minutesRead the warningAdvanced users only, after Fixes 1 to 6, when the program's uninstall log was deleted and the program cannot be reinstalled.

The InstallShield maker says error 1628 can be caused by the uninstall log being deleted from the system, and that a setup log then shows "Failed to open cab". Its fix is to delete the program's InstallShield uninstall key in the registry.

1. Press Win + R, type regedit and press Enter. Select Yes in the permission prompt.
2. Go to the key below. For a 32 bit program on 64 bit Windows, look also under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall.
3. Select each subkey whose name starts with InstallShield_ and read DisplayName on the right until you find the failing program.
4. Right-click that key, select Export and save the .reg file on your desktop.
5. Right-click the key again, select Delete and confirm.
6. Restart the PC and install the program again from its maker, or check that it is gone from Installed apps.

Where Windows lists uninstall entries

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

The InstallShield maker gives the key as InstallShield_UninstallInformation followed by the product GUID. The exact name can differ, so match the key by DisplayName, not by its spelling.

If error 1628 is still there: what to check and send

The InstallShield maker says that if its fixes fail, you need to contact the vendor of the program. Only that vendor knows how its setup was built, and some causes of 1628 are mistakes in the setup itself.

• Event Viewer. Press Win + R, type eventvwr.msc, open Windows Logs > Application and look for MsiInstaller or Error entries at the time of the failure.
• A screenshot of the error box, including its title bar, which names the program.
• The program's name and version from Installed apps, and whether you were uninstalling, repairing or updating.
• Your Windows version from winver, and whether a Windows update was installed just before the error started.
• Send it to the program's maker, not to Microsoft or to InstallShield.

Error 1628 is not a sign of failing hardware. If File Explorer also reports read errors or the PC freezes when it copies files, check the drive separately with Check a disk for errors (chkdsk) and back up your files first.

How to avoid error 1628 next time

Frequently asked questions

What is error 1628?

Error 1628 is an InstallShield run time error. InstallShield is the setup builder that many programs use to install and uninstall themselves. The box reads "1628: Failed to complete installation" or, in older setups, "Failed to complete script based install". The InstallShield maker says it normally occurs during uninstallation, repair or when applying a patch. Its most common causes are a leftover IDriver.exe or ISSetup.exe process and a damaged uninstall log, which Fix 1 and Fix 2 deal with.

Why does it say "installation" when I am trying to uninstall?

Because the same InstallShield engine runs both jobs. When you select Uninstall, Windows starts the program's own setup engine, and it runs an install script in uninstall mode. If that script cannot finish, the engine reports that it failed to complete the installation, meaning its own task. Your program is usually still installed and working. End the leftover setup process (Fix 1) and try the uninstall again.

Can I get error 1628 on an app from Microsoft Store?

Not from the Store app itself. Store apps install and uninstall through Windows, not through InstallShield, and Microsoft points to a separate help page for Store app problems. Some games and programs, though, are listed in Installed apps and run their own InstallShield uninstaller, even if you found them through the Store. If the box says "InstallShield Wizard" in its title bar, the fixes on this page apply. If it does not, see Reset the Microsoft Store.

What does "failed to complete installation 1628" mean on a game or driver?

The same thing as on any other program. Games, drivers and licence tools often ship with InstallShield setups, so the error box shows the game's or driver's name in its title bar. The cause is in that one setup, not in the game itself. End IDriver.exe or ISSetup.exe in Task Manager (Fix 1), move the damaged uninstall log (Fix 2), then contact the game's or driver's maker if the error stays.

Is "1628 failed to complete installation" different on Windows 11?

No. The error comes from the program's InstallShield setup, so it looks and behaves the same on Windows 11 and Windows 10. Only some menus differ: on Windows 11 you uninstall from Settings > Apps > Installed apps and show hidden files with View > Show > Hidden items. Microsoft's Program Install and Uninstall troubleshooter is offered only on the Windows 10 tab of its support page, so on Windows 11 use repair, reset or uninstall in Settings first.

What does "1628 Skriptbasierte Installation konnte nicht abgeschlossen werden" mean on Windows 10?

It is the German wording of the same error: "failed to complete script based install". The fixes on this page apply on a German Windows 10 or Windows 11 as well. In Task Manager, look on the Details page (German: Details) for IDriver.exe or ISSetup.exe. Uninstall from Einstellungen > Apps. The InstallShield Installation Information folder keeps its English name on German Windows too.

Can a Windows update cause error 1628?

Sometimes. The InstallShield maker says changes from recent updates can make setups created before the update fail. It suggests uninstalling the recent update, running the setup, and installing the update again, but warns you to check with the vendor first. On Windows 11 and 10, skipping security updates is a risk, so try Fixes 1 to 6 first. If you do remove one, use How to uninstall a Windows update and install it again straight after.

Should I re-register Windows Installer with msiexec /unregister and /regserver?

We do not recommend it as a fix for 1628. It was in an older version of this guide, but neither the InstallShield maker nor Microsoft lists it for this error. The InstallShield maker says the Windows Installer service must be properly configured, and restarting the service (Fix 6) covers that safely. If programs from many makers fail to install, a system file check is the better next step: Run DISM and SFC to repair Windows system files.

Does Safe Mode help with error 1628?

It is not a fix the InstallShield maker or Microsoft gives for this error, so we removed it from this guide. Safe Mode starts Windows with a minimal set of drivers and services, and many setups need services that are not running there. Ending the leftover setup process (Fix 1) gives the same clean start for the uninstaller without leaving normal Windows.