This message often does not mean that a disk is full. When it appears while opening a Windows network share, mapped drive, administrative share such as \computerd$, or a remote copy, a common historical cause is an undersized IRPStackSize resource on the computer hosting the share. First identify that host, check for Event ID 2011, and only then consider the legacy registry change described below.
What the error usually means
Windows file sharing normally uses SMB. In the classic case, the client displays the error but the server is the computer that cannot allocate enough I/O request stack resources for the Server service. The word “storage” therefore describes an internal Windows resource, not necessarily free disk capacity.
For a path such as \FILESERVERSharedFolder, investigate FILESERVER. For \COMPUTERNAMEd$, investigate COMPUTERNAME. A Windows registry fix does not apply to a NAS, Linux Samba host, macOS computer, or other third-party SMB appliance unless its vendor specifically documents an equivalent setting.
Microsoft’s historical documentation associates this condition with Event ID 2011 from the Srv service and a too-small IRPStackSize value: archived Microsoft KB guidance.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Run these checks before editing the registry
Confirm the host is not genuinely out of resources
- Check free space on the host’s system drive and the volume containing the share.
- Check memory and page-file capacity in Task Manager or your normal monitoring system.
- If the failure is sudden or intermittent, restart the host once and note whether the symptom returns.
- Review recent antivirus, endpoint-security, backup, encryption, disk-filter, or storage-driver changes.
Check the Server service and network path
Run these commands on the host or from an elevated PowerShell session where appropriate:
Get-Service LanmanServer
Get-SmbServerConfigurationThe LanmanServer service should be running when the machine is providing Windows shares. From the client, test SMB reachability:
Test-NetConnection FILESERVER -Port 445If TCP 445 is unreachable, troubleshoot firewall rules, routing, the server service, or the device itself before changing the registry. As a diagnostic only, try the share by IP address, for example \192.168.1.20SharedFolder. If the IP works but the hostname fails, DNS or name resolution is more likely than an SMB server-resource problem.
Check the exact wording
Do not apply this fix to every message containing the word “storage.” Different errors point to different investigations:
Recommended Free Tools
| Message or symptom | More likely investigation |
|---|---|
| “The network path was not found” | DNS, routing, firewall, or name resolution |
| “Access is denied” | Share permissions, NTFS permissions, credentials, or policy |
| “The specified network name is no longer available” | SMB session stability, network reliability, or protocol/security mismatch |
| “The local device name is already in use” | Mapped-drive conflict |
| “Not enough storage is available to process this command” | Could be memory, page-file, or application exhaustion; it is not automatically the server-share condition |
Event ID 2011 from Srv or LanmanServer |
IRPStackSize, a filter driver, the Server service, or other legacy configuration |
Confirm the diagnosis in Event Viewer
- Reproduce the failure using the same share.
- On the host, open Event Viewer.
- Go to Windows Logs > System.
- Filter or search for source
SrvorLanmanServerand Event ID 2011. - Read the event text. Wording that says the
IRPStackSizeconfiguration parameter is too small strongly supports this specific remedy.
You can also query the log with:
Get-WinEvent -FilterHashtable @{
LogName = 'System'
Id = 2011
} -MaxEvents 10These checks are diagnostic, not proof by themselves. Current Microsoft documentation does not define one universal IRPStackSize value for every supported Windows 10, Windows 11, or Windows Server release.
Rank #2
- 【Versatile Storage Expansion – For Gaming, Work & Everyday Use】 Running out of space on your PS5 or Xbox Series X/S? This external hard drive lets you store and play PS4 / Xbox One games directly, instantly freeing up your console’s internal storage for next‑gen titles. At the same time, it handles work file backups, media libraries, and cross‑device data transfers with ease. One drive, all your needs. *（Note: PS5 / Xbox Series X|S games cannot be run or stored directly from the external hard drive. However, by offloading your PS4 / Xbox One games, you can free up valuable space for newer titles.）*
- 【Patented Silicone Sleeve – Data Protection You Can Count On】 Worried about drops? We’ve got you covered. The patented built‑in silicone sleeve acts like a shock‑absorbing armor, cushioning your drive against bumps and falls. Whether it’s important work documents, precious family photos, or hard‑earned game saves, your data deserves this level of protection.
- 【Plug & Play, Compatible with Computers & Consoles】 No complicated setup—just plug in and go. Works seamlessly with Windows, Mac, and Linux computers, as well as PS4, PS5, Xbox One, and Xbox Series X/S. Process files at the office, back up data at home, or enjoy gaming in your downtime—one drive handles all your devices, simply and hassle‑free.
- 【USB 3.0 Ultra‑Fast Transfer – No More Waiting】 Tired of watching progress bars crawl? With USB 3.0 speeds up to 5Gbps, large files transfer in seconds. Whether you’re moving work documents, transferring hundreds of gigs of games, or backing up a year’s worth of photos, you get more done in less time.
- 【Sleek, Lightweight, and Ready to Go】 Weighing just 0.16 kg—lighter than a can of soda—this compact drive features a stylish mirror‑and‑frosted finish. Toss it in your bag and go, whether you’re heading to the office, visiting a friend for a gaming session, or giving a presentation on the road.
Back up the server’s registry key
Use an administrator account on the file-server computer. Create a restore point if your Windows edition and change-control process support it. Then export the exact key before making any edit.
In an elevated Command Prompt:
reg export "HKLMSYSTEMCurrentControlSetServicesLanmanServerParameters" "%USERPROFILE%DesktopLanmanServer-Parameters.reg" /yAlternatively, press Win + R, enter regedit, select HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanServerParameters, and use File > Export. Store the export somewhere you can access if the server must be recovered.
Set IRPStackSize using Registry Editor
Older Microsoft-hosted support guidance and community answers commonly use 15 decimal. That is legacy troubleshooting guidance, not a current all-versions Windows specification; archived material also describes different hexadecimal ranges and defaults. Use it only when the Windows-hosted share and Event ID 2011 evidence fit the classic diagnosis.
- On the host, open Registry Editor as an administrator.
- Navigate to
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanServerParameters. - Find
IRPStackSize. If it is absent, right-click an empty area and choose New > DWORD (32-bit) Value. - Name the value exactly
IRPStackSize. - Open it, select Decimal, and enter
15as the legacy test value. - Close Registry Editor and restart Windows, or restart the Server service only when your environment permits a controlled service interruption.
- Test the same share again and record the result.
Selecting Decimal matters: entering 15 while Hexadecimal is selected writes a different number. Do not edit a similarly named policy key, misspell the value, or change unrelated LanmanServer settings at the same time.
Use an administrator command instead
The following command changes the registry on the computer where it is run. Run it on the file server, not automatically on the workstation displaying the message, and only after making a backup:
Rank #3
- Value NAS with RAID for centralized storage and backup for all your devices. Check out the LS 700 for enhanced features, cloud capabilities, macOS 26, and up to 7x faster performance than the LS 200.
- Connect the LinkStation to your router and enjoy shared network storage for your devices. The NAS is compatible with Windows and macOS*, and Buffalo's US-based support is on-hand 24/7 for installation walkthroughs. *Only for macOS 15 (Sequoia) and earlier. For macOS 26, check out our LS 700 series.
- Subscription-Free Personal Cloud – Store, back up, and manage all your videos, music, and photos and access them anytime without paying any monthly fees.
- Storage Purpose-Built for Data Security – A NAS designed to keep your data safe, the LS200 features a closed system to reduce vulnerabilities from 3rd party apps and SSL encryption for secure file transfers.
- Back Up Multiple Computers & Devices – NAS Navigator management utility and PC backup software included. NAS Navigator 2 for macOS 15 and earlier. You can set up automated backups of data on your computers.
reg add "HKLMSYSTEMCurrentControlSetServicesLanmanServerParameters" ^
/v IRPStackSize /t REG_DWORD /d 15 /fRestart the host:
shutdown /r /t 0PowerShell can create or replace the same value:
New-ItemProperty `
-Path 'HKLM:SYSTEMCurrentControlSetServicesLanmanServerParameters' `
-Name 'IRPStackSize' `
-PropertyType DWord `
-Value 15 `
-ForceIf you are not comfortable changing the registry, use the graphical procedure or ask an administrator.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.If the registry change does not solve it
Do not keep increasing the number blindly
Some legacy support guidance suggests increasing the value gradually and rebooting between tests. If you follow that approach, change only one value at a time, record the original setting, avoid arbitrary large numbers, and stop if the logs point elsewhere. A current Windows build with no Event ID 2011 is a reason to reassess the diagnosis rather than escalate the number.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsInvestigate security and filter software
Older Microsoft-hosted answers associate this symptom with antivirus products, including historical Norton releases. Check the date of the last security-product update and review its logs for file-system or network-filter events. Apply current vendor updates and use the vendor’s documented exclusions or compatibility procedure. Do not leave protection disabled; if a brief test is unavoidable, perform it locally, for the shortest possible time, with other safeguards in place.
Check SMB compatibility and security policy
- Verify that a firewall permits TCP 445 between client and host.
- Check authentication, stored credentials, share permissions, and NTFS permissions.
- Review SMB signing requirements and guest-access policy when only certain clients fail.
- Consider whether an obsolete client or appliance requires an older SMB dialect.
Microsoft’s current SMB guidance explains protocol configuration and the security risks of SMBv1: SMBv1, SMBv2, and SMBv3 troubleshooting. Do not enable SMBv1 as a routine fix. It should be considered only for a documented, unavoidable legacy dependency, with isolation and a replacement plan. SMB signing controls are described in Microsoft’s SMB signing overview.
Account for non-Windows hosts
If the share is on a NAS, Linux/Samba server, macOS computer, or third-party appliance, troubleshoot that platform’s SMB service, firmware, logs, authentication, and resource limits. The Windows LanmanServer registry path cannot repair a server that does not run that service.
Rank #4
- Direct-attached storage device via USB Type-C for Windows, macOS and Linux
- Use the TR-004 as external storage for NAS backup
- Expand the capacity of your QNAP NAS
- 4 x 3.5-inch SATA 3Gb/s (Diskless)
- Hardware RAID supports RAID 0, 1, 5, JBOD, and individual disks
Review other host logs
Search for disk, NTFS, memory, service, and filter-driver errors around the same time. A reboot that helps only temporarily can indicate a resource leak or driver problem rather than a permanently correct registry value.
Undo the change
If IRPStackSize did not exist before the test, you can delete only that value, then restart and retest. If it existed, restore the exported key instead:
- In Registry Editor, choose File > Import and select the saved
LanmanServer-Parameters.regfile, or restore it with your approved recovery process. - Restart the host.
- Confirm that the original share behavior and other Server-service settings are intact.
Do not delete unrelated values from the LanmanServer key.
When to escalate
- The host is a domain controller, cluster node, highly available file server, or production system.
- Several clients are affected or the issue returns after every reboot.
- System logs contain additional
Srv, disk, NTFS, memory, or filter-driver errors. - The share is supplied by a NAS or another vendor’s SMB implementation.
- Group Policy or device management controls the setting.
- You cannot safely back up or restore the registry.
- The problem began immediately after a Windows or security-product update.
In those cases, preserve the event logs, exact UNC path, affected clients, recent changes, and test results for the administrator or vendor.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
