logo
search
Office Apps Crashing

How to Fix Office Apps Crashing When Opening Files from an SMB Share

Chanuka GeekiyanageChanuka Geekiyanage Oct 12, 2026 869 views

Question details

User experiences crashes in Office applications when trying to open files hosted on an SMB network share, while the same files work fine locally or on cloud storage.

How to Fix Office Apps Crashing When Opening Files from an SMB Share
Product
Microsoft Office
Device & OS
not provided
Scenario
Opening Word, Excel, or other Office documents directly from a local network SMB share.
Observed behavior
The Office applications crash or close unexpectedly when loading the files from the SMB share, but operate normally when accessing files from a local drive, OneDrive, or SharePoint.
Before you start

Verify your network connection stability and test opening the same file from a local drive to ensure the file itself is not corrupted before altering network or trust settings.

Solution 1Recommended

Unblock File Properties and Adjust Protected View

Use this solution if the files were downloaded from the internet or saved from Outlook attachments, as Windows may block them and cause Office Protected View to crash.

Microsoft Office utilizes Protected View to secure files originating from potentially unsafe locations. Sometimes, attempting to sandbox a file hosted on an SMB share causes the application to crash.

1
Locate the file

Navigate to the SMB network share where the affected document is stored.

2
Open file properties

Right-click the document and select 'Properties' from the context menu.

3
Unblock the file

Look at the bottom of the General tab. If you see a security warning stating the file came from another computer, check the 'Unblock' box and click 'Apply'.

4
Adjust Trust Center settings

Open the Office application (e.g., Word), go to File > Options > Trust Center > Trust Center Settings, and add your SMB share path to 'Trusted Locations'.

Unblock File Properties and Adjust Protected View
Security Warning: Only unblock files and add trusted locations if you are absolutely certain that the source and the network share are secure.
Free Microsoft Office alternative

Try WPS Office for Stable Network File Access

If Microsoft Office continues to crash when accessing files over your local SMB network, consider switching to WPS Office. It provides a highly compatible, lightweight alternative that handles local and network drives efficiently without heavy resource overhead or aggressive blocking mechanisms.

  1. 1. Download WPS Office: Visit the official WPS website and download the free installation package.
  2. 2. Install and set as default: Run the installer and choose to set WPS Office as your default application for documents, spreadsheets, and presentations.
  3. 3. Open network files: Navigate to your SMB share and double-click your files to open them seamlessly in WPS Office.
Free and lightweight office suite with rapid launch speedsSeamless format compatibility with Microsoft Office (.docx, .xlsx, .pptx)Stable performance when accessing documents over SMB network sharesFamiliar tabbed user interface for an easy and quick migration
microsoft office alternative - wps office

Frequently Asked Questions

Why does Word or Excel crash only when opening files from a network share?

This usually happens due to network latency, restrictive SMB permissions, or Office's Protected View struggling to secure a file over a network protocol. Cloud storage uses different synchronization methods, which is why OneDrive or SharePoint files remain unaffected.

How do I add an SMB share to Trusted Locations in Office?

Open your Office application, click File > Options > Trust Center > Trust Center Settings > Trusted Locations. Click 'Add new location', check the box to 'Allow Trusted Locations on my network', enter your SMB share path, and click OK.

Will reinstalling Microsoft Office fix the SMB crash issue?

Reinstalling or repairing Office rarely fixes this specific issue, as it is typically caused by Windows file blocking properties (Mark of the Web) or server-side SMB configurations rather than a corrupted Office installation.