Another Installation Is In Progress

If another installation is in progress, close the stuck installer, reboot, and restart update services so Windows can install again.

This message usually shows up at the worst moment. You click Install, the progress bar sits there, and Windows blocks the next setup with a warning. The good news: most of the time it’s not broken software. It’s Windows doing what it’s built to do—one installer at a time.

This article walks you through practical fixes, starting with low-effort checks and ending with deeper repairs. You’ll know what to try, why it works, and what to avoid so you don’t trade one problem for another.

Why You See This Message

Windows Installer (MSI) and Windows Update both protect system files while they write changes. When one install session is active, the next one waits. If something gets stuck—an update that never finishes, a setup window you closed, a reboot that didn’t happen—you’ll keep seeing the same block.

There are three common patterns. A real install is still running in the background. A prior install finished, yet Windows is waiting for a restart to close the loop. Or a service such as Windows Installer or Windows Update is hung and holding a lock it won’t release.

It can feel like a dead end, yet the lock is a clue. It tells you the installer engine is busy, not that your app is bad. Your goal is to find the busy piece, let it finish if it’s working, or clear it if it’s frozen.

What You See	Likely Cause	First Move
Setup won’t start, same warning each time	MSI session stuck (often msiexec.exe)	End the installer process, then reboot
Windows Update says install in progress for hours	Update services hung	Restart services, then try update again
Apps install fine, only one app fails	That app’s updater still running	Close its updater, check Task Manager

What Counts As “Another Installation”

It’s not just the app you can see on screen. Background installers run when you update Office, drivers, game launchers, printers, security tools, and store apps. A scheduled task can fire an updater right when you start your own install, and Windows will treat it as the same queue.

When A Reboot Is The Missing Step

Some installers finish files, then schedule final changes for the next restart. If you postpone the restart, the installer can stay “active” in Windows’ eyes. That’s why the simplest fix—restarting—works so often. It clears pending operations, reloads services, and ends leftover installer handles.

Another Installation Is In Progress On Windows Update

If this warning shows during an update cycle, treat it like an update jam first, not a broken PC. Windows Update can sit in a waiting state when a prior update needs a restart, when the update database has a bad entry, or when the update services are stuck.

Before you touch commands or folders, check for two signals: pending restart prompts and active update tasks. Those two checks keep you from resetting things that are fine.

Check For A Pending Restart

Open Windows Update — Go to Settings, then Windows Update, and look for a Restart now button.
Restart The PC — Save your work, restart once, then return and try the update again.
Run One Update — Install one pending update first, then do the rest in batches.

Check For Active Installer Tasks

Open Task Manager — Press Ctrl + Shift + Esc, then pick More details if you see the small view.
Look For MSIEXEC — On Details, sort by Name and watch for msiexec.exe, setup.exe, or a vendor updater.
Wait A Few Minutes — If CPU or disk use is moving, let it finish. If it’s idle and stuck, move to the next section.

Seeing two msiexec.exe entries can be normal. Watch disk activity for a few minutes. If it’s idle and there’s no installer window, end the stuck task and reboot.

Fast Checks Before You Change Anything

Start with the steps that fix the most cases and carry the least risk. They’re boring, yet they save time. Do them in order and stop when the install works again.

Close Hidden Installer Windows

Check The Taskbar — Hover over app icons and close any installer window sitting behind other apps.
Check The Notification Area — Click the tray arrow and look for an updater icon that is mid-install.
Sign Out And Back In — If a window won’t close, sign out, sign back in, then try again.

Run The Installer As Admin

Close The Installer — Exit the setup you’re trying to run.
Run As Administrator — Right-click the setup file, then choose Run as administrator.
Note The New Message — If it still fails, the next error often points to what’s blocking it.

Try The Install With A Clean Boot

A clean boot starts Windows with a minimal set of startup apps. It helps when a third-party updater keeps re-launching and grabbing the installer lock.

Open System Configuration — Press Win + R, type msconfig, then press Enter.
Hide Microsoft Services — On Services, tick Hide all Microsoft services, then click Disable all.
Disable Startup Apps — Open Startup in Task Manager and disable nonessential entries.
Restart And Test — Reboot, run the install, then restore your startup items after.

Clear The Stuck Installer And Restart Services

If you still see the block, the next move is to clear the process or service that is holding the installer lock. This is still a safe set of fixes, as long as you don’t end random system processes you don’t recognize.

End The Windows Installer Process

Open Task Manager — Use Ctrl + Shift + Esc, then go to Details.
End MSIEXEC — Right-click msiexec.exe, choose End task, then close Task Manager.
Reboot Once — Restart to clear the installer session cleanly before you try again.

If you just killed an installer, give Windows a moment to settle. A stuck setup can leave temporary files behind, and a reboot is the cleanest way to close them. When you come back up, try the same installer once. If it fails again right away, switch to the service steps below instead of repeating the end-task loop.

Restart The Installer Service

Open Services — Press Win + R, type services.msc, then press Enter.
Restart Windows Installer — Find Windows Installer, then choose Restart if it’s available.
Start If Stopped — If it’s stopped, choose Start, then run your installer again.

Restart Update Services For Update-Related Blocks

If the warning is tied to Windows Update, restarting a small set of services often breaks the deadlock. You can do this from an admin Command Prompt.

Open Admin Command Prompt — Search cmd, right-click Command Prompt, then pick Run as administrator.
Stop Update Services — Run: net stop wuauserv, net stop bits, net stop cryptsvc, net stop msiserver.
Start Update Services — Run: net start msiserver, net start cryptsvc, net start bits, net start wuauserv.
Try The Update Again — Return to Settings and retry the update.

Repair Windows Update Components And System Files

When the lock keeps coming back, Windows Update can be stuck on corrupted cache files or a broken component store. The fixes here are more involved, yet they’re still standard repairs used by IT teams. Take your time and type commands carefully.

Reset The Update Cache Folders

This resets the download and catalog caches used by Windows Update. It does not delete your personal files.

Renaming the folders is a safe trick because Windows will build fresh copies on the next check. If you ever need to roll back, you can delete the new folders and rename the .old folders back to their original names after stopping the services again.

Stop Services — In an admin Command Prompt, run: net stop wuauserv, net stop bits, net stop cryptsvc, net stop msiserver.
Rename Cache Folders — Run: ren %systemroot%\SoftwareDistribution SoftwareDistribution.old and ren %systemroot%\System32\catroot2 catroot2.old.
Start Services — Run: net start msiserver, net start cryptsvc, net start bits, net start wuauserv.
Restart And Update — Reboot, then check for updates again.

Run DISM And System File Checker

If Windows’ component store is damaged, installs can pile up and never finish. DISM can repair the store, and System File Checker can repair system files that depend on it.

Run DISM — In an admin Command Prompt, run: DISM /Online /Cleanup-Image /RestoreHealth.
Run SFC — After DISM finishes, run: sfc /scannow.
Reboot After Repairs — Restart once the scans finish, then retry your install.

Use Windows Update Troubleshooter

Open Troubleshoot — Go to Settings, then System, then Troubleshoot, then Other troubleshooters.
Run Windows Update — Run the Windows Update troubleshooter and apply the fixes it suggests.
Retry The Update — Check for updates again after the tool finishes.

Prevent It From Coming Back

Once your install works, take a minute to keep the same block from returning. Most repeat cases come from updates piling up, reboots being postponed, or too many installers launching at startup.

Keep Installs From Colliding

Install One Thing At A Time — Let a setup finish fully before starting the next one.
Reboot After Big Installs — Drivers, Office, and feature updates often need a restart to release locks.
Pause Auto Updaters — Close game launchers and vendor updaters before you install other apps.

Watch For The Same Symptom

If you ever see the warning again, you can run this short checklist. It’s the same flow you used above, condensed into a single pass.

Restart Once — A reboot clears most stale installer locks.
Check Task Manager — End only the stuck installer process you recognize, then reboot.
Restart Services — Restart Windows Installer, or restart update services if the issue is update-related.
Reset Update Cache — Rename SoftwareDistribution and catroot2 if Windows Update is the trigger.
Repair System Files — Run DISM and SFC when the block keeps returning.

When To Pause And Get A Second Set Of Eyes

If the same machine throws the warning after every reboot, and DISM/SFC keep finding damage, you may be dealing with a failing drive, aggressive security software, or a damaged Windows image. At that point, prioritize backups and a proper repair install, since repeated forced installs can leave you with half-applied updates.

If you’re stuck with the message another installation is in progress after trying the steps above, circle back to the service restart and cache reset sections and run them slowly. A rushed command or a missed reboot is the usual reason it doesn’t clear.

Once it’s gone, run your installer again and let it finish all the way. If you keep your installs spaced out and reboot when Windows asks, you’ll almost never see it again.