Microsoft Word Won’t Open Documents from Network Drives

If you’re running a business and suddenly find that Microsoft Word crashes when opening documents from your Windows Server, you’re not alone. A critical bug in Word Version 2601 (Build 16.0.19628.20166 and later) is affecting our customers across Oxford, Oxfordshire and Buckinghamshire, particularly those using Windows Server 2016 for file storage.

The Problem: Word Crashes on Network Documents

Many of our Oxford-based businesses have reported the same frustrating issue:

• Double-clicking a Word document stored on a network server causes Word to open briefly, then crash immediately
• Attempting to reopen shows the error: “Word couldn’t start last time. Safe mode could help you troubleshoot the problem, but some features might not be available in this mode“
• The crash repeats in a continuous loop
• Documents stored locally on the computer open without issues
• The problem specifically affects files on Windows Server 2016 network shares accessed via mapped drives or UNC paths.
• We have seen businesses running MS Word Build 16.0.19628.20166 and Build 16.0.19628.20204 affected.

What’s Causing This Word Bug?

Microsoft introduced a bug in Word Version 2601, Build 16.0.19628.20166, that affects how the application handles documents opened directly from network locations. If your Oxford or Oxfordshire office recently updated to this version or later (including build 16.0.19628.20204), you’re likely experiencing this problem.

The bug appears to be related to Protected View and how Word initialises when launching directly from a network file path, rather than from the application itself.

Working Workarounds for our Oxford Businesses

While Microsoft works on a permanent fix, our IT support team has identified three reliable workarounds:

Workaround 1: Open Word First, Then Browse to File

1. Launch Microsoft Word from your Start menu or desktop shortcut
2. Click File > Open
3. Browse to your network location and select the document
4. The file will open successfully

This method works consistently but adds extra steps to your workflow.

Workaround 2: Drag and Drop into Open Word Window

1. Open Microsoft Word (blank document is fine)
2. Open File Explorer and navigate to your network document
3. Drag the file directly into the Word window
4. The document opens without crashing

This technique is faster than using File > Open and works well for many of our Oxfordshire customers who frequently switch between documents.

Workaround 3: Downgrade to the Previous Word Build

For organisations with multiple computers, downgrading Word to a stable build is the most practical solution:

1. Close all Microsoft Office applications
2. Open Command Prompt as Administrator
3. Run this command:

"C:\Program Files\Common Files\microsoft shared\ClickToRun\officec2rclient.exe" /update user updatetoversion=16.0.19530.20184

3. Wait for the downgrade to complete
4. Verify Word opens network documents correctly

After downgrading, you should disable automatic Office updates to prevent Word from updating back to the buggy version. This can be done individually in MS Office Options or via Group Policy for all network computers.

Preventing Auto-Updates Across Your Network

To stop this issue from recurring across your Oxfordshire business network, disable Office automatic updates using Group Policy:

1. Open the Group Policy Management Console on your domain controller
2. Navigate to: Computer Configuration > Administrative Templates > Microsoft Office 2016 (Machine) > Updates
3. Set “Enable Automatic Updates” to Disabled
4. Set “Hide option to enable or disable updates” to Enabled
5. Apply the policy to client machines

Need IT Support in Oxford or Oxfordshire?

If your Oxford or Oxfordshire business is struggling with this Word bug or other Microsoft Office issues, professional IT support can help implement these workarounds quickly across your entire network. Local Oxford IT providers understand the specific needs of Oxfordshire businesses and can ensure your team stays productive while Microsoft resolves this issue.

For immediate assistance, consider reaching out to our support specialists.