Paging file size is managed by Windows automatically, and Microsoft’s own fix for “insufficient virtual memory” errors is to switch that automatic setting back on, not to type in a bigger number. Change it by hand only when an app’s documentation or a specific memory error asks for it. The setting lives in System Properties, which you open by searching for sysdm.cpl, and you need to be signed in as an administrator.
Which situation are you in?
Start with the reason you are here. Most people who search for this have one of the four situations below, and only some of them are a real case for a custom size.
| Your situation | What to do |
|---|---|
| Windows or Windows Update reports low or insufficient virtual memory | Make sure automatic management is on (see “Windows Update or Windows reports low virtual memory” below). Microsoft lists a manually configured page file as one cause of these errors. |
| An app’s installation notes ask for a page file of a certain size | Set a custom size that meets the app’s stated requirement. |
| You need a complete memory dump after a crash, for example for a support case | The page file (or a dedicated dump file) must be big enough to hold the dump. Microsoft’s minimum for a complete dump is 1 x RAM plus 257 MB. |
| The PC just feels slow | Leave the page file alone. Find out what is using memory first: see ways to lower RAM usage in Windows 11. |
How Windows decides the page file size
Virtual memory in Windows is backed by the page file, pagefile.sys. Microsoft describes it as “an optional, hidden system file on a hard disk.” When the memory that apps have asked for gets close to what RAM can hold, Windows can move pages of data that are not in active use out to this file and bring them back when they are needed.
Microsoft describes the reason to size a page file as “supporting a system crash dump, if it’s necessary, or extending the system commit limit, if it’s necessary,” not as a speed setting. The commit limit is “the sum of physical memory and all page files combined,” and if the system commit charge reaches that limit, Microsoft warns that processes “might not get committed memory,” which “can cause freezing, crashing, and other malfunctions.”
Microsoft’s documentation says that “by default, page files are system-managed.” In that mode Windows grows the file when needed. According to Microsoft, a system-managed page file can grow up to three times the physical memory or 4 GB, whichever is larger, but no more than one-eighth of the volume size, and only if enough free disk space is available.
That three-times figure describes how far Windows lets its own file grow. It is not a size Microsoft tells you to type in, and Microsoft does not publish a formula for custom sizes. Microsoft also notes that some products or services require a page file and that you should check the product documentation for those.
Virtual memory is also not video memory. The VRAM a graphics card or integrated GPU uses for games is a separate thing, and the page file setting does not change it.
Windows Update or Windows reports low virtual memory
Microsoft’s documented fix for Windows Update errors 0x8007000e and 0x800705aa (insufficient virtual memory) is to let Windows manage the page file, and it is the right setting for most PCs. Sign in with an administrator account. Then:
- Select Search on the taskbar, type
sysdm.cpl, and open the result. The System Properties window appears. - Select the Advanced tab, and under Performance, select Settings.
- In Performance Options, select the Advanced tab, then under Virtual memory, select Change. The Virtual Memory window lists each drive with its current page file setting, and near the bottom it shows the currently allocated total.
- Make sure Automatically manage paging file size for all drives is selected.
- Select OK, then OK again to close Performance Options and System Properties.
- Restart the computer.
Microsoft lists third-party apps that consume lots of virtual memory as the other common cause, and a system-managed page file can only grow when enough free disk space is available. Check free space on the Windows drive and see the last section below.
An app’s documentation names a page file size
Use this only for a documented requirement, such as an app’s stated page file size. Microsoft does not document a general rule such as a multiple of your RAM, so do not pick a number from a chart.
- Open the Virtual Memory window as in the previous section (steps 1 to 3).
- Clear the Automatically manage paging file size for all drives check box.
- Select the Windows drive (usually C:) in the drive list.
- Choose the custom size option, then type an initial size and a maximum size in megabytes (1 GB is 1,024 MB). Use the value from the app’s documentation, or at least the crash dump minimum if a dump is the reason.
- Select the button that sets the size for that drive, check that the drive list shows the new values, then select OK.
- Close the remaining windows and restart the computer so the new size takes effect.
You need a complete memory dump after a crash
If a support case asks for a complete memory dump, the page file on the Windows drive (or a dedicated dump file) has to be big enough to hold it. Microsoft’s minimum for a complete memory dump is 1 x RAM plus 257 MB; set at least that with the custom size steps above.
Keep a page file on the Windows drive. If no page file or dedicated dump file is large enough, Microsoft states that a system memory dump file is not created after a crash, which makes a blue screen much harder to diagnose. Choosing to remove the page file is not covered here for that reason.
Reading the commit charge in Task Manager
After the restart, open the Virtual Memory window again. The drive list and the “currently allocated” figure should match what you set. To see how close you are to the limit, open Task Manager (Ctrl + Shift + Esc), go to Performance, and select Memory: Microsoft notes that the system commit charge and commit limit can be measured on this tab. If the committed figure stays well below the limit in normal use, the size is more than enough.
To undo a custom size at any time, select Automatically manage paging file size for all drives again as in “Windows Update or Windows reports low virtual memory,” select OK, and restart.
Leaks, full drives and a full RAM
- Memory use that keeps climbing while you do nothing new points to a leaking app, not a small page file: find and fix a memory leak in Windows 11.
- If memory use is near the commit limit during your normal work, the PC simply needs more memory than it has; adding RAM is a hardware question for the PC maker.
- Defragmenting does not change virtual memory, although a hard disk that has not been optimized in a long time can be checked with the Windows 11 defrag and optimize tool.
Page file answers
Do I need an administrator account?
Yes. Microsoft’s troubleshooting page for these errors has you sign in to the affected computer as an administrator, and the page file is a setting for the whole PC. If you use a work or school PC without administrator rights, ask whoever manages it.
Why can’t I see pagefile.sys in File Explorer?
Microsoft describes it as a hidden system file, so File Explorer does not show it with the default view settings. You do not need to touch the file itself; all changes go through the Virtual Memory window.
For the full background, Microsoft’s introduction to the page file and its article on determining the page file size for 64-bit Windows explain the sizing rules, and its insufficient virtual memory troubleshooting page has the steps used above.

Kermit Matthews runs Live2Tech from just outside Philadelphia. He is an IT specialist with over 20 years of experience, from a university help desk to small-business IT, IT management and his own consulting practice, and has written tech guides full time since 2020. Steps are checked against the current software on a real device or the maker’s official documentation. More about Kermit.