Forum Discussion

Les99's avatar
Les99
Copper Contributor
Nov 12, 2026

Word for the web does not open. Documents remain on a loading spinner indefinitely.

What works:

  • OneDrive loads normally.
  • Excel files open and edit successfully in Excel for the web.
  • Word documents can be downloaded from OneDrive.
  • New Word documents can be created, but they also fail to open and remain stuck loading.

Troubleshooting performed:

  • Tested in Microsoft Edge, Chrome, and Safari.
  • Tested in private/incognito mode.
  • Cleared browser cache and cookies.
  • Disabled browser tracking protection.
  • Tested using a different network (mobile hotspot).
  • Issue occurs when opening Word Online directly from Office.com as well as from OneDrive.
  • No 401, 403, 500, or 503 requests appear in the browser network log.
  • The only visible console error is a CORS-related fetch request involving Microsoft services, but OneDrive and Excel continue to function normally.

Account type:

  • Personal Microsoft account (not work or school).

Expected result: Word documents should open in Word for the web.

Actual result: Word for the web remains on an indefinite loading spinner and never opens any document, including newly created documents.

2 Replies

  • Les99's avatar
    Les99
    Copper Contributor

    I suspect this problem might have been related to the recent Microsoft outage, perhaps a precursor to the main event. Yesterday morning I was able to open and edit Word documents. However, I would get error messages from time to time saying a portion of a document that I had been editing wasn’t saved. This usually took a few tries to re-establish access. Today it seems to be back to normal. Hoping it stays that way.

  • Your tests already isolate this beyond one document, browser or network: even newly created Word documents fail, while Excel and OneDrive work. I would not repeat cache clearing or disable more browser protections. The console CORS message alone does not establish the underlying cause. One useful remaining comparison is to try a new blank document with a different personal Microsoft account in a separate browser session, and try your affected account on another device if available. Record those outcomes and a UTC failure time. Then use Microsoft’s Get Help route for personal accounts, describe the Word web loading failure, and select Contact Support when offered; available contact methods depend on the product and subscription. Include your existing browser/network tests and the failing request details. This needs service-side investigation if the failure follows the account. Keep downloaded copies of important documents while awaiting a supported resolution.