Fix it now
Microsoft publishes one cause for 30102-11, 30102-13, 30103-11 and 30103-13: an operating system error, or the machine running low on disk space. Its remedies are disk cleanup, a restart, Windows updates, then the two Windows repair commands. Removing Office does not address any of those, so start with free space.
sfc /scannow
dism /online /cleanup-image /restorehealth
- Check free space on the system volume first. Use Settings, then System, then Storage, and act on its cleanup recommendations, including previous Windows installation files if the machine has been upgraded.
- Restart the machine and try the installation again before running anything else. Pending work from an update can produce this on its own.
- Install any outstanding Windows updates and restart again.
- Run the two commands above and let each finish, then restart and retry setup.
Removing previous Windows installation files makes rolling an upgrade back impossible. Only clear them once you are satisfied the machine is otherwise working.
If setup completes you can stop here. If not, the next section explains what the numbers after the dash mean and what to check when the disk is healthy.
Why it happens
This one is worth stating plainly because the internet is full of the opposite advice. Microsoft’s page for 30102-11, 30102-13, 30103-11 and 30103-13 says you might see these errors if there was an operating system error or you are running low on disk space. It does not say another Office installation is in the way, and its remedy list contains no uninstall step at all: clean up disk space, restart, install Windows updates, run the System File Checker, run DISM, and as a last resort refresh Windows or do an in-place upgrade.
That matters because the wrong reading is expensive. Stripping every Office product off a working machine takes an afternoon, loses add-ins and customisations, and leaves you back at the same error with less to work with. If a machine genuinely has two conflicting Office products on it, Windows and the installer report that differently and the coexistence rules are a separate subject.
The number after the dash identifies the sub-stage that raised the failure rather than a distinct fault. Microsoft groups all four on one page with one cause and one remedy list, so treat them as one problem. What varies between them is how far setup got before it gave up, which is why some readers see files appear and then vanish.
The two repair commands are doing different jobs and the order matters. The System File Checker compares protected system files against the component store and repairs what it can. DISM repairs the component store itself, which is where the System File Checker gets its known-good copies. Running the System File Checker against a damaged component store is why people report it finding problems it cannot fix.
The system volume is short of working room
You have this one if Free space on C: is in the low single-digit gigabytes, and setup fails at roughly the same point every time.
- Open Settings, then System, then Storage, and work through its cleanup recommendations.
- On a machine that has been upgraded in place, remove previous Windows installation files – they are frequently the largest single item.
- Aim well above the finished size of Office. A streamed install needs room for the download, the staging and the finished product at once.
- Retry setup with the space available rather than clearing space while it runs.
Windows itself is damaged underneath
You have this one if Other installers fail too, Windows Update reports errors, and the machine has a history of unclean shutdowns.
- Run
sfc /scannowfrom an elevated prompt and let it complete. - Run
dism /online /cleanup-image /restorehealth, which repairs the component store the previous command depends on. - Restart, then run
sfc /scannowonce more and confirm it reports no unrepaired problems. - Retry the Office installation.
If DISM cannot repair the store from Windows Update, it can be pointed at a mounted installation image as a source. That is the step before considering an in-place upgrade.
Pending update work has not finished
You have this one if The failure started the day a feature update or a large cumulative update was installed, and the machine has not been restarted since.
- Restart, and let the machine finish whatever it is configuring at shutdown and start-up.
- Install any remaining updates and restart again.
- Retry setup only once the update history shows nothing pending.
The installation source itself is damaged
You have this one if Every machine installing from the same share fails identically while a fresh download works.
- Rebuild the local source with
setup.exe /download configuration.xmlrather than copying the old folder again. - Check free space on the source volume; a partial write produces failures that look like client faults.
- Install one machine from the rebuilt source before redeploying it.
Windows is damaged beyond what the repair commands can fix
You have this one if The repair commands run cleanly, the disk has space, and setup still fails at the same point.
- Reset the PC with the option that keeps your files, or run an in-place upgrade using the current Windows installation media.
- Back up first. Either route rewrites the operating system around your data and applications.
- Reinstall Office afterwards from a fresh source.
Microsoft lists this last for a reason. It is a long job, and it is the correct answer only once space and the two repair commands have been ruled out.
Full reference
Where the fault actually is
| What you see | Where to look |
|---|---|
| Free space on C: in single-digit gigabytes | Disk space, which is one of the two documented causes |
| Windows Update also failing | The component store; run DISM before anything else |
sfc /scannow finds problems it cannot repair |
The component store is damaged; DISM first, then run it again |
| Only machines installing from one share fail | The source, not the clients |
| The failure began the day of a feature update | Pending work; restart and finish the update first |
| Everything checks out and it still fails | A reset keeping files, or an in-place upgrade |
If a second Office product really is in the way
That is a different problem from this code, and it is worth knowing where the line is. Microsoft publishes which combinations of Office, Visio and Project can share a machine, and the rules are about installation technology, architecture and update channel rather than about licensing model.
| Rule | What it means in practice |
|---|---|
| Same version, different installation technology | Not supported. A Click-to-Run product and an MSI-based product of the same version cannot share a machine |
| Different versions, both Click-to-Run, overlapping applications | Not supported |
| Architecture | All installed products must be 32-bit or all 64-bit. Mixed architectures are not supported and setup fails |
| Update channel | Products on one machine must use the same update channel; a volume-licensed Visio or Project has to be configured to match |
| Licensing model | Subscription Office alongside a volume-licensed or retail Visio or Project is supported, subject to a minimum Microsoft 365 Apps version |
Removing Office properly, when that is genuinely the job
- Note where any PST files live and copy them somewhere safe. Removing Office does not delete them, but knowing where they are costs nothing.
- Uninstall from Settings, then Apps, then Installed apps, or from Control Panel, then Programs and Features, and let it finish.
- If it will not go, run Microsoft’s uninstall troubleshooter. Note that Microsoft states it cannot uninstall Office 2024 and that it needs Windows 10 or later, running on the affected PC.
- Restart, then confirm no Office folder remains under Program Files or Program Files (x86).
- To have setup clear an older MSI-based product for you, put the RemoveMSI element in your Office Deployment Tool configuration and run
setup.exe /configure configuration.xml. It removes 2007, 2010, 2013 and 2016 MSI-based Office, Visio and Project, and has no effect on a Click-to-Run installation.
Deployment reference
| Item | What it does |
|---|---|
setup.exe /download configuration.xml |
Builds the local Office source described by your configuration XML |
setup.exe /configure configuration.xml |
Installs, removes or reconfigures Office from that source |
| RemoveMSI element | Uninstalls 2007, 2010, 2013 or 2016 MSI-based Office, Visio and Project before installing |
| Remove element with All=”TRUE” | Removes all Microsoft 365 Apps products and languages |
| OfficeClientEdition attribute | Fixes the install to 32 or 64; must match an existing Microsoft 365 Apps installation or setup fails |
| Channel attribute | Selects the update channel for everything in that configuration |
One practical note on managed estates. If your deployment tool retries a failed install automatically, a machine short of disk space will fail, retry, and fill the disk a little further each time with staging data. Suspend the deployment for that machine before you start clearing space, or you will be racing it.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
30102-11 |
An operating system error, or the machine is running low on disk space | Microsoft Support |
30102-13 |
Published on the same page with the same cause: an operating system error or low disk space | Microsoft Support |
30103-11 |
Same group, same published cause: an operating system error or low disk space | Microsoft Support |
30103-13 |
Same group, same published cause: an operating system error or low disk space | Microsoft Support |
Confirm the fix worked
- Free space on the system volume is comfortably above what a full Office installation needs.
sfc /scannowcompletes and reports no unrepaired problems.dism /online /cleanup-image /restorehealthcompletes without error.- Setup finishes and File, then Account shows the product, version and channel you intended.
- Windows Update runs cleanly afterwards, which is the sign the component store is genuinely repaired.
Questions people ask about this
Do I need to remove my old Office first?
Not for this code. Microsoft documents these four errors as an operating system fault or low disk space and its remedy list contains no uninstall step. Removing Office is a long job that leaves you at the same error.
Do I need a new licence to get past this?
No. This is a Windows problem rather than a licensing one. Your key or subscription is untouched and reapplies itself when the build starts.
How much free space is enough?
Microsoft does not publish a figure for this error, so aim well above the finished size of the installation. A streamed install needs room for the download, the staging copy and the finished product at the same time, and a disk that is merely not full is not the same as a disk with working room.
Which repair command first?
DISM if Windows Update is also failing, because it repairs the component store that the System File Checker draws its known-good copies from. Otherwise run the System File Checker first, then DISM, then the System File Checker again.
Will I lose my Outlook data?
No. OST and PST files live in your user profile and a mailbox lives on the server. Even so, note where any PST files are before you start any removal work.
