Error Code 30029-4 Fix: Office Won’t Install (Solved)

Error code 30029-4 means that Click-to-Run — the engine that downloads and assembles Office on your PC — could not finish installing or updating its components. The operation stopped partway through and rolled itself back. Nine times out of ten the culprit is a half-applied package: an update that was interrupted, a corrupted cache, or an Office installation already sitting on the machine in a broken state. Note what this code does not tell you: nothing at all about your product key. Your licence is only checked the first time you open Word or Excel. Here is the full sequence, from a simple reboot to a clean offline reinstall.

What does error 30029-4 actually mean?

Click-to-Run has been the Office installer since 2013. It streams the program files to your disk while you wait and keeps them patched in the background, which is why every 30xxx code traces back to it — the second number roughly indicates which stage the process reached before giving up. Microsoft has never published a code-by-code table, so the practical approach is to work through the causes one by one.

• An interrupted update — PC shut down, screen went to sleep, connection dropped — leaving a package half applied.
• A corrupted Click-to-Run cache, stored in C:\ProgramData\Microsoft\ClickToRun.
• The Microsoft Office Click-to-Run Service stopped or disabled.
• An Office version already installed, or its leftovers: an old MSI-based release, an expired Microsoft 365 subscription, a 32-bit and 64-bit mix.
• A broken Windows Update: the Office engine leans on it.
• An antivirus, firewall, VPN or proxy blocking access to Microsoft’s servers.
• A nearly full disk, or damaged system files.

Worth committing to memory: a 30xxx code always concerns the installation, never the licence. A faulty or refused key produces a 0xC004… activation error instead — a completely different family of problems, with completely different fixes.

The fixes, from the mildest to the most drastic

1. Start again from a clean slate

1. Reboot the PC. Locked files are released, and a pending update sometimes finishes on its own once the machine comes back up.
2. Close Word, Excel, Outlook and Teams, then end any remaining OfficeClickToRun.exe processes in Task Manager.
3. Check disk space and connection: at least 4 GB free on C:, wired Ethernet if you have the option, VPN and proxy switched off.
4. Relaunch the installer as administrator, from the very beginning — never by resuming the session that failed.

2. Repair Office and force the update through

If Office is already on the machine, the built-in repair tool rebuilds whichever components are broken. It is the least invasive fix, and it works more often than people expect.

1. Open Settings > Apps > Installed apps, select Microsoft Office or Microsoft 365, then click Modify.
2. Run a Quick Repair first: a few minutes, no internet connection required.
3. If the error comes back, move up to Online Repair. It re-downloads and reinstalls everything, so budget around thirty minutes and leave the machine alone while it runs.
4. To push a stalled update through by hand, open a Command Prompt and run: “C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe” /update user

If Office does not appear in the list even though its folders are still sitting on the disk, the registry entries are gone — skip straight to step 4.

3. Restart the Click-to-Run service and clear its cache

This service drives every Office installation and update on the machine. Stopped, disabled, or fed by a corrupted cache, it produces exactly this kind of code.

1. Press Windows + R, type services.msc, open Microsoft Office Click-to-Run Service, set its startup type to Automatic and start it. While you are there, check that Windows Update has not been disabled either.
2. From an administrator Command Prompt: net stop ClickToRunSvc then net start ClickToRunSvc.
3. Empty %temp%, then — with Office closed and the service stopped — delete C:\ProgramData\Microsoft\ClickToRun. It is rebuilt automatically on the next attempt, so there is nothing to back up.
4. If Windows Update is failing too: net stop wuauserv, rename C:\Windows\SoftwareDistribution to SoftwareDistribution.old, then net start wuauserv.

4. Remove everything with SaRA, then reinstall

When the engine stays stuck no matter what, start from zero. A standard uninstall through Control Panel leaves far too much behind to be useful here.

1. Download the Microsoft Support and Recovery Assistant (SaRA) and run its Office uninstall option. Orphaned registry keys and residual folders go with it — that is the whole point of using it rather than the normal uninstaller.
2. Let the tool finish, then reboot. Two restarts are occasionally requested; give it both.
3. Reinstall from your Microsoft account or from the official link supplied with your licence, keeping the same architecture throughout. Mixing 32-bit and 64-bit is a reliable way to trigger the error all over again.

One honest word of warning. A cracked activator of the AutoKMS type, or a so-called “pre-activated” Office bundle, hooks itself into this very service and breaks its update chain. Windows Defender then neutralises the loader, which is why these machines throw 300xx codes in series, month after month. Remove it along with its scheduled tasks, clean up with SaRA, and start again on a genuine Office activation key — it is the only way to keep receiving security patches, and the only configuration a support team can realistically help you with.

5. Offline installation and system diagnostics

When the progress bar dies at the same percentage every single time, take the network out of the equation with the Office Deployment Tool (ODT), free from Microsoft. Prepare a configuration.xml file declaring the version, language and architecture you want, then:

• download the payload: setup.exe /download configuration.xml
• install it from disk: setup.exe /configure configuration.xml

Back that up with a clean boot — run msconfig, open the Services tab, tick “Hide all Microsoft services”, disable everything that remains — and then check the system itself with sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth. Reboot between the two and try the installer again.

If none of that worked

Let us be blunt. If 30029-4 survives SaRA, an offline installation and a clean boot, the problem is no longer Office — it is the system underneath. A corrupted user profile, group policies inherited from an old corporate PC, damaged Windows components: any of these will keep the installer on its knees. Create a fresh local administrator account and try from there. If the error follows you into the new profile, only a Windows reset will settle it. Back up your documents first, then repair or reset from Settings > System > Recovery.

The other dead end shows up later. Office finally installs, you open Word, and the key is refused. A key that is blocked, revoked, or already used more times than it allows cannot be repaired — no command will bring it back to life. From the Office folder, check it with cscript ospp.vbs /dstatus, then try cscript ospp.vbs /inpkey:YOUR-KEY followed by cscript ospp.vbs /act. If the Microsoft server rejects it, that answer is final; the same logic applies to Windows keys tested with slmgr. If the message specifically says the key is already in use on another device, our guide to error 25004 and keys already in use covers what can and cannot be recovered. That leaves two ways out: Microsoft support, invoice in hand, or a new licence. Our hub of Windows and Office activation error fixes maps out the rest of the codes, and a genuine Office 2021 Pro Plus licence at €19.90 is the shortcut when the old key is simply dead.

For the record, the pre-owned licences sold here are perfectly legal in the European Union. The Court of Justice settled the question in its UsedSoft v. Oracle ruling (C-128/11): once a software licence has been sold for the first time inside the EU, the rights holder’s distribution right is exhausted and the licence can lawfully be resold. Every key comes with its official Microsoft download link and EU-based support behind it.

Frequently asked questions

Does error 30029-4 destroy my Office product key?

No. It happens while files are being downloaded and assembled, well before anything is submitted to Microsoft’s activation servers — your key stays valid and works normally after a clean reinstall. A 30xxx code points at the cache, a previous installation or the network, nothing else. If you were mid-installation when it appeared, no activation attempt was ever recorded against your key.

Do I have to uninstall the old Office before installing the new one?

Yes, almost always. An old MSI-based Office living alongside a Click-to-Run version, or an expired Microsoft 365 subscription sharing the machine with Office 2021 or 2024, is a textbook cause of 30029-4. Uninstall, reboot, then install — and use SaRA rather than the standard uninstaller if the previous version ever crashed or was force-removed. Your documents are untouched by any of this; only the applications are removed.

Is 30029-4 an activation error or an installation error?

Strictly an installation error. Activation problems announce themselves differently: a 0xC004 code, a “product key not working” message, or Office opening in read-only mode with a yellow banner across the top. If your copy installs correctly but then reports itself as unlicensed, the cure is in our guide to the Office “unlicensed product” message, not on this page.

30029-4, 30015-11 and 30180-4: is it the same fault?

Same engine, three different moments. 30029-4 lands while a component is being installed or updated; 30015-11 stops the installer as it starts up; 30180-4 hits during the download and unpacking phase. Seeing these codes one after another is a strong signal that a residual installation is in the way — go straight to step 4 rather than working through the list again.