Last updated on November 20th, 2026 at 08:27 am
Seeing a low-on-memory warning, or an app that asks for a bigger paging file? Before changing anything, know that Windows 11 sizes the paging file itself, and that setting suits most PCs. If you do need manual control, search for View advanced system settings and go to Performance Settings > Advanced > Virtual memory > Change. Whatever you set takes effect after a restart.
Applies to: Windows 11 24H2 and later (25H2, 26H2). You need an administrator account.
When the warning appears: decide whether to change anything
The paging file (pagefile.sys, usually on C:) is disk space Windows uses alongside RAM. Together they set the commit limit, the total memory Windows can promise to apps. A warning that the PC is low on memory means apps asked for close to that limit.
A manual change is worth it in only a few cases:
- Someone set a small custom size earlier, and the warnings started after that.
- An app’s vendor or a support technician gives a minimum paging file size.
- You need a complete memory dump to diagnose blue screens.
- C: is nearly full and a second internal drive has room.
If none of those apply, the fix is usually elsewhere: an app using too much memory, too much running at startup, or too little RAM. Skip to the section on when the paging file isn’t the problem.
Measure first: how much paging file you actually use
A number beats a guess. Open PowerShell (right-click Start and choose Terminal) and run:
Get-CimInstance -ClassName Win32_PageFileUsage | Select-Object Name, AllocatedBaseSize, CurrentUsage, PeakUsage
All three figures are in megabytes. AllocatedBaseSize is the space set aside, CurrentUsage is what’s in use now, and PeakUsage is the highest use since the PC started. Check it after a heavy work session, for a few days. If the peak stays well under the allocated size, a bigger file won’t fix anything.
Choose a setup that fits your situation
| Situation | Setting to use |
|---|---|
| No specific requirement | Automatically manage paging file size for all drives (the default) |
| One drive should hold the file, size left to Windows | System managed size on that drive |
| An app, vendor or complete dump needs a minimum | Custom size with that minimum as the initial size |
| Lots of RAM and you want no paging file | Not recommended: the commit limit drops to RAM alone, some apps expect a paging file, and crash dumps may not be saved |
Set a custom size in the Virtual Memory window
- Select Search on the taskbar, type advanced system, and open View advanced system settings. System Properties opens on the Advanced tab. If Search doesn’t show it, open Settings > System > About and select Advanced system settings under Related links.
- Under Performance, select Settings.
- In Performance Options, open the Advanced tab and select Change under Virtual memory.
- Clear Automatically manage paging file size for all drives. The drive list and size options become available.
- Select the drive, usually C:.
- Choose Custom size and type an Initial size and a Maximum size in MB. Or choose System managed size to let Windows size only this drive.
- Select Set. Without this step, OK saves nothing for that drive.
- Select OK in each window, then restart from Start > Power > Restart.

If the size boxes stay gray, the automatic check box at the top is still selected. If Windows refuses a size, the drive lacks the free space; lower the maximum, or free up disk space in Windows 11 first.
Work out the numbers
The window takes megabytes, and 1 GB is 1,024 MB. Three worked examples:
- Vendor minimum. Alex’s video software asks for a 16 GB paging file. 16 x 1,024 = 16,384 MB, so the initial size is 16384. A maximum somewhat higher, such as 20480, leaves room to grow.
- Complete memory dump. Microsoft says this needs a paging file of at least RAM plus 257 MB (on a local drive). On a PC with 16 GB of RAM: 16,384 + 257 = 16,641 MB.
- Small memory dump. The minimum is only 1 MB, so crash dumps alone are no reason for a huge file.
You’ll still see the 1.5x to 3x RAM rule in older advice. Microsoft’s page file sizing article gives no fixed multiple; it ties size to peak memory use and dump settings. For comparison, this is what Windows does with a system-managed file:
| Item | How Windows sizes it |
|---|---|
| Minimum | Varies with past use, RAM divided by 8 (up to 32 GB) and crash dump settings |
| Maximum | 3 x RAM or 4 GB, whichever is larger, capped at one-eighth of the drive |
| Growth | Grows when commitments reach 90 percent of the commit limit and disk space allows |
To see how much RAM you have before doing the arithmetic, see how to check how much RAM you have on Windows 11.
Put the file on a second drive without losing crash dumps
Use this when C: is short of space and another internal drive has plenty. Open the Virtual Memory window with steps 1 to 4 above.
- Select the second drive, choose System managed size, and select Set.
- Select C:, then decide: choose No paging file to move it fully, or a small Custom size to keep some on C:. Select Set.
- Select OK and restart.
The catch is crash dumps. Microsoft’s crash dump documentation ties at least the small dump to a paging file on the boot drive, so with no file on C:, a blue screen may leave nothing to analyze. If you ever check crash logs on Windows 11, keep a small file on C:. With files on two drives, Microsoft says Windows uses whichever responds first, so the faster SSD naturally does more of the work.
Why old wmic recipes fail now
Many older tutorials change the paging file with wmic commands. Microsoft disabled WMIC by default in Windows 11 23H2 and 24H2, removed it during upgrades to 25H2, and in 2026 removed it from all currently supported Windows 11 versions, as its WMIC removal notice explains. It can’t be added back as an optional feature. WMI itself remains, so PowerShell’s CIM commands still read paging file data, as in the measuring step above. For changes, the Virtual Memory window is the dependable route.
Confirm the result, or put everything back to automatic
After the restart, open the Virtual Memory window again (steps 1 to 3). Each drive’s line shows its paging file setting, and the bottom of the window shows the total. Run the PowerShell command again: AllocatedBaseSize should match what you entered.
To undo everything, select Automatically manage paging file size for all drives, select OK, and restart. That is also the quickest fix if warnings started after a custom change.
When the paging file isn’t the problem
A bigger paging file stops out-of-memory errors; it doesn’t make a PC faster, because storage is far slower than RAM. If the PC is slow all the time:
- Find the app using the most memory in Task Manager and close or update it.
- Trim apps that launch at sign-in; see how to change startup programs in Windows 11.
- Use the safe steps to clear memory on Windows 11.
- If warnings return every day under normal work, more RAM is the real fix.
Graphics memory is separate as well; a game short on video memory needs a different check, covered in how to check VRAM in Windows 11.
Questions people ask after resizing the paging file
Does the new size apply without a restart?
Plan on a restart. Windows creates the paging file at startup, and a smaller size never takes effect until you restart, so restart before you test.
Why did my paging file grow after a crash?
With a system-managed size and the automatic memory dump setting, Windows can raise the file to at least the size of RAM for four weeks after a crash it couldn’t fully record, so the next dump succeeds.
Can I do this on a work or school PC?
Only with administrator rights, and your IT department may manage the setting. Ask them before changing it, since their tools may reset it.
Are the steps the same on Windows 10?
The window is the same, but Windows 10 no longer gets security updates. The older version is covered in changing virtual memory in Windows 10.
If you changed the size only to stop a warning, give the PC a few days of normal use, then run the PowerShell check again to see whether the peak stays below what you set.

Matt Jacobs writes and maintains the guides on Support Your Tech, which he started in 2017. He spent most of his career keeping small-business PCs running and still takes the occasional consulting job, so the steps here come from fixing the same problems on other people’s computers. Each guide follows Microsoft, Apple and Google’s own documentation and is updated when the steps change. Screenshots marked “Recreated” are illustrations of the real screens.