Error 0x426-0x0 often appears when Office can’t start; restarting Click-to-Run and running an Online Repair fixes most cases.
You click Word or Outlook, the splash screen flashes, then you get a blunt “Something went wrong” message and nothing opens today.
This guide walks you through the fixes that tend to work on Windows 11 and Windows 10, in the order that saves the most time. You’ll start with quick checks, then move into service and repair steps, then finish with a clean reinstall route when nothing else sticks.
Error 0x426-0x0 Fixes That Work On Windows 11 And 10
The dialog that comes with this code often points you toward repairing Office. That’s a good hint, yet it’s not the only angle. In many cases, Office isn’t broken as an app; it’s blocked by the Click-to-Run layer that launches and updates it.
Think of Click-to-Run as the engine room for Microsoft 365 apps on Windows. If that service is stopped, stuck, or set to the wrong startup type, Office can fail to launch and throw this code. Microsoft’s own repair steps also confirm that Quick Repair and Online Repair can replace damaged files and restore normal startup.
What You’re Trying To Fix
- Office won’t open — Word, Excel, PowerPoint, or Outlook closes right away or never appears.
- Office updates got stuck — an update started, then Office began failing after a reboot.
- Click-to-Run isn’t active — the background service that starts Office is disabled or not running.
A Fast Triage Table
Use this table to pick a first move based on what you see. You can still follow the full order below if you’d rather not guess.
| Move | When It Fits | Typical Time |
|---|---|---|
| Restart Click-to-Run | Office won’t launch, no other Windows issues | 2–5 minutes |
| Online Repair | Office fails after an update, files may be damaged | 10–30 minutes |
| Clean reinstall | Repairs fail or the code returns after a day | 30–60 minutes |
What Triggers The Error In Plain Terms
Most people hit error 0x426-0x0 in one of three moments: right after a Microsoft 365 update, right after installing Office, or right after a security tool changes how background services run. The code itself is a sign that Office’s startup chain didn’t complete, so Windows never hands you the full app window.
Common roots include a stopped Click-to-Run service, a partial update that left files in a half-swapped state, or a damaged local cache that Office checks at launch. A smaller batch of cases comes from Windows system file problems that ripple into Office.
Before You Change Anything
- Save open work — close other apps so repairs can replace files cleanly.
- Check your license sign-in — confirm you can sign in at office.com in a browser with the same account.
- Restart Windows once — it clears hung installer tasks and can bring services back.
Quick Checks That Clear Many Cases
These checks take only a few minutes and they often fix the “it broke after a restart” version of the problem. Do them before deeper repairs, since they don’t change your setup much.
Confirm The App You’re Launching
Windows can have more than one Office entry. A store-installed Microsoft 365 app behaves differently from a classic desktop install, and its repair buttons don’t always map to the deeper Office repair options.
- Open Installed Apps — go to Settings, then Apps, then Installed apps, and note whether your entry says Microsoft 365, Office, or a store-style listing.
- Try a different shortcut — open Word from the Start menu search, not a pinned taskbar icon, in case the pin points to an old path.
- Launch in safe mode — press Win + R, type
winword /safe, then press Enter to see if Word starts with add-ins off.
Disable Add-ins That Crash Office At Launch
If Word starts in safe mode, an add-in is a prime suspect. Safe mode loads Office with fewer extras, so a clean start there is a strong clue.
- Open the app normally — try Word first; if it fails, open it again with
winword /safe. - Turn off COM Add-ins — in Word, go to File, Options, Add-ins, then Manage COM Add-ins and untick third-party items.
- Restart and test — close Word, then open it the normal way to see if the crash is gone.
- Add them back one by one — re-enable a single add-in, restart, and repeat until the culprit shows up.
Temporarily Pause Security Tools
If you run third-party antivirus or “cleanup” utilities, they can block services or quarantine Click-to-Run files. Pause them for a short test, then try launching Word again. If that clears error 0x426-0x0, add Office folders to the tool’s allow list and turn protection back on.
Get Click-to-Run Running Again
This is the most common fix path because Click-to-Run sits between Windows and your Office apps. When it’s stopped, Office can’t fully initialize, so the app never reaches the normal window.
Restart The Click-to-Run Service
- Open Services — press Win + R, type
services.msc, then press Enter. - Find Microsoft Office Click-to-Run — scroll to the service name that includes “Click-to-Run.”
- Start or restart it — if it says Stopped, choose Start; if it says Running, choose Restart.
- Set startup to Automatic — open Properties, set Startup type to Automatic, then select Apply.
If the service won’t start and throws its own error, that points to damaged Office components. Move to the repair section next.
Check The Click-to-Run Process Location
It’s rare, yet malware can mimic system processes. A quick file-location check keeps you from chasing the wrong issue. In Task Manager, find OfficeClickToRun.exe, then choose Open file location. A common legitimate path is under Program Files\Common Files\Microsoft Shared\ClickToRun.
Repair Office The Way Microsoft Documents It
When error 0x426-0x0 keeps showing up after you restart Click-to-Run, the next best move is an Office repair. Microsoft documents two layers: Quick Repair for a fast local check, and Online Repair for a deeper reinstall that replaces more components.
Run Quick Repair First
- Open Installed apps — Settings, Apps, Installed apps.
- Pick your Office entry — select the three dots, then Modify.
- Choose Quick Repair — follow the prompts, then reboot.
Quick Repair won’t remove your documents. It also won’t always fix a broken update chain. If Office still fails to open, move to Online Repair.
Reset A Store-installed Office Entry
If your Office entry in Settings looks like a Microsoft Store app, try the built-in reset controls first. They can clear a broken cache without touching your documents.
- Open Advanced options — Settings, Apps, Installed apps, then select the Office or Microsoft 365 entry and choose Advanced options.
- Run Repair — select Repair, wait, then try launching Word.
- Run Reset — if Repair doesn’t change anything, select Reset, then launch Word and sign in again.
Run Online Repair When Quick Repair Fails
- Return to Modify — open the same Office entry and choose Modify again.
- Select Online Repair — follow the prompts and stay connected to the internet.
- Sign in after repair — open Word and sign in so licensing and activation finish cleanly.
Online Repair takes longer, yet it replaces more pieces and it’s the step that clears many stubborn “can’t start” cases. If you’re on a work device with admin restrictions, you may need an admin to run it.
Fix Windows Issues That Can Block Office Startup
If repairs complete and Office still fails with error 0x426-0x0, the problem can be higher up in Windows. System files and servicing components are part of the update and install chain, so a Windows image issue can cause Office repairs to land poorly.
Microsoft documents a safe order for repairing system files: run DISM first, then run SFC. This sequence restores the Windows component store that SFC depends on.
Run DISM And SFC
- Open an admin terminal — search for Command Prompt, then choose Run as administrator.
- Run DISM — type
DISM /Online /Cleanup-Image /RestoreHealth, then press Enter and wait for completion. - Run SFC — type
sfc /scannow, then press Enter and wait. - Restart Windows — reboot, then try opening Word again.
Use Event Viewer To See The Failing Module
If Office closes with no extra clue, Event Viewer can point to a DLL or add-in name. You don’t need to decode each field. You just want the failing file name so you can remove or update the related tool.
- Open Event Viewer — press Win + R, type
eventvwr.msc, then press Enter. - Check Application errors — go to Windows Logs, Application, then filter for Error entries around the last failed launch.
- Note the faulting module — if it names an add-in or security DLL, update or uninstall the related program, then retest Office.
Try A Clean Boot Test
A clean boot starts Windows with a minimal set of startup items, which helps you spot a background app that blocks Office. If Office opens in this state, re-enable items in batches until you find the conflict.
- Open System Configuration — press Win + R, type
msconfig, then press Enter. - Hide Microsoft services — in Services, tick Hide all Microsoft services, then choose Disable all.
- Disable startup apps — open Task Manager from Startup, then disable extra entries.
- Restart and test Office — open Word, then undo the clean boot after testing.
Reinstall Office Cleanly When The Error Keeps Coming Back
If you’ve restarted Click-to-Run, run Online Repair, and repaired Windows files, yet error 0x426-0x0 still returns, it’s time to remove Office completely and install it fresh. A clean reinstall clears leftover update caches and broken registry entries that repairs can miss.
Microsoft provides uninstall steps through Control Panel and an uninstall troubleshooter that removes stubborn installations. If uninstall fails, use the troubleshooter first, reboot, then retry the install from your Microsoft 365 account page.
Remove Office Fully
- Uninstall from Settings — Settings, Apps, Installed apps, then uninstall Microsoft 365 or Office.
- Run the uninstall troubleshooter — use Microsoft’s troubleshooter if uninstall fails or leaves entries behind.
- Restart Windows — reboot before reinstalling to clear pending installer tasks.
Install Fresh And Verify
- Install from your account page — sign in at office.com, then download the installer from your Microsoft 365 account.
- Finish first launch online — open Word once while connected so activation completes.
- Update Office — open any Office app, go to Account, then check for updates.
Keep The Fix From Repeating
Once Office opens again, a few habits lower the chance of the same code returning after the next patch cycle.
- Leave Click-to-Run on Automatic — don’t disable it to save resources, since updates rely on it.
- Avoid aggressive “cleaners” — registry cleaners can remove Office entries that updates expect.
- Let updates finish — if Office starts updating, give it time, then reboot once when it’s done.
- Keep Windows current — install Windows quality updates so servicing components stay healthy.
After a reinstall, take one minute to check your default template and add-in folders. If you carried over an old Normal.dotm template or a legacy Outlook add-in, it can reintroduce the same crash on first launch. If Office opens cleanly, add extras back slowly so you can spot the one that flips it back.
If you want the shortest path, start with the Click-to-Run restart, then run Online Repair, then do a clean reinstall if the code returns. In most homes and small offices, that sequence gets Office opening again without chasing obscure tweaks.
