Windows · Windows Server  ·  high  ·  Microsoft Office

Office will not install or repair — 30015, 30088, 30183, 30029-4, 1058-13

A Click-to-Run install or repair stops partway with a hyphenated error code. The number is almost never the real fault — a previous install left files behind, something is holding a file open, or the architecture of what is already installed does not match what is being installed.

What you see

Setup runs to somewhere between 10% and 90% and then shows "Something went wrong" with a code like 30015-6 (-1) or 30088-1015. Retrying produces the same code at the same point. On a machine that already has Office, the installer may instead refuse to start at all with 30029-4.

What is actually wrong

Click-to-Run installs into a virtualised package and repairs by replacing it wholesale, so it cannot proceed past a file another process has open, a partially removed previous install, or a mismatch between the 32-bit and 64-bit builds. 1058-13 is different in kind: it usually means a service is disabled or security software is blocking the installer's own executable.

Codes and articles

30015-30088-30183-30029-430045-1058-130-1018Something went wrong office

Start here — find out which fix applies

A script that runs the 8 inspection commands from the write-up below and prints what each one returned. It reads the machine and changes nothing — every command that could write, delete, start or stop is excluded from it by construction. Run this first, then pick the fix its output points at.

Download the read-only diagnosticchanges nothing · safe to run before reading

Fixes (4)

Run the repair from the command line, not the Control Panel
PowerShell as administrator40 minuteslow riskreversible

Office is installed and misbehaving. Start here — an online repair fixes most of these without removing anything.

  1. Close every Office application, including the background processes that outlive the windows.

    PowerShell
    Get-Process WINWORD,EXCEL,OUTLOOK,POWERPNT,MSACCESS,ONENOTE,ms-teams,Teams,OfficeClickToRun -ErrorAction SilentlyContinue | Stop-Process -Force

    A repair that cannot replace a file in use fails with exactly the codes in this entry. The Control Panel repair does not tell you which process blocked it, which is why it appears to fail at random.

  2. Confirm the installed architecture so the repair is told the right one.

    PowerShell
    Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' | Select-Object Platform, ClientVersionToReport, ProductReleaseIds

  3. Run a quick repair first. It re-registers the installation without downloading anything, and it takes a couple of minutes.

    PowerShell
    & "$env:CommonProgramFiles\Microsoft Shared\ClickToRun\OfficeClickToRun.exe" scenario=Repair platform=x64 culture=en-us RepairType=QuickRepair DisplayLevel=True

    Change platform= to x86 if the value read above says 32-bit. Passing the wrong one is itself a source of 30015.

  4. If the quick repair does not hold, run the full online repair. This re-downloads the whole package, so allow for several gigabytes and do not start it on a metered connection.

    PowerShell
    & "$env:CommonProgramFiles\Microsoft Shared\ClickToRun\OfficeClickToRun.exe" scenario=Repair platform=x64 culture=en-us RepairType=FullRepair DisplayLevel=True
Confirm it workedEvery Office application opens and the version reported matches the build you expect.
PowerShell
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' | Select-Object ClientVersionToReport
If you need to undo itA repair changes no user data — documents, profiles and settings are untouched. Nothing to reverse.
Download this fix as a PowerShell scriptneeds an elevated shell · asks before each step
Remove the remains of the previous install properly
PowerShell as administrator, with the machine free for a restart1 hourmedium risknot reversible

A repair fails, or a previous version was uninstalled and the new one will not go on. Appwiz uninstall routinely leaves registration behind that blocks the next install.

  1. Record what is currently registered, so you know what to put back.

    PowerShell
    Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' | Format-List ProductReleaseIds, Platform, UpdateChannel, ClientCulture

    ProductReleaseIds is the list of products the licence covers. Reinstalling without it gets you a different edition than the one that was there, which is the usual reason activation then fails as well.

  2. Download and run the Microsoft Support and Recovery Assistant's Office uninstall tool. It is the only removal that clears the Click-to-Run registration, the scheduled tasks, the shell extensions and the licence tokens together.

    PowerShell
    Start-Process 'https://aka.ms/SaRA-officeUninstallFromPC'

  3. Let it restart the machine when it asks. Do not skip this — the removal is not complete until the pending file operations have run.

  4. Confirm nothing is left registered before reinstalling.

    PowerShell
    Test-Path 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun'

    This should now be False. If it is still True the removal did not finish, and reinstalling on top will reproduce the original error.

  5. Reinstall from the portal, choosing the same architecture and the same products you recorded in the first step.

Confirm it workedOffice installs to completion, opens, and shows the correct account under File → Account.
If you need to undo itThere is no rollback — this deliberately removes the installation. Documents are not touched, but the install itself has to be redone. Confirm the licence and the sign-in details are to hand before starting.
Download this fix as a PowerShell scriptnot reversible · needs an elevated shell · 2 steps you do yourself · asks before each step
Resolve a 32-bit / 64-bit conflict
PowerShell as administrator1 hourmedium risknot reversible

30029-4, or setup says it cannot install this version because another is present.

  1. Find out which architecture is installed.

    PowerShell
    Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' | Select-Object Platform

  2. Check for standalone Office products that install separately and pin the architecture — Project, Visio and the Access Runtime are the usual ones.

    PowerShell
    Get-Package -Provider Programs -ErrorAction SilentlyContinue | Where-Object Name -match 'Microsoft (Office|365|Project|Visio|Access)' | Select-Object Name, Version

    Every Click-to-Run product on a machine must be the same bit-ness. A 32-bit Visio installed years ago will block a 64-bit Office and the error names neither of them.

  3. Decide which architecture you actually want. 64-bit is the right default now; keep 32-bit only if a required add-in or an Access database with 32-bit ODBC dependencies forces it.

  4. Remove everything Click-to-Run with the SaRA tool, then install every product again at the chosen architecture in one pass.

    PowerShell
    Start-Process 'https://aka.ms/SaRA-officeUninstallFromPC'
Confirm it workedEvery Office product opens and reports the same architecture.
PowerShell
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' | Select-Object Platform, ProductReleaseIds
If you need to undo itNone — the old installation is removed. Check any critical add-in supports the architecture you are moving to before you start, because that is not reversible without another full cycle.
Download this fix as a PowerShell scriptnot reversible · needs an elevated shell · 1 step you do yourself · asks before each step
Clear what is blocking the installer itself
PowerShell as administrator30 minuteslow riskreversible

1058-13, or setup exits within seconds of starting.

  1. Confirm the services the installer depends on are running.

    PowerShell
    Get-Service ClickToRunSvc, msiserver, BITS, wuauserv | Select-Object Name, Status, StartType

    1058 is the Windows error for "the service cannot be started because it is disabled". A hardening policy or a cleanup tool that disabled msiserver or BITS produces this and nothing in the Office error names the service.

  2. Start anything that is stopped and set it back to manual.

    PowerShell
    foreach ($s in 'msiserver','BITS') { Set-Service $s -StartupType Manual; Start-Service $s }

  3. Check whether security software quarantined part of the installer, and look at the setup log for the last thing it did.

    PowerShell
    Get-ChildItem "$env:TEMP" -Filter '*.log' | Where-Object Name -match 'Microsoft Office|SetupExe' | Sort-Object LastWriteTime -Descending | Select-Object -First 3

  4. Retry the install with real-time protection paused, if your endpoint policy permits it, and re-enable it immediately afterwards.

Confirm it workedThe installer runs past the point it was failing at and completes.
If you need to undo itSet any service you changed back to its previous start type; nothing else here persists.
Download this fix as a PowerShell scriptneeds an elevated shell · 1 step you do yourself · asks before each step

Related faults

Outlook keeps asking for a password and will not accept itWindowsOffice says "Product Deactivated" or "Unlicensed Product"WindowsOffice is stuck on an old build, or a bad update needs rolling backWindowsOutlook cannot set up the account, or connects to the wrong serverWindows

Where this stops. This write-up was written and checked by hand. It says what each step changes, how to confirm it worked and how to reverse it, and anything destructive is flagged before you reach it. If it does not match what your machine is doing, search the Support Centre for the exact code or message — and when something needs a person, get in touch.