Error: Insufficient resources to perform operation or The message file cannot be created Affects: Windows 10 22H2 ESU, Windows Server 2019, Windows Server 2016 Time: 10-15 minutes
Quick Fix
Download and install the out-of-band patch KB5074976 from the Microsoft Update Catalog:
https://www.catalog.update.microsoft.com/Search.aspx?q=KB5074976This patch is not delivered through Windows Update automatically. You must download and install it manually.
Step-by-Step
Step 1: Confirm the Issue
Check if MSMQ queues are inactive or if IIS applications are throwing 500 errors related to messaging.
Get-Service msmq | Select-Object Status, StartType
Get-WmiObject Win32_PerfFormattedData_msmq_MSMQService | Select-Object *Look for inactive queues or services that fail to start.
Step 2: Identify the Problematic Update
Confirm KB5071546 (Windows 10), KB5071544 (Server 2019), or KB5071543 (Server 2016) is installed:
Get-HotFix | Where-Object {$_.HotFixID -match "KB507154"} | Format-Table HotFixID, InstalledOnStep 3: Download KB5074976
Visit the Microsoft Update Catalog and download the correct version for your OS:
- Windows 10 22H2 x64: KB5074976
- Windows 10 21H2 x64: KB5074976
Select the appropriate architecture (x64 or ARM64) and download the .msu file.
Step 4: Install the Patch
Run the installer from an elevated command prompt:
wusa.exe "C:\path\to\windows10.0-kb5074976-x64.msu" /quiet /norestartStep 5: Restart and Verify
Restart-Computer -ForceAfter reboot, confirm MSMQ is operational:
Get-Service msmq
Get-MsmqQueue | Select-Object QueueName, MessageCountWhy This Happens
The December 2025 security updates (KB5071546, KB5071544, KB5071543) modified NTFS permissions on the MSMQ storage folder at C:\Windows\System32\msmq\storage. The update tightened the security model, which inadvertently removed write access for service accounts like NetworkService, LocalService, and IIS app pool identities.
When these accounts attempt to create or write .mq message files, MSMQ returns misleading "insufficient resources" or "insufficient disk space" errors, even when plenty of storage is available.
Microsoft acknowledged the issue on December 15, 2025 and released the emergency out-of-band patch KB5074976 on December 18-19, 2025.
Alternative Solutions
Option A: Rollback the December Update
If you cannot install KB5074976 immediately, roll back the problematic update:
wusa.exe /uninstall /kb:5071546 /quiet /norestartNote: This removes security fixes and should only be a temporary measure.
Option B: Manual Permission Fix (Temporary)
Grant explicit write permissions to the MSMQ storage folder for the affected service account:
$acl = Get-Acl "C:\Windows\System32\msmq\storage"
$rule = New-Object System.Security.AccessControl.FileSystemAccessRule("NETWORK SERVICE","FullControl","ContainerInherit,ObjectInherit","None","Allow")
$acl.SetAccessRule($rule)
Set-Acl "C:\Windows\System32\msmq\storage" $aclThis is not recommended as a permanent fix. Install KB5074976 as soon as possible.
Affected Systems
| Platform | Problematic KB | Fix KB |
|---|---|---|
| Windows 10 22H2 ESU | KB5071546 | KB5074976 |
| Windows Server 2019 | KB5071544 | KB5074975 |
| Windows Server 2016 | KB5071543 | KB5074974 |
Home and Pro users on personal devices are unlikely to encounter this issue. MSMQ is primarily used in enterprise and server environments.

