Fix it now
Microsoft publishes this one plainly: the error usually occurs if another installation, update or uninstall was running before you tried to install Office. Sometimes that is still true and you simply need to wait; more often a previous run ended badly. Either way, start by finding out whether an install is genuinely in progress.
- Look for an Office icon in the Windows system tray and click it to check the install progress. That is Microsoft’s documented first step, and it answers the only question that matters here.
- If an install or update is genuinely running, wait for it to finish before starting yours. On a slow connection that can take a while, and interrupting it creates the stuck state you are trying to avoid.
- If nothing is running, restart the computer. That clears the claim without you having to end anything by hand.
- After the restart, run setup once, before opening any Office application.
- If it still refuses, remove Office with Microsoft’s uninstall troubleshooter, restart, and install again.
On a shared or Remote Desktop host, run quser from a Command Prompt to see whether somebody else is signed in and installing at the same time. Install with no users connected.
If setup gets past the point it previously refused, you can stop here. If the same message returns immediately, the next section covers what holds the claim and why.
Why it happens
Click-to-Run serialises its own work deliberately. Two installations, or an installation and an update, cannot safely write the same product at the same time, so the client takes an exclusive claim before it starts and releases it when it finishes. Microsoft’s published cause for this code says exactly that in plain language: it usually occurs if another installation, update, or uninstall was running before you tried to install Office.
The everyday version is far more innocent than the error implies. Office updates itself in the background, and if an update is in flight when somebody launches setup, the installer correctly declines. Updates take several minutes on a slow link and they do not announce themselves, which is why the error looks inexplicable on a machine where nothing appears to be happening. The system tray icon is the one place it does announce itself, which is why Microsoft’s first step is to look there.
The other version is a previous run that ended without releasing the claim – a forced restart, a crash, a session logged off mid-install. Then the machine is holding a lock for work that is no longer happening, and a restart is the documented and safe way to clear it. Stopping the Click-to-Run service or ending its processes is not in Microsoft’s guidance for this code, and it is capable of leaving a partially installed Office that neither runs nor repairs.
Two of the codes here need placing carefully. Microsoft publishes 0-1018, 17003-2031 and 2035-0 on one page, under the same cause. 0-3 has its own page with a different one: you might see this error if a previous installation of Microsoft 365 failed. And 0-2031 (17004) appears in Microsoft’s FSLogix article, on the dialog that follows 30010-45 or 30088-26 when a profile rule is hiding an Office executable – so if you have that combination, the answer is a rule change rather than a lock.
An Office update is genuinely running
You have this one if The system tray shows install progress, or Office applications are asking to be closed.
- Let it finish. Interrupting it is what produces the stuck state.
- Watch progress under File, Account, Update Options in any Office application that will open.
- Run your installation once the update has completed.
A previous run ended without releasing the claim
You have this one if Nothing is progressing anywhere, and a setup attempt was interrupted earlier.
- Restart the machine. This is the safe way to clear the claim and it works most of the time.
- Sign back in, wait a minute for logon tasks to settle, then run setup once.
- If it still refuses, remove Office with Microsoft’s uninstall troubleshooter, restart, and install again from a fresh download.
A previous installation failed and left the machine confused
You have this one if You have 0-3 rather than 0-1018, and an earlier Office install did not complete.
- Repair Office first: right-click Start, select Apps and Features, select the Office product, select Modify, then Online Repair and Repair.
- If repair does not help, use the uninstall troubleshooter and then reinstall.
- If the troubleshooter does not remove everything, follow Microsoft’s manual uninstall procedure before installing again.
Windows Installer or Windows Update has the machine
You have this one if Another installer window is open, or Windows Update installed something in the last few minutes.
- Close any other installer windows and let Windows Update finish its current cycle.
- Check Settings, then Windows Update, and confirm nothing is waiting on a restart.
- Restart if a restart is pending, then run Office setup before anything else starts.
Another session on a shared host is installing
You have this one if A Remote Desktop or multi-session host where quser shows other active sessions.
- Run
quserfrom a Command Prompt and see who else is signed in. - Coordinate so only one installation runs on the host at a time.
- Put the server into the appropriate maintenance state and install with no users connected. Installing Office under an active user session on a shared host invites exactly this error.
Full reference
What Microsoft publishes for each code
| Code | What Microsoft publishes |
|---|---|
0-1018 |
This error usually occurs if another installation, update, or uninstall was running before you tried to install Office |
17003-2031 |
Published on the same page as 0-1018, with the same cause |
2035-0 |
Published on the same page as 0-1018, with the same cause |
0-2031 |
Shown as 0-2031 (17004) on the dialog that follows 30010-45 or 30088-26, where FSLogix is hiding an Office executable. No general meaning is published |
0-3 |
When installing Microsoft 365, you might see this error if a previous installation of Microsoft 365 failed |
The grouping is worth noticing. Three of the five are one condition with one remedy, and the other two are separate conditions with their own. That is a better basis for a plan than the digits, which look related and are not.
Telling a real install from a stuck one
| What you observe | What it means |
|---|---|
| The system tray Office icon shows progress | A real installation or update is running. Wait for it |
| No tray icon and nothing progressing | A previous run is holding the claim. Restart |
| The error appears immediately after a restart | A pending operation is still queued from before it |
| Windows Update is mid-cycle | Another installer has the machine and Office is behind it |
| Another user session is active on the same host | Somebody else is installing on a shared machine |
| 30010-45 or 30088-26 preceded it | An FSLogix rule is hiding an Office executable. Fix the rule |
Microsoft’s documented remedies, in order
- Check the system tray for the Office icon and read the install progress from it.
- If an install is already running, wait until it is done before starting yours.
- Restart the computer, then reinstall Office.
- If that does not work, use the uninstall troubleshooter to remove Office, restart when prompted, and reinstall.
- If the troubleshooter leaves anything behind, follow Microsoft’s manual uninstall procedure.
Ending the Click-to-Run processes or stopping its service is not part of Microsoft’s guidance for this code. If the processes are genuinely writing at the time, you can be left with an Office that neither runs nor repairs, and the only route back is a full removal and reinstall. Restart first, and treat a service stop as a last resort on a machine you are prepared to rebuild.
If you do reach for the last resort
- Confirm from the tray icon and from Task Manager that nothing is progressing – no CPU, no network, no disk.
- Confirm a restart has already been tried and did not clear it.
- Stop the Click-to-Run service from an elevated prompt, then run setup immediately, before anything restarts it.
- If Office will not start afterwards, remove it completely with Microsoft’s uninstall troubleshooter rather than attempting a repair on the remains.
- Reinstall from a fresh download, or from a local copy pulled with the Office Deployment Tool.
Why it keeps happening on the same machine
Usually because an update runs on a schedule that overlaps with when somebody tries to install, or because a run is repeatedly interrupted by a logoff or a forced restart. On shared infrastructure it is almost always the second. Install with the machine otherwise idle, and on a session host with no users connected, and it stops recurring.
Things worth ruling out before you conclude it is a lock
- A second Office product installing at the same time – a standalone Visio or Project deployment kicked off by a management tool.
- A management agent that starts an Office update at logon, which collides with a technician’s manual install every time.
- A pending restart from an unrelated installer, which blocks setup without any Office process being involved.
- An FSLogix rule, if the error was preceded by 30010-45 or 30088-26.
- A previous failed install, if the code is actually 0-3 rather than 0-1018 – Microsoft gives that one a different cause and a repair-first remedy.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0-1018 |
Microsoft: this error usually occurs if another installation, update, or uninstall was running before you tried to install Office | Microsoft Support |
17003-2031 |
Published on the same page as 0-1018 and with the same cause | Microsoft Support |
2035-0 |
Published on the same page as 0-1018 and with the same cause | Microsoft Support |
0-2031 |
Microsoft shows 0-2031 (17004) on the dialog that follows 30010-45 and 30088-26, where FSLogix is hiding an Office executable. No general meaning is published | Microsoft Learn |
0-3 |
Microsoft: when installing Microsoft 365, you might see this error if a previous installation of Microsoft 365 failed | Microsoft Support |
Confirm the fix worked
- Setup runs past the point it previously refused.
- Open Word and check File, then Account for the expected version and channel.
- Confirm no Office installer process is left running once the installation has finished.
- Restart and open an Office application, to confirm nothing is queued from the failed attempts.
- On a shared host, confirm
qusershows no other session mid-install before you hand the machine back.
Questions people ask about this
How long should I wait before assuming it is stuck?
Check the system tray icon first – that is Microsoft’s own first step and it tells you whether anything is happening. If progress is moving, keep waiting; a full build over a slow link takes a long time. If nothing has moved for a quarter of an hour, restart.
Should I stop the Click-to-Run service?
Not as a first move, and not at all if you have not restarted. Microsoft’s documented steps are to check the tray, wait, restart, and reinstall. Stopping the service while it is genuinely writing can leave an Office that neither runs nor repairs.
Is 0-3 the same problem?
No. Microsoft gives 0-3 its own cause: you might see it if a previous installation of Microsoft 365 failed. The remedy starts with an Online Repair rather than with waiting for a lock to clear.
I see 0-2031 after another error. What is that?
Microsoft shows 0-2031 (17004) on the dialog that follows 30010-45 or 30088-26, where FSLogix is set to hide an Office executable. If you run FSLogix, list the rules with frx.exe and remove any that hide Office binaries.
Is there anything to buy to fix this?
No. This is a lock on the local machine and has nothing to do with your licence or subscription.
