Word

Fix "There Was a Problem Opening This File" Error in Word

Error message: There was a problem opening this file. The file might be corrupted, located on a server that is not responding, or read-only

"There was a problem opening this file. The file might be corrupted, located on a server that is not responding, or read-only" is one of the more honest Word errors — it tells you exactly the three things to check. The order matters, though. Of the three named causes, the file location and read-only attribute are far more common than actual corruption, and they’re faster to test. Working through the causes in order of likelihood resolves most cases in under two minutes without touching repair tools.

This guide takes the three causes one at a time, in the order they’re worth checking.

Quick fix

If the file is on a network share, SharePoint, OneDrive, an external drive, or any non-local location, copy it to your local Documents folder first. This eliminates the entire “server not responding” branch in one step.

  1. Open File Explorer and navigate to the file.
  2. Copy it (Ctrl+C).
  3. Paste it into a local folder, ideally Documents (Ctrl+V).
  4. Open the local copy.

If the local copy opens, the original is fine — the issue was network connectivity, server availability, or sync state. If the local copy still fails, move on to the next strategy.

If that didn’t work

Remove the read-only attribute

Word treats read-only files differently and, in some configurations, refuses to open them entirely rather than opening in read-only mode.

  1. Right-click the file in File Explorer and choose Properties.
  2. On the General tab, find the Attributes section near the bottom.
  3. If the Read-only checkbox is checked, uncheck it.
  4. Click OK and try opening the file again.

For multiple files at once, the command line is faster. Open Command Prompt in the folder and run:

attrib -R "filename.docx"

For all Word files in a folder:

attrib -R *.docx

The -R flag removes the read-only attribute. Use +R if you ever need to re-add it.

If the file is in a folder you don’t have write permissions for, removing the attribute may also fail. In that case, copy the file to a folder you do have write access to (your Documents folder is always safe), then remove the read-only attribute on the copy.

For SharePoint or OneDrive files: re-authenticate

If the file is on SharePoint or in a OneDrive folder synced to your computer, an expired or invalid authentication token can produce this error. Word can see the file but can’t actually retrieve it.

  1. In Word with no document open, click File > Account.
  2. Find your Microsoft account in the User Information section.
  3. Click Sign out and confirm.
  4. Click Sign in and complete the authentication.
  5. Try opening the file again.

For OneDrive sync specifically, also check the OneDrive icon in the system tray. If it shows a sign-in prompt or sync error, resolve those first — the file’s “server not responding” condition often originates from a sync client problem rather than from Word itself.

For mapped network drives: verify the network connection

Mapped network drives can appear available in File Explorer while their underlying connection is broken — particularly common for users on corporate networks where the VPN may have disconnected without user awareness.

  1. Open File Explorer and click on This PC in the left sidebar.
  2. Find the mapped drive in the Network locations section.
  3. If the drive icon shows a red X or warning indicator, right-click and choose Reconnect or Map network drive to re-establish the connection.
  4. If you’re on VPN, verify the VPN is connected. Disconnect and reconnect if uncertain.
  5. Try opening the file again from the network location.

For files on a server you can reach via web browser (corporate file portal, SharePoint), test by opening the location in your browser. If the browser can reach the server, your connection is intact and the issue is something else; if the browser also fails, the server itself is unreachable and the file isn’t openable from anywhere until the server is back.

Now check for actual corruption

If location and read-only are both ruled out — the file is local, writable, and on a working filesystem — the third cause named in the error becomes likely. Run Word’s built-in repair:

  1. Open Word with no document loaded.
  2. Click File > Open > Browse and locate the file.
  3. Single-click the file (don’t open it).
  4. Click the dropdown next to the Open button and choose Open and Repair.

If that fails, try opening in LibreOffice Writer:

  1. Install LibreOffice from libreoffice.org.
  2. Right-click the file and choose Open with > LibreOffice Writer.
  3. If it opens, Save As a fresh DOCX copy.

If both repair attempts fail, the corruption diagnosis is confirmed and the "The file is corrupt and cannot be opened" page covers more advanced recovery approaches.

Why this happens

Word’s check before opening a document is more involved than just reading the file. Word verifies the file is reachable, has the right permissions, isn’t locked, and matches an expected format. Failures in any of these stages can produce this error.

File location not reachable. The most common cause. Mapped network drives that have lost their connection, SharePoint or OneDrive paths where authentication has expired, external drives that have spun down or disconnected, file-server outages — all produce a “file exists in the path but Word can’t actually retrieve it” condition that Word reports with this error.

Read-only attribute set on the file. Some file-extraction processes (notably some email clients extracting attachments) preserve a read-only attribute. Some user actions (like dragging from a CD or read-only network share) inherit it. The file is fine, but Word can’t open it for editing — and depending on configuration, won’t open it for read-only viewing either.

Read-only inherited from folder permissions. Even if the file’s own attribute isn’t read-only, the parent folder may have permissions that effectively prevent Word from opening the file in its normal read-write mode. Common in corporate environments with locked-down folder structures.

Authentication or session expiry on cloud storage. SharePoint, OneDrive for Business, and Microsoft 365 sessions expire periodically. When they do, Word can still see file paths in recently-used lists but can’t retrieve the actual files until you re-authenticate.

Genuine corruption. Less common when the error wording is exactly this string. When corruption is the actual cause, the file usually triggers “The file is corrupt and cannot be opened” instead, which doesn’t mention server or read-only in the message.

Preventing this in future

For files you work with regularly that live on cloud storage, verify your authentication is working before you actually need to open the file. A weekly check-in to File > Account in Word catches expiring sessions before they catch you mid-deadline.

For files coming from email attachments, save them to your Documents folder rather than opening them directly from the mail client. Direct-open from email often inherits unhelpful attributes (read-only, MOTW blocking) that the save-to-disk path strips.

For VPN-dependent network locations, configure your VPN client to reconnect automatically after disconnect. Many corporate VPN clients support this but don’t enable it by default.

For external drives, eject them properly (right-click > Eject in File Explorer) before unplugging. Unclean disconnects sometimes leave file attributes in inconsistent states that produce open errors when the drive is reconnected.

If your file isn’t on a network or cloud location and isn’t read-only, the genuine-corruption branch becomes the relevant one — the "The file is corrupt and cannot be opened" page covers the recovery strategies in detail. If the error you’re actually seeing is about file locking rather than file location, see "Word cannot open this document. The document might be in use by another application" — different cause, similar symptoms.

For broader context on Word document recovery, see the Word repair complete guide.

Last verified: April 2026