This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 76%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELP%3C/text%3E%3C/svg%3E)
Current System State
1. Office binaries
2. Registration layer failures
COM registration for Word.Application and shell open commands for Word.Document.12 appear missing or invalid.
3. Store interference ruled out
No Store-based Word app.
No “Office Desktop Apps” package.
PowerShell enumeration shows only two benign Office utilities (OfficePushNotificationUtility and ActionsServer).
No hidden AppX stubs.
Troubleshooting Already Performed
What I’m Looking For
I’m seeking guidance from people familiar with deep Windows registration internals, specifically:
My Current Hypothesis
At this point, I suspect the Windows registration layer is damaged beyond the reach of standard repair tools. A bare‑metal rebuild may be the only reliable fix, since it resets:
If the issue persists even after a clean rebuild, the remaining explanation is that Word’s registration model has an edge‑case failure that this system has exposed.
Any insights, diagnostic steps, or confirmation from others who have seen this failure mode would be greatly appreciated.
A family of Microsoft word processing software products for creating web, email, and print documents.
Yes, I previously ran Online Repair from Windows Settings > Apps > Installed Apps > Microsoft 365 > Modify > Online Repair. I can make further clarifications or additions to the page if that will help. Just let me know.
Just as you recommended, I re-ran Online Repair from Windows Settings twice, ensuring that Online Repair was explicitly selected. Each time, Online Repair completed without error. I then shut down the machine and restarted it. Once I logged back into Windows, I waited a few minutes to ensure the system was stable. Please post my request so I can get insights and recommendations from others.
I want to clarify that I never reported Word displaying the message, "We’re sorry but Word has run into an error that is preventing it from working correctly… Would you like to repair now?" No such message appeared, and there was no indication of any error when I ran Online Repair. The only sign that the installation failed is that a reduced-functionality version of Word was installed.
This is evident because under the File menu, critical controls like "Options" and "Account"—which are present in the full desktop version—are missing. Key features such as document creation and full editing capabilities are absent. The installed version primarily functions as a document viewer with a simplified interface lacking the full Word toolset.
I identified this by noting the absence of these essential File menu controls and editing tools typical of the full Word desktop application.
Title: Windows 11 launches stripped‑down Word viewer instead of desktop Word; protocol handlers and COM registrations missing even after Online Repair
I’m dealing with a Windows 11 system where the Microsoft 365 desktop Word binaries are fully present and intact, but Windows refuses to recognize the installation at the registration layer. Every attempt to launch Word—whether via file association, protocol, or directly through WINWORD.EXE—opens the stripped‑down “Office Viewer” interface instead of the full desktop application.
I want to clarify that I never reported Word displaying the message, "We’re sorry but Word has run into an error that is preventing it from working correctly… Would you like to repair now?" No such message appeared, and there was no indication of any error during normal use. The only sign that the installation failed is that a reduced-functionality version of Word was installed.
This is evident because under the File menu, critical controls like "Options" and "Account"—which are present in the full desktop version—are missing. Key features such as document creation and full editing capabilities are absent. The installed version primarily functions as a document viewer with a simplified interface lacking the full Word toolset.
1. Office binaries
Launchable directly, but still open the viewer shell.
Not replaced by Store apps; no AppX version of Word is installed.
2. Registration layer failures
ms-word: and microsoft-word: protocol handlers are missing entirely.
.docx, .doc, .rtf file associations are broken and cannot be reassigned to desktop Word.
Default Apps only offers “Browse apps in the Microsoft Store.”
COM registration for Word.Application and shell open commands for Word.Document.12 appear missing or invalid.
3. Store interference ruled out
No Store-based Word app.
No “Office Desktop Apps” package.
PowerShell enumeration shows only two benign Office utilities (OfficePushNotificationUtility and ActionsServer).
No hidden AppX stubs.
Verified integrity of Office binaries.
Confirmed absence of Office Hub and other Store components.
Ran Online Repair (not Quick Repair).
Online Repair completed successfully but did not rebuild any of the missing registration components.
System still launches the fallback viewer.
I’m seeking guidance from people familiar with deep Windows registration internals, specifically:
How to identify missing or corrupted keys in HKCR and related hives.
PowerShell techniques for enumerating orphaned COM classes and AppModel registrations.
Whether SxS assembly corruption or AppModel Runtime failures could block Word registration.
Whether there are known cases where Online Repair fails to rebuild protocol handlers.
At this point, I suspect the Windows registration layer is damaged beyond the reach of standard repair tools. A bare‑metal rebuild may be the only reliable fix, since it resets:
Registry hives
AppModel Runtime
COM registration
SxS assemblies
Protocol handlers
File associations
Virtualization layers
Windows Installer database
If the issue persists even after a clean rebuild, the remaining explanation is that Word’s registration model has an edge‑case failure that this system has exposed.
Any insights, diagnostic steps, or confirmation from others who have seen this failure mode would be greatly appreciated.Title: Windows 11 launches stripped‑down Word viewer instead of desktop Word; protocol handlers and COM registrations missing even after Online Repair
Body: I’m dealing with a Windows 11 system where the Microsoft 365 desktop Word binaries are fully present and intact, but Windows refuses to recognize the installation at the registration layer. Every attempt to launch Word—whether via file association, protocol, or directly through WINWORD.EXE—opens the stripped‑down “Office Viewer” interface instead of the full desktop application.
1. Office binaries
Verified present and intact under C:\Program Files\Microsoft Office\root\Office16.
Launchable directly, but still open the viewer shell.
Not replaced by Store apps; no AppX version of Word is installed.
2. Registration layer failures
ms-word: and microsoft-word: protocol handlers are missing entirely.
.docx, .doc, .rtf file associations are broken and cannot be reassigned to desktop Word.
Default Apps only offers “Browse apps in the Microsoft Store.”
COM registration for Word.Application and shell open commands for Word.Document.12 appear missing or invalid.
3. Store interference ruled out
No Store-based Word app.
No “Office Desktop Apps” package.
PowerShell enumeration shows only two benign Office utilities (OfficePushNotificationUtility and ActionsServer).
No hidden AppX stubs.
Verified integrity of Office binaries.
Confirmed absence of Office Hub and other Store components.
Ran Online Repair (not Quick Repair).
Online Repair completed successfully but did not rebuild any of the missing registration components.
System still launches the fallback viewer.
I’m seeking guidance from people familiar with deep Windows registration internals, specifically:
How to identify missing or corrupted keys in HKCR and related hives.
PowerShell techniques for enumerating orphaned COM classes and AppModel registrations.
Whether SxS assembly corruption or AppModel Runtime failures could block Word registration.
Whether there are known cases where Online Repair fails to rebuild protocol handlers.
At this point, I suspect the Windows registration layer is damaged beyond the reach of standard repair tools. A bare‑metal rebuild may be the only reliable fix, since it resets:
Registry hives
AppModel Runtime
COM registration
SxS assemblies
Protocol handlers
File associations
Virtualization layers
Windows Installer database
If the issue persists even after a clean rebuild, the remaining explanation is that Word’s registration model has an edge‑case failure that this system has exposed.
Any insights, diagnostic steps, or confirmation from others who have seen this failure mode would be greatly appreciated.
Answer accepted by question author
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(86.4, 71%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERS%3C/text%3E%3C/svg%3E)
Hi Luis,
How are you launching Word? Can you please try running the following command from the Start/Run dialog?
winword.exe /safe
And, if possible, post a screenshot of the Word program window.
I launched Word in safe mode - no joy; same result.
Answer recommended by moderator
Ramesh: Here are two screenshots of my Word interface.
Hi Luis,
The interface looks normal to me.
Are you able to click on the "Account" option. It's shown in your 2nd screenshot.
Yes, indeed; I see Account and, beneath it, Options. I suppose in my frustration I failed to see them. Thank you, and God bless you. The issue is now resolved.
You're very welcome, Luis.
Glad it's sorted.
Did you uninstall Office per recommendation by Ramesh? Using the special tool you can download?
Then restart your computer?
Then reinstall Office desktop apps from your Microsoft account?
See comment below - under Ramesh.
It sounds very much as if you are opening online Word (Word for the Web) rather than the desktop application.
Sarah's statement leaves me wondering whether she understands that the opening of Word for the Web is happening despite the fact that Microsoft 365 desktop version is actually installed. The (full version) Word binaries are present and intact, but Windows refuses to recognize the installation at the registration layer.
Prior to contacting Microsoft, I ran the SaRA tool to uninstall the current installation then I reinstalled Microsoft 365 Personal - the version I am subscribed to use. However, the sequence and command I used to run SaRA and reinstall the application differs from the instructions Ramesh provides below. Later today I will run SaRA and attempt to reinstall, precisely following his instructions. I'll then report whether this solves the issue. Needless to say I am hopeful. Thank you for your reply.
To reiterate: Despite a verified and healthy installation of the Microsoft 365 desktop binaries, Windows fails to recognize the installation at the registration layer. The system defaults to the "Office Viewer" fallback version. I will follow the instructions provided by Ramesh to remove all remnants of the current installation and then reinstall it. You'll hear back from me later today on the results.
Online Repair is the supported way to rebuild Word’s registrations when the “Repair now” prompt and Quick Repair are ineffective. When Word shows “We’re sorry but Word has run into an error that is preventing it from working correctly… Would you like to repair now?” and that path fails, the recommended resolution is to run a full Online Repair of Office from Windows Settings rather than relying on the in‑app repair.
To run a full Online Repair on Windows 11:
This process repairs the entire Office suite, including Word, and is the supported method when Word’s registration and startup behavior are broken. The automatic “Repair now” path inside Word typically corresponds to a Quick Repair and is noted as generally ineffective for these recurring “run into an error” scenarios; the Online Repair is the documented next step.
If Online Repair has already been run once, repeating it from Windows Settings (ensuring Online Repair is explicitly selected) is still the prescribed remediation in the available guidance for persistent Word startup/registration issues.
References: