Excel 0x8007003B Crash When Saving to Network Drive
Excel crashes with error 0x8007003B when saving to a network drive on Windows 10. This is usually a path length or SMB issue, not a damaged file.
Why Does Excel Crash with 0x8007003B?
This error hits when you’re saving an Excel file to a mapped network drive or UNC path on Windows 10. You click Save, Excel freezes for a second, then closes itself. The error code 0x8007003B means “An unexpected network error occurred.” In my experience, it’s almost always one of two things: the file path is too long (over 255 characters) or Windows 10’s SMB protocol is having a fit with Excel’s auto-save or file-locking handshake. It’s not a corrupted workbook — your file is fine, the network connection is just choking on something.
Let’s walk through this step-by-step. Start with the quick fix below. If that doesn’t work, move to the moderate fix. Only the last section is a registry edit — skip it if you’re not comfortable editing the registry.
Quick Fix (30 seconds): Check the File Path Length
- Close Excel if it crashed. Open File Explorer and browse to the network drive where you were trying to save.
- Right-click the folder you’re saving into, then click Properties. Look at the Location field — it shows the full UNC path (like
\server\share\folder). - Count the characters in that path. Add the filename you’re saving (including .xlsx). If the total is over 255 characters, that’s your problem.
- What to do: Copy the file to a shorter path. For example, from
\\server\share\Accounting\2024\November\Reports\Final\Weekly_Summary_Nov_2024_v3.xlsxto\\server\share\Nov2024.xlsx. Then open it from there and save again.
Expected outcome: If the path was too long, Excel should now save without crashing. If it still crashes, move to the moderate fix below.
Moderate Fix (5 minutes): Disable Excel’s Auto-Save and File Locking
This fix targets Excel’s background auto-save feature, which sometimes clashes with network drives over SMB. It’s safe — you’ll just need to manually save.
- Open Excel from your Start menu (don’t open the problem file yet).
- Click File → Options → Save.
- Under Save workbooks, uncheck AutoSave OneDrive and SharePoint Online files by default on Excel. (If you don’t see this, skip it.)
- Then uncheck Save AutoRecover information every X minutes. This turns off Excel’s periodic auto-save.
- Click OK to close Options.
- Now click File → Options → Trust Center → Trust Center Settings.
- In the Trust Center, click File Block Settings.
- Make sure Open and Save for Excel 97-2003 workbooks (.xls) are not checked (they’re usually fine). This step is about rule-following, not fixing — but some reports say locking settings here cause conflicts.
- Click OK twice to close all dialogs.
- Reopen your workbook from the network drive and try saving again.
Expected outcome: If auto-save was the culprit, Excel will save without crashing now. If it still crashes, proceed to the advanced fix.
Advanced Fix (15+ minutes): Registry Tweak for SMB 3.0 Timeout
This is the one that fixes most stubborn cases. Windows 10 uses SMB 3.0 by default, and Excel’s file locking can time out with certain NAS devices or older network switches. The fix is to disable SMB leasing in the registry — it forces Windows to use a simpler locking mechanism.
Warning: Editing the registry can break your system if you mistype a key. Back up your registry first: File → Export in Regedit.
- Press Win + R, type
regedit, and hit Enter. - Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters. - Right-click in the right pane, select New → DWORD (32-bit) Value.
- Name it DisableLeasing and set its value to 1.
- Click OK.
- Now navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters. - Right-click in the right pane again, New → DWORD (32-bit) Value.
- Name it Smb2LeasingDisabled and set value to 1.
- Click OK and close Registry Editor.
- Restart your computer. This is important — the settings only apply after reboot.
Expected outcome: After restart, open Excel, load your file from the network drive, and save it. The crash should be gone. If it’s not, check if your antivirus is blocking Excel’s temp files — try temporarily disabling it (not recommended long-term) to test.
One More Thing: Check Your Network Drive’s SMB Version
If the registry fix didn’t help, your NAS or server might only support SMB 1.0 (super old). Windows 10 has SMB 1.0 disabled by default. To check: open PowerShell as admin and run Get-SmbServerConfiguration | Select EnableSMB1Protocol. If it’s False, you need to enable SMB 1.0 (but please don’t — it’s insecure). Better solution: update your NAS firmware or replace it with a modern one that supports SMB 2.0 or 3.0.
That’s the complete fix flow. Start with the path check, then the Excel settings, then the registry tweak. Nine times out of ten, the registry tweak is the real fix. Good luck.
Was this solution helpful?