Error 30015-4: Why It Happens and How to Install Office

If sfc says it "could not fix some files," run DISM /Online /Cleanup-Image /RestoreHealth first, then run sfc again. DISM repairs the component store that SFC pulls its replacement files from.

Fix 2: Check the hard drive for errors

Bad sectors or a corrupted file system will sabotage any install. Two ways to scan:

1. Error checking (GUI): Open File Explorer, right-click the C: drive, choose Properties > Tools > Check. Enable automatic fixing of file system errors and recovery of bad sectors.
2. Check Disk (command): In an admin Command Prompt, run chkdsk C: /f /r, confirm with Y, and restart. The scan runs before Windows loads.

Fix 3: Cleanly uninstall and reinstall Office

Leftover files are a top cause of 30015-4, so a normal uninstall isn't enough.

1. Download the Microsoft Office Support and Recovery Assistant.
2. Run it and follow the prompts to fully remove the current version (about 10-15 minutes).
3. Sign into your Microsoft 365 account.
4. Choose your Office edition and click Install Now, then complete the prompts.

Fix 4: Reset Windows Update components

Office installs often piggyback on Windows Update services. If those are broken, the install breaks too.

Quick route: Settings > Update & Security > Troubleshoot > Windows Update > Run the troubleshooter.

Manual route (admin Command Prompt):

1. net stop wuauserv
2. net stop cryptsvc
3. net stop bits
4. net stop msiserver
5. ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
6. Restart each service with the matching net start command.
7. Retry the Office install.

Which fix to try first

Fix 5: Clear the registry leftovers

Registry corruption is one of the listed causes, and leftover keys from an old Office version frequently block a fresh install. You don't need to hand-edit the registry — that's risky — but you can clean it safely:

1. Run the Support and Recovery Assistant's full uninstall, which strips most Office registry entries automatically.
2. If keys remain, use Microsoft's documented manual removal steps for your Office version rather than a third-party "registry cleaner," which can do more harm than good.
3. Always create a System Restore point before touching the registry, so you can roll back if anything goes wrong.

Warning: avoid generic registry-cleaner tools for this. They tend to delete entries Windows still needs and can turn a fixable Office error into a much bigger problem. Stick to Microsoft's own removal tools.

Understanding the -1073740791 stop code

The number trailing this error, -1073740791, is more than noise. In hex it's 0xC0000409, a Windows status code for a stack buffer overrun — in plain terms, a process crashed because it hit corrupted or unexpected data. For an Office install, that almost always means the installer touched a damaged system file or a broken component mid-process.

That single detail explains why surface-level fixes fail. You're not dealing with a bad download; you're dealing with a process that crashes when it reaches something rotten in Windows itself. It's also why the repair-the-OS-first approach works so reliably here: fix the underlying corruption and the installer stops crashing.

A diagnostic order that saves time

Run the checks in the sequence below rather than randomly. Each one is quick and rules out a layer:

1. DISM + sfc — repairs the component store and system files. This addresses the most common cause and should always come first.
2. chkdsk — rules out physical drive errors that corrupt files faster than software can fix them.
3. Clean Office removal — eliminates leftover-file conflicts with the Support and Recovery Assistant.
4. Windows Update reset — clears broken update services the Office installer depends on.

Pro tip: if chkdsk reports a growing number of bad sectors across runs, stop installing Office and back up your data. A failing drive is a far bigger problem than an install error, and 30015-4 can be the first warning sign.

Common mistakes that prolong this error

• Reinstalling before repairing Windows. Because 30015-4 is usually a system-file or drive problem, jumping straight to reinstall wastes time. Run sfc and chkdsk first.
• Interrupting chkdsk or sfc. Both can take a while and look frozen. Let them complete — a half-finished repair is worse than none.
• Forgetting antivirus. Security software is a listed cause. Temporarily disable it during the install, then re-enable it immediately after.
• Skipping the restart. chkdsk runs at boot, and several fixes only take effect after a reboot. Don't retry the install until you've restarted.

Using a Windows repair install as a clean reset

When sfc, DISM, and chkdsk all report problems they can't fully fix, an in-place repair install rebuilds Windows without touching your apps, files, or settings. It's the strongest fix short of a full reinstall, and it almost always clears 30015-4 caused by deep system corruption.

1. Download the Media Creation Tool from Microsoft and create installation media, or mount a Windows ISO.
2. Run setup.exe from within your running Windows, not by booting from the media.
3. Choose to keep personal files and apps when prompted.
4. Let it reinstall Windows over itself — this replaces every corrupted system file with a clean copy.
5. Once it finishes, retry the Office install; the underlying corruption is now gone.

An in-place repair install is dramatically safer than people assume. Done from inside Windows with the keep-everything option, it refreshes the OS while leaving your desktop exactly as you left it. It's the go-to move when corruption keeps coming back.

Why this matters: if you've repaired files twice and the error returns, you're treating symptoms. A repair install fixes the foundation in one pass and saves you from the endless loop of partial fixes.

How to prevent it next time

The single best preventive habit is keeping Windows healthy. Run sfc /scannow occasionally as a checkup, keep your storage drivers current, and shut down cleanly rather than forcing power-offs that corrupt the file system. When you do install Office, use the Support and Recovery Assistant to remove any previous version fully first — that one step eliminates the leftover-files cause that's behind a large share of 30015-4 reports.

Why this matters: 30015-4 is one of the few Office errors that's really a Windows health problem in disguise. Repair the OS layer first and the install usually succeeds on the next try.