Fix ERROR_PAGEFILE_QUOTA (0X000005AE) – 3 Steps

You're staring at ERROR_PAGEFILE_QUOTA (0X000005AE) and your app just crashed. I know this error is infuriating – it's vague, and the first time I hit it on a Windows Server 2019 box, I spent an hour digging through event logs before realizing the fix was embarrassingly simple.

The error means that a process tried to commit more memory than the pagefile allows it to use. This isn't a memory leak or a hardware issue. It's a quota thing – Windows sets a limit on how much virtual memory each process can lock down, and you've blown past it.

Here's the thing: this error shows up in two common scenarios. One, you're running a backup or indexing tool that's eating memory like candy. Two, you're on a Terminal Server or RDS host where multiple users are hammering the same pagefile. Either way, the fix is the same logic: free up headroom, then grow the pagefile.

Step 1: The 30-Second Fix – Kill the Hungry Process

Before you touch any settings, check if a single process is hogging all your pagefile quota. Open Task Manager (Ctrl+Shift+Esc), click the Details tab, then sort by Commit size (if you don't see that column, right-click the headers and add it).

Look for something that's using more than a few gigabytes. Common culprits: sqlservr.exe, backup.exe, w3wp.exe (if you're on IIS), or even a runaway svchost.exe.

If you find a clear hog, right-click it and End task. That's it. The error should clear instantly. If your app crashes again, move to Step 2.

One quick note: if you're on a production server, don't kill random processes without checking what they are. A quick tasklist /svc in the command prompt shows you which service owns each process.

Step 2: The 5-Minute Fix – Adjust the Pagefile Size

If killing processes doesn't help, it's time to look at your pagefile configuration. By default, Windows manages the pagefile automatically, but that default is often too small on servers with lots of RAM. The error appears when the system can't grow the pagefile fast enough to meet demand.

Here's how to fix it:

Open System Properties – press Win + Pause/Break or right-click This PC and select Properties.
Click Advanced system settings on the left.
Under Performance, click Settings.
Go to the Advanced tab, then under Virtual memory, click Change.
Uncheck Automatically manage paging file size for all drives.
Select your system drive (usually C:), then choose Custom size.
Set Initial size to 1.5 times your RAM (e.g., 16384 MB for 16 GB RAM) and Maximum size to 3 times your RAM.
Click Set, then OK, and restart.

This is what fixed it for me on a Windows Server 2019 box running SQL Server 2017. The default pagefile was 4 GB, but SQL Server wanted more. After bumping it to 24 GB initial, the error vanished.

Worth noting: if you have multiple drives, put the pagefile on the fastest drive – not the system drive – for extra performance. But don't scatter it across drives; that can slow things down.

Step 3: The 15+ Minute Fix – Disable Pagefile Quota Enforcement

If you've done Steps 1 and 2 and still see the error, you're dealing with a quota enforcement issue. This happens when a service or driver sets a specific pagefile quota for itself, and that quota is too low. The real fix is to disable quota enforcement for that process.

You can do this via the registry, but be careful – this is a system-wide change that affects all processes. Here's the path:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

Create a new DWORD (32-bit) value called DisablePagingExecutiveQuota and set it to 1. This tells Windows to ignore pagefile quotas for all processes. Restart your server for the change to take effect.

I've only needed this on one occasion – a custom backup agent that had a hardcoded quota. If you're running third-party software that triggers this persistently, contact the vendor first. Disabling quotas globally can lead to other issues, like a single process consuming all your virtual memory and causing system instability.

If the registry edit doesn't work, one more thing to check: make sure your system drive has enough free space for the pagefile to grow. If you're running low on disk, Windows may fail to expand the pagefile, and you'll get this error even with correct settings. Aim for at least 20% free space on the drive where the pagefile lives.

When to Call It a Day

Most people will be fixed by Step 1 or Step 2. I'd say 80% of the time, it's a runaway process or a too-small pagefile. Only in rare cases do you need the registry tweak.

If you're still stuck after Step 3, check your event logs under Windows Logs > System for source Ntfs or Kernel-Paging – they might point to a specific driver or program. And if you're running a hypervisor-based backup or a memory-heavy app, consider moving it to a machine with more RAM. Sometimes the best fix is just throwing hardware at the problem.

Got questions? Drop them below – I try to answer every comment within a day. And if this saved your afternoon, pass it along to whoever's stuck next.