Why Word Reports ‘Disk Is Full’ on a Network Share With Free Space

When you try to save a document to a network drive, Word may display a “Disk is full” error even though the server shows hundreds of gigabytes of free space. This error occurs because Word writes temporary files in the same location as the document, and the network share or the user account lacks the required permissions to create or modify those hidden files. This article explains why the false positive happens, how to check the real cause on the server side, and the specific permission changes that resolve the problem without moving the file.

Why Word Reports a False Disk Full Error on Network Drives

Word does not simply check the free space reported by the operating system before saving. Instead, it follows a multi-step save process that involves creating a temporary file with a .tmp extension in the same folder as the document. After the save completes, Word deletes the original file and renames the temporary file to the original name. This mechanism prevents data loss if the save is interrupted.

When the target folder is on a network share, Word must have permission to create, write, and delete files in that folder. If any of these operations fail, Word interprets the failure as a full disk. The most common causes are:

• Insufficient NTFS permissions: The user account has Read and Execute or List Folder Contents only, but not Write or Modify.
• Share permission restrictions: The share itself is set to Read-only for the user.
• Disk quota enforcement: The server has quotas enabled, and the user has reached or exceeded their limit.
• File system filters or antivirus: Third-party software on the server or client may block .tmp file creation.
• Volume shadow copy or deduplication locks: Rare server-side configurations that prevent file writes.

Steps to Diagnose and Fix the Disk Full Error on a Network Share

Method 1: Verify and Adjust NTFS Permissions on the Server Folder

1. Identify the exact folder path on the server
   On the server, open File Explorer and navigate to the folder that is shared. Right-click it and select Properties.
2. Open the Security tab
   In Properties, click the Security tab. Under Group or user names, select the user account that receives the error. If the account is not listed, click Edit, then Add to include it.
3. Grant Modify permission
   In the Permissions list, check the Allow box for Modify. Modify includes Read, Write, Execute, and Delete. Click Apply and OK.
4. Test the save from Word
   On the client machine, open Word and try to save a new document to the same network path. If the error persists, proceed to Method 2.

Method 2: Check and Update Share Permissions

1. Open the Sharing tab on the server
   Right-click the folder and select Properties. Click the Sharing tab, then click Advanced Sharing.
2. Open Permissions
   In Advanced Sharing, click Permissions. Select the user or group that accesses the share.
3. Allow Full Control or Change
   Check the Allow box for Full Control or Change. Read-only permission blocks Word from writing temporary files. Click Apply and OK.
4. Restart the file server or clear the SMB cache
   On the client, open Command Prompt as administrator and run net use /delete to clear cached connections. Then reconnect to the share and test Word.

Method 3: Check Disk Quotas on the Server

1. Open the volume Properties on the server
   In File Explorer on the server, right-click the drive letter that hosts the shared folder and select Properties.
2. Go to the Quota tab
   Click the Quota tab. If quotas are enabled, click Quota Entries.
3. Review the user’s quota limit and usage
   Find the user account in the list. If the Amount Used column shows a value equal to or greater than the Quota Limit, the user has exceeded the quota. Increase the limit or disable quotas for that user.
4. Apply the change and test
   Click OK to close all dialogs. On the client, reconnect to the share and try saving from Word again.

Method 4: Disable Antivirus Real-Time Scanning on the Network Folder Temporarily

1. Locate the antivirus settings on the client or server
   Open the antivirus software. Look for Real-Time Protection, On-Access Scanning, or File System Protection.
2. Add an exclusion for the network folder path
   Add the full UNC path (for example, \\server\share\folder) to the exclusion list. If the antivirus runs on the server, add the local folder path instead.
3. Test the save in Word
   Save a document to the same network location. If the error stops, the antivirus was blocking Word’s temporary file creation. Keep the exclusion in place.

If Word Still Reports Disk Full After the Main Fix

Word Saves to a Different Location Than Expected

Word may be trying to create temporary files in the user’s local temp folder or in a subfolder that does not exist on the network. Check AutoRecover and default save locations in File > Options > Save. Ensure the default local file path points to a local folder with sufficient space and write permissions.

Network Drive Mapped With Different Credentials

If the user mapped the drive with one set of credentials but Word runs under different credentials, the save may fail. Open Credential Manager in Windows, remove any stored credentials for the network share, and remap the drive using the correct username and password.

Volume Shadow Copy or Deduplication Services Interfere

On Windows Server, Volume Shadow Copy Service or Data Deduplication can lock files during backup windows. Check the server’s event log for errors related to VSS or dedup. If the error occurs at a specific time each day, schedule the save outside the backup window.

Word Save Methods: Local Save vs Network Save Behavior

Item	Local Drive Save	Network Share Save
Temporary file creation	Creates .tmp file in same folder	Creates .tmp file in same network folder
Permission required	Write and Delete	Write, Delete, and Modify on share and NTFS
Error if permission missing	Access Denied	Disk is full or Access Denied
Antivirus interference	Rare	Common with network scanning policies
Quota enforcement	Rare on local drives	Common on file servers

Word’s save process on a network share is identical to a local save in terms of file operations. The difference is that network shares introduce two layers of permissions and additional server-side services that can block the temporary file creation, causing the misleading disk full error.

You can now identify the exact permission layer or server configuration that triggers the false disk full message. Start by granting Modify on both NTFS and share permissions, then check for disk quotas and antivirus exclusions. For persistent issues, review the server’s event logs under Applications and Services Logs for SMB or file system warnings that pinpoint the blocked operation.