How to Fix Microsoft Office Error 30145-13
Error 30145-13 stalls your Office install. Here's how to clear disk space, kill the blockers, and finish the install clean.
Founder & Lead Technician

Quick answer
To fix Office Error 30145-13, run Microsoft's Support and Recovery Assistant, free up 10-15 GB of disk space, temporarily disable your antivirus, and reset the Microsoft Store cache with wsreset.exe. Then reinstall Office from a fresh download.
Error 30145-13 shows up when Microsoft Office's installer can't finish the job — usually because of corrupted download files, not enough free disk space, or security software blocking the process mid-install. The fastest path is to run Microsoft's Support and Recovery Assistant, free up real disk headroom, and temporarily pause your antivirus. Most people are installed and running within twenty minutes.
It's a generic installer failure, so don't panic and don't immediately blame your hardware. The installer choked on something specific, and the steps below isolate it instead of guessing.
What causes Error 30145-13
- Corrupted installation files — the download got interrupted or arrived damaged, so the installer can't unpack a required component.
- Insufficient disk space — Office needs real working room, not just the final footprint.
- Network or proxy issues — a flaky connection or corporate proxy blocks the installer from pulling resources.
- Conflicting software — another program (often a leftover Office version) holds files the installer needs.
- Antivirus or firewall blocking — security tools flag installer processes and quietly stop them.
Check system requirements first
Before troubleshooting, confirm your PC actually meets Office's minimums. Falling short here causes errors that no amount of cache-clearing will fix.
| Component | Minimum requirement |
|---|---|
| Processor | 1 GHz or faster, 2+ cores |
| RAM | 2 GB (32-bit), 4 GB (64-bit) |
| Free disk space | 3 GB minimum (aim for 10 GB+) |
| Graphics | DirectX 9 or later |
| OS | A currently supported Windows version |
That "3 GB" figure is the bare minimum and it's misleading. The installer unpacks temporary files during setup, so give it 10 to 15 GB of breathing room to avoid mid-install failures.
Step-by-step fixes
- Run the Support and Recovery Assistant. Download Microsoft's free SaRA tool, run the Office install/uninstall scenario, and let it auto-detect and repair the most common causes. This alone resolves a large share of 30145-13 cases.
- Free up disk space. Uninstall programs you don't use, empty the Recycle Bin, and move large media files to external storage. Clear 10-15 GB so the installer has room to unpack.
- Disable security software temporarily. Turn off your antivirus and firewall, run the install, then re-enable both immediately afterward.
- Do a clean reinstall. Uninstall the current Office version via Control Panel, delete any leftover Office folders, restart, then download a fresh installer from your Microsoft account.
Fix Microsoft Store and Windows itself
If you installed Office through the Microsoft Store, the Store's own cache is a frequent culprit. Work through these:
- Reset the Store cache. Open the Microsoft Store, go to settings, and choose to reset the cache, then restart.
- Sign out and back in. Log out of your Microsoft account in the Store and sign back in to refresh your license token.
- Reset Store app data. Press
Windows + R, typewsreset.exe, and press Enter. The Store reopens once the reset finishes. - Update Windows. Settings > Update & Security > Windows Update. Missing patches often break installers in ways that look unrelated.
Handle network and proxy interference
If you're on a corporate or campus network, a proxy or firewall is a likely suspect. The Office installer pulls components from Microsoft's servers mid-install, and a blocked request shows up as 30145-13. Work through these:
- Try a different network. Tether to your phone or use home Wi-Fi to confirm the network is the issue. If the install completes elsewhere, the original network is filtering it.
- Temporarily disable the proxy. Settings > Network & Internet > Proxy, and turn off any manual proxy for the duration of the install.
- Whitelist Microsoft's install endpoints. On managed networks, ask IT to allow the Office Content Delivery Network domains so the installer can fetch what it needs.
- Use a wired connection. A flaky wireless link can corrupt the streamed install files; Ethernet is more reliable for a clean download.
If the install fails at the exact same percentage every time on one network but sails through on another, stop troubleshooting your PC. The problem is the network filtering the install, not your computer.
Common mistakes to avoid
- Leaving antivirus off after the install. Disabling it is a diagnostic step, not a fix. Re-enable it the moment Office is installed.
- Not removing leftover Office files. A standard uninstall leaves folders behind that collide with the new install. Use the Support and Recovery Assistant for a truly clean removal.
- Ignoring the temp folder. A full or locked
%temp%directory can block the installer. Clear it before retrying. - Running an old installer. Always download a fresh copy from your Microsoft account rather than reusing a setup file that may itself be corrupted — the original cause of many 30145-13 errors.
How 30145-13 differs from related Office errors
Office install errors look interchangeable but they aren't, and confusing them sends you down the wrong path. Here's how 30145-13 sits next to its cousins:
| Error | Core cause | Where to focus |
|---|---|---|
| 30145-13 | Install blocked: files, space, network, security | SaRA, disk space, antivirus |
| 30015-4 | System file or drive corruption | sfc /scannow, chkdsk |
| 30088-x | Update or component download failure | Network, retry, reset Store |
| 0-1018 | Insufficient disk space specifically | Free up 10-15 GB |
If your code is genuinely 30145-13, the win is usually in the install environment — connection, free space, and security software — rather than deep Windows repair. Why this matters: matching the error to its real cause is the difference between a ten-minute fix and an hour of unrelated scans.
A clean-slate install routine that just works
When you've fought the error more than once, stop patching and do a deliberate clean install. This sequence resolves the stubborn cases:
- Run the Support and Recovery Assistant to fully remove Office, including leftover folders and registry keys.
- Restart the PC — non-negotiable, since it releases locked files.
- Confirm 15 GB+ free space and a stable, ideally wired, connection.
- Add your Office folder to antivirus exclusions before installing.
- Download a fresh installer from your Microsoft account and run it as administrator.
Doing these in order — rather than cherry-picking — is what separates a one-and-done install from the people who hit 30145-13 three times in a row.
Reading Office install logs when all else fails
If you've worked the whole list and 30145-13 still appears, the install logs will tell you precisely which file or step failed. They're plain text and easier to read than they look.
- Press
Windows + R, type%temp%, and press Enter to open the temp folder. - Look for files beginning with OfficeSetup or stored under a folder named after the install session.
- Open the most recent log and search for the words error or failed.
- The line near the failure usually names a specific file, registry key, or network resource — that's your real culprit.
A common find here is a single file the installer couldn't write because antivirus locked it, or a network resource it couldn't reach. The log turns guesswork into a pinpoint fix, which is exactly what you want after several failed attempts. Why this matters: instead of repeating the same broad steps, the log lets you attack the one thing that's actually broken.
How to prevent it next time
Most repeat cases trace back to two habits. First, keep 15-20 GB of free space on your system drive so installs and updates always have room to unpack. Second, install Office over a stable, ideally wired, connection with your antivirus exclusions already in place. Doing both turns a frustrating multi-attempt install into a single clean run.
Why this matters
Error 30145-13 isn't a sign your Office license is broken or your PC is failing. It's an installer that got blocked. Each step above removes one specific blocker — bad files, no space, a security tool, a stale Store cache, a filtering network — so you're not reinstalling Windows over a fixable hiccup. Run them in order and stop as soon as the install succeeds.
Frequently asked questions
What does Office Error 30145-13 actually mean?+
It's a generic installation failure indicating the Office installer couldn't complete. The usual triggers are corrupted download files, insufficient disk space, network or proxy interference, or antivirus and firewall software blocking the install process. It does not mean your license or computer is broken.
How much disk space do I really need to install Office?+
Microsoft lists 3 GB as the minimum, but that figure ignores temporary unpacking files created during setup. Free up 10 to 15 GB of space to give the installer room to extract components. Tight disk space is one of the most common causes of Error 30145-13.
Does resetting the Microsoft Store cache delete my apps?+
No. Running wsreset.exe clears only the Store's temporary cache and license tokens, not your installed apps or data. It's a safe, quick reset that often resolves Store-based Office install errors. The Store simply reopens once the process completes.
Founder & Lead Technician
Harjindar founded Ask Technicians to cut through bad tech advice. He writes hands-on troubleshooting guides drawn from years of real-world repair and support work.
Related guides

Error 30015-4: Why It Happens and How to Install Office
Error 30015-4 blocks your Office install. Repair system files, check the disk, reset Windows Update, and get installed.

Fix the "Something Went Wrong" Error in Microsoft Office
Office won't open and throws "Something went wrong"? Here's the exact order to fix it, fastest path first.

How to Fix the DNS_PROBE_STARTED Error in Google Chrome
Stuck on DNS_PROBE_STARTED in Chrome? Flush the DNS cache, swap to a public resolver, and you're usually back online in two minutes.

Video Playback Error 224003: How to Fix It Fast
Videos failing with error 224003? Clear the cache, kill the extensions, and update codecs to get playback back.
