How to Fix “General File Open Failure” in Microsoft Teams

A “General File Open Failure” in Microsoft Teams occurs when the application cannot initialize the viewer component or negotiate a valid access token with SharePoint Online. Instead of displaying your Word, Excel, or PowerPoint document inside the Teams workspace, the app stalls and drops an error banner.

Fast Fix

Click the three dots (…) next to the file name and select Open in browser or Open in app. If the document opens there, the issue is an isolated Teams client cache failure. Quit Teams, delete the local cache folder in %localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams, and relaunch the application.

---

Diagnostic Snapshot

Indicator	Details
Error Type	Client-side viewer rendering failure / Token handshake timeout
Primary Location	Teams Desktop (Windows/macOS) embedded Office viewer
Data Risk	Zero; the file in SharePoint or OneDrive remains intact
Admin Involvement	Rare; typically resolved on the client device

---

Why the Teams File Viewer Fails

Teams does not contain native document rendering engines. When you open an Office document directly inside Teams, the app loads an embedded web session using Microsoft Edge WebView2.

This process breaks down when:

1. The WebView2 Runtime Cache Becomes Stale: If cached security tokens expire while Teams remains running, the embedded browser window cannot authenticate to the backend SharePoint storage endpoint.
2. File Handler Protocol Errors: Setting the default file-open behavior to “Desktop app” fails if your local Office installation is corrupted or has an unverified activation state.
3. Session Interruption on Large Files: Large files (especially complex spreadsheets or rich presentations) may hit an internal rendering timeout before the web viewer generates the first page layout.

If the file refuses to open on mobile devices as well, consult Teams Mobile App “Cannot Open File” Diagnostic to rule out device-specific network bottlenecks.

---

Progressive Troubleshooting Steps

1. Change the Default File Open Preference

Teams gives you three ways to open files: in Teams (the default embedded viewer), in the browser (Office on the web), or in the installed desktop application. Bypassing the built-in viewer immediately isolates whether the issue is Teams-specific.

1. In Microsoft Teams, click Settings and more (the three dots next to your profile picture) > Settings.
2. Select Files and links from the left-hand menu.
3. Under Always open Word, PowerPoint, and Excel files in, switch the setting from Teams to Browser or Desktop app.
4. Return to your channel or chat and attempt to open the file again.

[User clicks file] ──> Default: Teams (WebView2 Viewer) ──> Fails: "General File Open Failure"
                    └── Bypassed: Browser / Desktop App  ──> Bypasses Teams cache ──> Success

2. Clear Modern Teams and WebView2 Cache

If switching to the browser works, the Teams local runtime is holding a broken session handle. Clearing this cache forces Teams to generate a clean WebView2 workspace.

1. Right-click the Teams icon in the Windows taskbar system tray and select Quit.
2. Press Windows Key + R to open the Run prompt.
3. Paste the following path and press Enter: %localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams
4. Select all files and folders in this directory (Ctrl + A) and delete them.
5. Next, check if a dedicated WebView2 profile cache exists by navigating to:
   Clear any stale folders found here to purge bad authentication tokens. %localappdata%\Microsoft\IdentityCache
6. Relaunch Teams and test the file.

If your Teams application also throws authentication pop-ups or code loops after clearing the cache, review Resolving “Something Went Wrong” Error 1001 in Outlook and Teams.

3. Verify Desktop Office Activation State

If you chose “Desktop app” and immediately hit the “General File Open Failure” message, Teams is calling an unactivated or unresponsive local Office executable.

1. Open Word or Excel directly from your Windows Start menu.
2. Go to File > Account.
3. Confirm whether your product status shows Subscription Product for [Your Account] or highlights an activation error.
4. If an activation error or “Account Notice” appears, your desktop Office suite will refuse command-line file open requests sent by Teams.

If a local Office application closes the instant Teams hands off the document, check Microsoft 365 Apps Closing Immediately After Sign-in.

4. Check for Cloud File Deletion or Renaming

When a coworker moves, deletes, or renames a document while you are looking at the channel file list, Teams maintains a ghost reference until the view refreshes. Clicking that listing triggers a general open failure because the underlying URL no longer points to a valid SharePoint object.

1. At the top of the Teams channel Files tab, click the Refresh button.
2. Check if the file name changes or disappears from the list.
3. If the file is missing, click Open in SharePoint in the top menu and check the SharePoint Recycle bin from the left navigation pane.

If the file vanished from the view entirely, reference “This item might not exist” Error in Teams Files Tab.

---

When to Involve IT

If multiple users receive a “General File Open Failure” across different channels on both the web and desktop applications, the issue is not a local client cache bug. It points to a tenant-level access disruption:

• SharePoint Service Outage: Verify Microsoft 365 Service Health for degraded SharePoint Online or Teams file services.
• Conditional Access / Device Compliance: If your organization requires compliant devices, an unmanaged machine may be blocked from downloading or launching local file handlers while still being allowed to browse Teams chats. Consult your IT team to verify endpoint compliance policies.