Fix it now
Microsoft publishes 30015-4 together with 30015-1011 and gives one remedy for both: restart the computer and reinstall, then use the offline installer, which it says may help bypass proxy, firewall, antivirus or internet connection problems. Do those in that order before anything more invasive.
- Save your work, close everything, and restart the computer. Microsoft’s first documented step, and it clears a pending file operation that would otherwise stop setup every time.
- After the restart, sign in and start the install once, before opening anything else.
- If it fails again, install with the Microsoft 365 offline installer, or with the Office Deployment Tool:
setup.exe /download configuration.xmlon a machine with a good connection, thensetup.exe /configure configuration.xmlto install from that copy. - If you have 30015-6 rather than 30015-4, do not remove anything. Microsoft says the installation is probably fine and that the message can be dismissed – look for the Office apps on the Start menu and try to start one.
- Only if the log shows a leftover installation is genuinely the blocker, remove Office with Microsoft’s uninstall support tool, restart, and install again from a fresh download.
The offline installer and the Office Deployment Tool are Microsoft’s documented route here, not a last resort. They remove the streaming download – and therefore the proxy, firewall and scanning path – from the equation entirely.
If Office starts and reports the version you meant to install, you can stop here. If setup fails again, the next section explains what the code family does and does not tell you.
Why it happens
Click-to-Run does not lay files down the way an older MSI installer did. It streams a build into place, registers it, and hands the applications over as usable only at the end. Because the intermediate state is not a working Office, a failure part way through leaves the machine looking untouched, which hides the fact that a specific operation failed at a specific moment. That is worth knowing, but it is not the same as saying the installer ‘rolls back’, which is a description no Microsoft page for this code uses.
The suffix after the dash is a stage identifier and Microsoft does not publish a mapping for it. There is a widely repeated rule that low numbers mean local problems and large numbers mean network problems. It is invented, and Microsoft’s own pairing disproves it: it publishes 30015-4 and 30015-1011 on one page, with one cause and one remedy, and that remedy is network-flavoured – restart, then use the offline installer to bypass proxy, firewall, antivirus or internet connection issues. Treat the suffix as an identifier, not as a diagnosis.
Two codes in this family need separating from the rest before you do anything destructive. 30015-6 is not a failure at all in the usual sense: Microsoft states that it appears when a process was not properly shut down at the end of installing Office, that the installation is probably fine, and that you can dismiss the message and try to start an app. And 6-30015, which looks like a typo, is a different condition entirely – Microsoft lists it with 0-1018 under another installation already being in progress.
A pending restart is stopping setup
You have this one if Windows Update recently ran, or another installer asked for a restart nobody performed, and setup fails almost immediately.
- Restart and let any pending updates finish applying before signing back in.
- Open Settings, then Windows Update, and confirm nothing is waiting on a restart.
- Run setup once after the restart, before installing anything else.
The network path is interfering with the download
You have this one if Setup fails at roughly the same point each time, and other machines behind the same gateway behave the same way.
- Use the offline installer, which Microsoft says may help bypass potential proxy, firewall, antivirus or internet connection issues.
- For more control, download the build once with the Office Deployment Tool and install from that local copy.
- If you want to fix the path rather than route around it, have the Office content and configuration hostnames exempted from inspection and from download scanning limits.
Security software is interrupting setup
You have this one if The failure lines up with an entry in the endpoint protection log at the same minute.
- Open Windows Security, then Virus and threat protection, then Protection history, or the equivalent log in your third-party product, and look at the time of the failure.
- Test by turning real-time protection off briefly, on a machine you control and a network you trust, then run setup once.
- Turn protection back on immediately afterwards and remove any temporary exclusion you added.
Microsoft’s own guidance for the related install codes includes temporarily turning antivirus and the firewall off as a test. It is a diagnostic step, not a configuration to leave in place.
A previous installation is still present or half-removed
You have this one if Office is listed in Apps and features, a repair does nothing, and setup fails at the same point every attempt.
- Try an Online Repair first: right-click Start, select Apps and Features, select the Office product, select Modify, then Online Repair and Repair.
- If that fails, use Microsoft’s uninstall support tool rather than removing through Apps and features.
- Restart when it finishes. The removal is not complete until you do.
- Reinstall from a fresh download rather than a cached installer.
There is not enough room, or the temp folder is unusable
You have this one if The system drive is close to full, or the temp path is redirected somewhere the installer cannot use.
- Free space on the system drive and clear the contents of
%temp%. - Run
set tempandset tmpand confirm both point at a local, writable path. A temp folder on a network share or a disconnected drive will fail setup. - Retry with comfortable headroom rather than a few hundred megabytes.
Worth ruling out, but not first. Microsoft’s published guidance for this code does not mention disk space at all – it points at the network path and the offline installer.
Full reference
What each code in this record actually means
| Code | What Microsoft publishes |
|---|---|
30015-4 |
Published with 30015-1011 (1392). Restart and reinstall; then use the offline installer, which may bypass proxy, firewall, antivirus or internet connection issues |
30015-6 |
A process was not properly shut down at the end of installing Office. The installation is probably OK and the message can be dismissed |
30015-1011 |
Published on the same page as 30015-4 (1392), with the same remedy |
30015-45 |
Nothing published |
6-30015 |
Listed with 0-1018 under another installation already being in progress |
If you have 30015-6, read this before removing anything
- Look for the Office applications on the Start menu and try to start one. Microsoft’s guidance is that the installation is probably fine.
- If they start, you are finished. Dismiss the message.
- If they are missing or will not start, restart the PC and look again.
- Only then repair: right-click Start, select Apps and Features, select the Office product, select Modify, then Online Repair and Repair.
- Removing Office at this point is the wrong move and creates work that was not needed.
If you have 6-30015, it is a different problem
Microsoft lists 6-30015 alongside 0-1018 under the heading about another installation being in progress. Check whether an Office update or another installer is running, wait for it to finish, restart if something is stuck, and start the install again. Nothing about the 30015-6 remedy applies to it, despite the digits.
Microsoft’s uninstall support tool removes every Click-to-Run Office product on the machine, for all users, and clears the activation state with it. Before running it, confirm you have the Microsoft account the licence is attached to, or the product key, and confirm from the log or from Apps and features that a leftover installation really is the blocker. A reader who cannot sign in to the licensing account afterwards cannot put Office back.
Installing from a local copy instead of streaming
| Step | What it does |
|---|---|
setup.exe /download configuration.xml |
Pulls the build once into a folder you choose, on a machine with a good connection |
setup.exe /configure configuration.xml |
Installs from that folder, with no streaming from the internet |
SourcePath in the configuration file |
Points the install at the local folder or a file share |
OfficeClientEdition and Channel |
Pin the architecture and update channel so every machine gets the same build |
Where to look when the documented steps have not worked
- Sort
%temp%by date modified and open the newest setup log. The failing operation is named a few lines above the failure. - Check for an older MSI-based Office, or a standalone Visio, Project or Access runtime, that cannot coexist with the build you are installing.
- Confirm the architecture. Installing 64-bit alongside an existing 32-bit product, or the reverse, will fail.
- Check the gateway log for the client at the time of the failure, not a summary. A categorised block shows up immediately.
- Try the install on a machine on a different network. Success there tells you the path is the variable and stops you re-permissioning a healthy computer.
Why retrying does not help
The installer is deterministic. The same blocker produces the same failure, at the same point, every time. Every attempt also costs a full download unless you are installing from a local copy, which is one more reason the offline route is worth taking early rather than late. Establish which blocker applies, fix it once, and run setup a single time.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
30015-4 |
Microsoft publishes it with 30015-1011 (1392): restart and reinstall, then use the offline installer, which may help bypass proxy, firewall, antivirus or internet connection issues | Microsoft Support |
30015-6 |
A process was not properly shut down at the end of installing Office. Microsoft states the installation is probably OK and the message can be dismissed | Microsoft Support |
30015-1011 |
Published on the same page as 30015-4 (1392) and given the same remedy | Microsoft Support |
30015-45 |
Seen during Click-to-Run setup. Microsoft publishes no page for this suffix | not published by the vendor |
6-30015 |
Listed by Microsoft with 0-1018 under another installation already being in progress. Not 30015-6 with the halves swapped | Microsoft Support |
Confirm the fix worked
- Open Word and confirm it starts without a setup or repair prompt.
- Check File, then Account, and confirm the version and update channel are what you intended to install.
- Confirm Office does not appear twice in Apps and features.
- Restart and open Outlook, to prove the installation survives a restart.
- Run an update check from File, Account, Update Options, so you know the content path still works after installation.
Questions people ask about this
Does the number after the dash tell me what failed?
No. It is a stage identifier and Microsoft publishes no mapping for it. The often-repeated rule that small numbers mean local problems and large numbers mean network problems is invented, and Microsoft’s own pairing of 30015-4 with 30015-1011 – same page, same remedy – contradicts it.
I have 30015-6. Should I uninstall Office?
No. Microsoft says the installation is probably OK and that you can dismiss the message and try to start an app. Look on the Start menu, restart if the apps are not there, and use an Online Repair only if they are still missing.
Is 6-30015 the same as 30015-6?
No. Microsoft lists 6-30015 with 0-1018 under another installation being in progress. It is a concurrency problem, and the 30015-6 advice does not apply to it.
Is the Office Deployment Tool worth the effort for one machine?
On a machine that keeps failing, yes. It downloads the build once, installs from that copy, and lets you pin the architecture and channel – which removes the network from the equation and makes the outcome repeatable.
Will I lose my documents or Outlook profile?
No. Removing and reinstalling Office does not touch documents, and Outlook data files and profiles survive. Be aware that Microsoft’s uninstall support tool removes every Click-to-Run Office product for all users and clears activation, so make sure you can license it again before you run it.
