Short answer: Office error code 147-0 tells you Click-to-Run thinks an update is still running, so Office apps refuse to open. Restart the PC, then run Quick Repair from Programs and Features. If it returns after every reboot, we'd delete the stuck AppVISV registry key, run Online Repair or reinstall Office.
You click Word and expect your document, not Office error code 147-0 in a dialog box. That dialog shows up in its place, with the code at the bottom. It comes from Click-to-Run, never from an MSI install. Your files are safe, and so is the license.
Unable to start Office. We couldn’t open Office because we’re updating, adding or removing programs. Please try later.
- Restart once, after a few minutes of waiting.
- Quick Repair from Programs and Features.
- Back after every reboot? The AppVISV registry key.
- Still there: Online Repair.
- Last resort: uninstall and reinstall.
Nothing is updating. You just wanted to type. It’s a crowded club.
The Click-to-Run service believes an update, repair or uninstall is still running. So the Office apps refuse to start.
Somewhere, the service stuck a “busy” note on the fridge and forgot to take it off. Your files are fine. Your license is fine. Office itself is usually fine too.
The good news: the fix typically takes 3 minutes. The bad news: if the error comes back after every reboot, you’re looking at a registry fix.
Below are all 7 fixes in the order we’d try them, plus a PowerShell section for people who’d rather script their way out.
| Point | What to know |
|---|---|
| Type of error | A Click-to-Run error: only Click-to-Run Office shows it (Microsoft 365, 2019, 2021, 2024), never MSI installs |
| Microsoft’s own order | Wait a few minutes, restart, then uninstall and reinstall. Quick Repair and Online Repair sit in between and save most installs |
| Recurring after a “successful” repair | Points to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppVISV key |
| SaRA | Gone, Microsoft has retired it. Microsoft’s uninstall troubleshooter now runs in the Get Help app, and it can’t remove Office 2024 |
| Applies to | Microsoft 365 Apps, Office 2024, Office 2021 and Office 2019 Click-to-Run on Windows 11 and Windows 10 |
How to fix Office error code 147-0: the order to try
Top to bottom. Stop as soon as Office opens. Every step keeps your documents, and only the last one removes Office itself.
Before step 1, do what Microsoft’s own page says: wait a few minutes and restart the PC once. Sometimes a real background update was finishing.
If the restart changes nothing, look for a stuck updater. Press Ctrl + Shift + Esc, find Microsoft Office Click-to-Run in Task Manager and choose End task.
Then restart once more. Leave other Windows processes alone.
- Run Quick Repair.
- Delete the AppVISV registry key.
- Run Online Repair.
- Launch Office as administrator.
- Catch up on Windows Update.
- Do a clean boot to find conflicts.
- Uninstall with the Get Help troubleshooter and reinstall.
| Step | Fix | Time | Works? | Keeps data |
|---|---|---|---|---|
| 1 | Quick Repair | 2-5 min | Often | Yes |
| 2 | Delete the AppVISV registry key | 3 min | Often, for recurring cases | Yes |
| 3 | Online Repair | 10-20 min | Almost always | Yes |
| 4 | Launch Office as admin | 30 sec | Rarely | Yes |
| 5 | Catch up on Windows Update | 10-30 min | Rarely | Yes |
| 6 | Clean boot to find conflicts | 15 min | Sometimes | Yes |
| 7 | Uninstall with the Get Help troubleshooter and reinstall | 30-60 min | Eventually | Files yes, Office no |
What causes Office error code 147-0
The cause sits in Click-to-Run, the service that installs and updates modern Office. Microsoft calls it C2R.
It streams updates down in the background while you work. That works great, until it doesn’t.
Our guide to the Office Click-to-Run service explains what it does day to day. Here’s how it breaks.
An update kicks off. Something interrupts it. A forced shutdown, an antivirus scan that killed the wrong process, or a Windows Update fighting for bandwidth.
C2R drops a “still working, come back later” flag and forgets to clean it up. Word sees the flag at the next start and refuses.
We went through forum threads and Microsoft Q&A posts, and reproduced the error on test VMs. It comes down to five buckets.
| Bucket | Detail |
|---|---|
| Damaged Click-to-Run files | The biggest chunk of cases. The usual culprit is a failed update, a crash partway through one, or an antivirus that quarantined OfficeClickToRun.exe mid-download |
| Confused registry | Two places hold “update in progress” state, and both sometimes forget to clean themselves up |
| Something fighting Office | Antivirus, mostly. Bitdefender and some ESET configurations come up a lot in the threads. VPN agents too; a few builds of Cisco AnyConnect and GlobalProtect have been named |
| Windows behind on updates | A smaller slice, but real. A missing system component update can trip the updater’s checks |
| Old Office not fully removed | This one hits upgraders who moved from an MSI Office 2016 to Microsoft 365 without fully removing the old one. Those two don’t coexist. They fight, and C2R loses |
| Where the “update in progress” state lives |
|---|
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppVISV |
HKEY_CURRENT_USER\Software\Microsoft\Office\ClickToRun |
The thing to hang onto: your Office install is probably not broken. The fix is basically telling it that it’s done and can relax.
Fix 1: Quick Repair
Start here. Always start here. It sounds too basic, and we’d run it anyway.

Quick Repair checks the installation against the files already on disk and replaces damaged ones. It needs no internet connection.
It takes a few minutes and keeps documents, settings and the license.
- Press Win + R, type
appwiz.cpland press Enter. Programs and Features opens. - Find your Office entry. It may read Microsoft 365, or Microsoft Office Home and Business 2024, or whichever version you bought.
- Right-click it, choose Change and say yes to the UAC prompt.
- Pick Quick Repair and click Repair.
- Wait for the “Done repairing!” message.
- Restart the PC and try Word.
On Windows 11 there’s a modern route: Settings, Apps, Installed apps. Find Office, click the three dots and choose Modify. Different path, same repair dialog.
Now the gotcha. Quick Repair says it succeeded, and Word still throws the error the second you click the icon.
Don’t run Quick Repair again. The files aren’t what’s broken anymore. Go to Fix 2, because it’s a registry problem now.
Fix 2: the AppVISV registry key
Most articles on this topic bury this fix at step five or six. For a recurring error, we find it’s usually the real problem.
The key holds C2R’s “update in progress” state. When that state gets wedged, Office reads it on every launch and shows the error.
It keeps doing that until you remove the key. No repair touches this part.
Back up the registry before you touch anything. Don’t skip this.
- Open
regedit. - Choose File, Export.
- Save the .reg file somewhere easy to find.
Deleting the wrong key is really easy in regedit. You’ll want a way back.
- Press Win + R, type
regeditand press Enter. - Paste the first path from the table below into the address bar.
- Right-click the AppVISV key, choose Delete and confirm.
- Go to the second path from the table.
- Look for a Postpone or UpdatePending entry there. If either exists, delete it.
- Close regedit and restart.
| Path | Value |
|---|---|
| First | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppVISV |
| Second | HKEY_CURRENT_USER\Software\Microsoft\Office\ClickToRun |
Office recreates clean keys at the next launch, so you lose nothing.
We ran this on two machines stuck in the loop after Quick Repair had claimed victory. One was on Windows 10 and one on Windows 11. Both came back clean after one reboot.
Microsoft doesn’t document this registry fix on its support pages. It’s a community fix that works in many recurring cases. To stay on the documented path, we’d go straight to Online Repair and the uninstall troubleshooter.
Fix 3: Online Repair
Run it when Quick Repair and the registry fix don’t clear the error.
It downloads a fresh copy of Office from Microsoft and puts it over the existing one. That catches missing DLLs and half-overwritten files that Quick Repair misses.
| Online Repair | Detail |
|---|---|
| Needs | An internet connection |
| Time | 10 to 20 minutes on normal broadband |
| Your files | Kept |
The path is the same as in Fix 1. Only pick Online Repair this time.
Microsoft’s repair guidance lists it as the next step after Quick Repair, so this is the documented route.
When it finishes, Office may ask you to sign in again. Use the same account as before.
Watch for one message: “We need to close some programs but weren’t able to.” It tells you a process has a lock on an Office file.
Open Task Manager and end every Office process you see. Then repair again.
| Process to end | What it is |
|---|---|
OfficeClickToRun.exe |
The Click-to-Run service |
WINWORD.EXE |
Word |
EXCEL.EXE |
Excel |
OUTLOOK.EXE |
Outlook |
OfficeBackgroundTaskHandlerRegistration.exe |
A background task helper |
If the same message shows a second time, something outside Office holds the file. That’s the clean boot in Fix 6.
Fix 4: run Office as administrator
The quickest one in the list. Half a minute. We’d do it before committing to anything bigger.
It helps only when your user account lacks the permissions Click-to-Run needs. That mainly happens on work and school PCs.
- Open Start and find the Office app that won’t open.
- Right-click it and pick Run as administrator.
- Say yes to the UAC prompt.
If Office opens that way but not normally, you have a permissions problem and not damaged files.
| Where | Next move |
|---|---|
| Your own PC | Check your account type under Settings, Accounts |
| A work laptop | Group Policy is likely in your way, and IT has to sort it |
It won’t fix damaged files. It does rule out permissions in 30 seconds.
Fix 5: pending Windows updates
A boring fix. Sometimes it’s the whole answer.
The Office updater’s checks can run into an out-of-date system component. An unfinished Windows update can also hold files Office needs.
- Press Win + I for Settings.
- Open Windows Update and select Check for updates.
- Install whatever it finds, optional updates included.
- Restart and try Office.
Only a small share of cases get fixed by this alone. It costs nothing and runs in the background, so we’d kick it off early.
Fix 6: a clean boot
If Fixes 1 to 3 ran and the error is back, something in your startup is fighting the Click-to-Run service.
A clean boot starts Windows with only Microsoft services and no startup apps. It shows whether third-party software blocks Click-to-Run.
- Press Win + R, type
msconfigand press Enter. - On the Services tab, tick Hide all Microsoft services first. Skip that, and you’re about to disable parts of Windows itself.
- Click Disable all.
- On the Startup tab, click Open Task Manager.
- In Task Manager’s Startup apps, disable every entry.
- Back in msconfig, click Apply and OK. Restart.
Now try Office. If it opens, it’s a startup thing.
Turn services back on in batches of 5 or 10, and restart after each. When the error returns, halve that batch until one is left.
| Usual suspects | Examples |
|---|---|
| Security suites | Bitdefender and some ESET builds come up most in the threads we read |
| VPN clients | Cisco AnyConnect and GlobalProtect |
| “PC optimizer” tools | Any that change service startup types |
Once you’ve found the villain, add an exclusion for Office in its settings or uninstall it. Then put msconfig back to Normal startup.
Fix 7: a full reinstall
The last resort, and a big one. It works when everything else gave up.
Block out 30 to 60 minutes. Have your Office account or Office product key handy.
- Open Microsoft’s support page “Uninstall Office from a PC” and choose the uninstall troubleshooter. If the browser asks to open Get Help, click Open.
- Follow the prompts in Get Help and select the Office version to remove.
- Restart when asked.
- Reinstall Office from your Microsoft account or installer. On 2021, our Office 2021 install guide has the steps.
Not sure about the reinstall steps? Our Office 2024 installation guide walks through every click.
The troubleshooter removes leftover files and registry entries that Programs and Features leaves behind.
What happened to SaRA
Older guides send you to SaRA, the Microsoft Support and Recovery Assistant. Microsoft has since retired it. Microsoft removed its command-line version, SaRACmdLine, from Windows updates released on and after March 10, 2026.
The Get Help app now handles these troubleshooters. IT departments use the GetHelpCmd.exe command-line tool for scripted uninstalls.
| Microsoft’s page says the troubleshooter | What follows |
|---|---|
| Can’t remove Office 2024 | Uninstall that one from Settings, Apps |
| Must run on the PC you want to clean | No cleaning from another machine |
| Needs Windows 10 or later | Older systems are out |
When it doesn’t fully remove Office, a manual uninstall is the fallback.
Our roundup of the Microsoft Office uninstall tool options in 2026 covers every method that still works.
If a reinstall leads to buying a new license, we’d go for a perpetual Office license. You pay once and keep it.
Need a key? Our Microsoft Office Home and Business 2024 comes as a genuine license from HypestKey. Delivery is instant to email.
Fixing Office error 147-0 with PowerShell
If you’d rather script this, you can. A handful of commands replace every GUI step above.
That’s handy over an RMM tool, or for pushing a fix across 50 machines. Clicking through Control Panel gets old fast.
Right-click Start and open an elevated window. Everything below runs there.
| System | Menu entry |
|---|---|
| Windows 11 | Terminal (Admin) |
| Windows 10 | Windows PowerShell (Admin) |
First check whether the C2R service is running:
Get-Service "ClickToRunSvc" | Format-List Name, Status, StartType
Anything other than Running and Automatic is probably your problem. One line fixes it:
Set-Service "ClickToRunSvc" -StartupType Automatic; Start-Service "ClickToRunSvc"
Then clear the stuck registry state in three lines:
Remove-Item -Path "HKLM:\SOFTWARE\Microsoft\AppVISV" -Recurse -Force -ErrorAction SilentlyContinue
Remove-ItemProperty -Path "HKCU:\Software\Microsoft\Office\ClickToRun" -Name "Postpone" -ErrorAction SilentlyContinue
Restart-Service "ClickToRunSvc"
| Command | What it does |
|---|---|
Get-Service |
Shows the service name, status and startup type |
Set-Service and Start-Service |
Set the startup type to Automatic and start the service |
Remove-Item |
Deletes the stuck AppVISV key |
Remove-ItemProperty |
Removes the Postpone entry |
Restart-Service |
Restarts Click-to-Run |
On a machine stuck in this loop, these three lines can clear the error without a reboot. That tends to surprise people. Results may be worse if the damage goes deeper.
You can also trigger an Online Repair from the terminal, the same thing Control Panel does:
& "C:\Program Files\Common Files\Microsoft Shared\ClickToRun\OfficeClickToRun.exe" scenario=Repair platform=x64 culture=en-us RepairType=FullRepair forceappshutdown=True DisplayLevel=True
| Parameter | Note |
|---|---|
platform=x64 |
Change to x86 for 32-bit Office |
culture=en-us |
Swap the culture code for your Office language. On non-English installs, that one matters |
RepairType=FullRepair |
The Online Repair |
RepairType=QuickRepair |
Runs the offline repair instead |
Pushing this through Intune or Configuration Manager to a fleet calls for a detection script. It should check for the AppVISV key first. Fleet reinstalls go through the Office Deployment Tool instead.
You don’t want unprompted registry deletes on healthy machines. That’s how fleet-wide bad days start.
Differences by Office version
The error behaves the same on every Click-to-Run build. MSI-based Office 2016 and older can’t show it. The difference is uninstall tooling.
| Version | Can show 147-0? | Uninstall route |
|---|---|---|
| Microsoft 365 Apps | Yes | Get Help troubleshooter |
| Office 2024 and LTSC 2024 | Yes | Settings, Apps or manual |
| Office 2021 | Yes | Get Help troubleshooter |
| Office 2019 | Yes | Get Help troubleshooter |
| Office 2016, MSI | No | Programs and Features |
| Version | Note |
|---|---|
| Office 2016 MSI and older | Can’t throw 147-0, because it’s a Click-to-Run error. An MSI install with a similar “updating” message has a different code; read the dialog |
| Office 2016 Click-to-Run | Yes, it existed, and it can show the error. Its program files sit under C:\Program Files\Microsoft Office\root\Office16, the same folder name later versions use, which confuses cleanup scripts that try to tell versions apart by path |
| Office 2019 and 2021 | Same as Microsoft 365 as far as this error goes. All fixes, same order |
| Office 2024 | Released October 1, 2024, on the same C2R engine. The gotcha: Microsoft’s uninstall troubleshooter can’t remove it, so use Settings, Apps or a manual uninstall |
| Microsoft 365 Monthly Enterprise Channel | Machines on faster update channels tend to hit the error more often than those on Semi-Annual. More updates, more chances for one to die halfway |
When you upgrade between versions, fully remove the old one first.
A healthy PC can turn into a mess after the 2024 installer runs over a half-uninstalled 2019 suite. Take 10 minutes and do it right.
If none of this works
Rare, but it happens. Check three edge cases before you start shopping for a new laptop.
Two Office installations at once
Microsoft states that Click-to-Run and MSI Office of the same version can’t sit on one PC.
A dusty Office 2016 Professional Plus MSI next to a new Microsoft 365 install puts the two at war.
Remove the older one in Programs and Features, restart, then repair what’s left.
The service got disabled
Press Win + R, type services.msc and find Microsoft Office Click-to-Run Service.
| Check | Expected |
|---|---|
| Status | Running |
| Startup type | Automatic |
| If not | Right-click, Properties, Startup type Automatic, Start |
| A clue | If repair throws error 30068-4 (1058) and not 147-0, the service is off |
Some “debloat” scripts and plenty of corporate policies disable it for reasons nobody remembers. Until it’s back on, nothing else works.
A work laptop under Group Policy
Your IT admin may have locked updates or repairs. You can’t work around that yourself, so talk to IT.
For a personal license, Microsoft’s own support through the Get Help app is the next stop.
Microsoft’s support article for the “Unable to start Office” updating message lists its official steps. Wait, restart, uninstall and reinstall. They match the backbone of this page.
Keeping it from coming back
Most recurring cases trace back to interrupted updates or a second Office copy.
- Let updates finish. Use “Update and restart”, not a hard shutdown. Force-killing updates is the exact recipe for a fresh error.
- Keep Windows current. Old Windows with new Office brings odd update bugs.
- With an aggressive antivirus, add the Click-to-Run process to its exclusions. Thirty seconds now, fewer headaches later.
- Keep one Office install per machine. Two is asking for trouble.
- Before upgrading, check the Office 2024 system requirements. A machine that barely meets spec is where updates time out and leave locks behind.
| Antivirus exclusion | Value |
|---|---|
| File | OfficeClickToRun.exe |
| Folder | C:\Program Files\Common Files\Microsoft Shared\ClickToRun |
Tired of update-related surprises on a work machine? A perpetual Office 2024 install has a fixed feature set and only security updates. We’d say that leaves fewer moving parts than a monthly subscription channel.
Common mistakes with Office error 147-0
- Running Quick Repair again and again. After one success with the error still there, it’s the registry.
- Editing the registry with no backup.
- Hitting the power button during an update.
- Putting a new suite over a half-removed old one.
- Calling a phone number from a pop-up. Office error dialogs never show phone numbers.
- Looking for SaRA. It’s gone, and the troubleshooter lives in Get Help now.
- Switching the Click-to-Run service off with a debloat script.
Related guides
Terms used on this page
| Term | Meaning |
|---|---|
| Click-to-Run, C2R | The service that installs and updates modern Office |
| MSI | The older Windows Installer setup, without Click-to-Run |
| AppVISV | The registry key that holds the “update in progress” state |
| Quick Repair | The fast, offline repair |
| Online Repair | The repair that downloads a fresh copy from Microsoft |
| Clean boot | A start with only Microsoft services and no startup apps |
| Get Help | The Windows app that now runs Microsoft’s troubleshooters |
| SaRA | The Support and Recovery Assistant, now retired by Microsoft |
| UAC | User Account Control, the Windows permission prompt |
| RMM | Remote monitoring and management software used by IT teams |
Typical Office error 147-0 cases
The repair that “worked”
Quick Repair reports success, and the dialog returns at the next click. The stuck state sat in the registry. With the AppVISV key deleted and one reboot, Office opens.
The forced shutdown
A laptop gets powered off in the middle of an update. Next morning no Office app starts. Quick Repair puts it right in a few minutes.
The security suite
Office opens after a clean boot and fails after a normal one. Turning services back on in batches points to the antivirus. An exclusion for Office ends it.
Two suites on one PC
An old MSI suite still sits next to a new Click-to-Run one. The two can’t share a machine. With the old one removed and a repair run, the error stops.
The scam pop-up
A browser window shows the error text and a phone number. It isn’t from Office. Real Office dialogs never show phone numbers.
The disabled service
Some cleanup script had switched the Click-to-Run service off. Repairs failed with a different code. With the service back on Automatic, everything else worked again.
The half-finished upgrade
Someone runs a new installer over an older suite that was only partly removed. The dialog appears on the first launch. After a full removal and a fresh setup, it’s gone.
The work laptop
On a company laptop no repair will start at all. Group Policy has locked it. That one goes to the IT desk.
Office and Windows versions these error 147-0 fixes cover
The repair dialog, registry paths and PowerShell commands are the same on all of the setups below.
| Office, Click-to-Run | Windows 11 24H2, 25H2, 26H2 | Windows 10 22H2 |
|---|---|---|
| Microsoft 365 Apps, Current and Monthly Enterprise channels | Yes | Yes |
| Office 2024 | Yes | Yes |
| Office 2021, Office 2019 | Yes | Yes |
Office error 147-0: quick reference
| Situation | Fastest way |
|---|---|
| First try | Wait a few minutes and restart once |
| Fast fix | Quick Repair from Programs and Features |
| Error returns after every reboot | Delete the AppVISV key after a registry backup |
| Still there | Online Repair |
| Opens only after a clean boot | Find the conflicting startup service |
| Nothing helps | Uninstall with the Get Help troubleshooter, then reinstall |
| Office 2024 | Uninstall from Settings, Apps |
FAQ
What does Office error code 147-0 mean?
Office thinks it's in the middle of an update, repair or uninstall, and it isn't. A stuck state in the Click-to-Run service makes every app wait. So nothing opens until that state is cleared.
What is the fastest fix for error 147-0?
Restart the PC once, then run Quick Repair from Programs and Features. It takes a few minutes. If the error is back after the next reboot, we'd move on to the AppVISV registry fix.
Why does 147-0 come back every time I restart?
In most recurring cases the AppVISV registry key still holds the stuck update state. Office reads it at every launch. We'd back up the registry, delete that key and restart, and Office recreates a clean one.
Can I fix 147-0 without losing my files?
Yes. Quick Repair, Online Repair and the registry fix leave documents, settings and the license alone. Even a full uninstall removes only the Office program. Your files stay where they are.
Does 147-0 happen on every Office version?
On every Click-to-Run version, yes, and the same fixes work. One difference: Microsoft's uninstall troubleshooter can't remove Office 2024. We'd uninstall that one from Settings, Apps if a reinstall is needed.
Can I still use SaRA to uninstall Office?
No. Microsoft has retired the Support and Recovery Assistant. Its Office uninstall troubleshooter now opens in the Get Help app.
Is Office error 147-0 a virus?
No, it's a genuine Office error. A pop-up that tells you to call a phone number is a scam, though. Office error dialogs never show phone numbers, so we'd close it and not call.
Is 147-0 the same as error 30015-11 or 30174-4?
No. This one appears when you open an Office app while Click-to-Run thinks an update is running. The 30000-range codes appear during installation or updates themselves.