Movian SecurityVirtual memory settings for better Windows performance
Virtual memory settings affect how Windows responds when applications need more working memory than the installed RAM can provide. Windows places less-active pages in a reserved file on a storage drive, usually called the page file. This paging process protects stability, although it cannot make a computer feel as quick as having enough physical memory.
On most Windows 10 and 11 PCs, automatic management is the safest starting point. That matters in Australia, where an older family desktop in Brisbane may sit beside a newer Windows 11 laptop bought from JB Hi-Fi. Australians often describe RAM in gigs, but a larger number does not remove the need for sensible virtual memory configuration.
Virtual memory becomes noticeable when Outlook, browser tabs, photo editing and streaming tools compete with the operating system. A fast SSD makes paging far less disruptive than paging on a hard drive, yet excessive reads can still cause stuttering. The page file also raises the system’s commit limit, which is the amount of virtual memory Windows backs with RAM and page-file space.
Tuning should follow measurement rather than folklore. A small business in Canberra may run accounting, cloud accounting and remote-support tools on one Windows PC, while a gamer in Melbourne may create much heavier memory peaks. Record the symptoms, back up important files and check whether the bottleneck is actually memory pressure, startup activity, storage health or malware before changing any setting.
| Setting | Best fit | Expected effect | Main risk |
|---|---|---|---|
| System managed | Most Windows PCs | Windows adjusts the page file as memory and drive conditions change | Occasional resizing may cause brief disk activity |
| Custom size | Measured specialist workloads | Provides predictable capacity for known memory peaks | Poorly chosen limits can cause allocation failures |
| No paging file | Rare, specialist setups only | Reclaims reserved storage and removes paging | Reduces commit capacity and removes stability headroom |
What virtual memory actually does
RAM holds data that applications are actively using. When demand rises, Windows can page selected memory pages out to disk and bring them back when required. A committed page needs page-file backing, subject to the system commit limit. This distinction remains useful in a broader computing context: paging is general, while pagefile.sys and the Windows controls are platform-specific.
The page file is normally stored invisibly on the Windows system drive, although its location can be changed on most installations. Its input and output remains much slower than RAM, so a workload that constantly crosses that boundary will stay slow. Virtual memory is therefore a capacity and stability tool, not a substitute for physical memory or a well-maintained SSD.
When automatic management is the right choice
Let Windows manage the file when the PC is stable, the system drive has reasonable free space and applications do not report memory-allocation errors. Windows sizes the file according to installed memory, available drive capacity and commit demand. Automatic management also avoids fragile values that may look precise but become wrong after an application update or a RAM upgrade.
Changing to a custom range rarely improves ordinary office use and can reduce reliability if the maximum is too small. It makes more sense for a specialist workstation, a controlled server-like environment or troubleshooting where known peaks must be satisfied. Even then, recheck the figures after major software changes, and do not move the file merely to free a few gigabytes.
Find the real bottleneck before changing settings
Open Task Manager and inspect Performance, then Memory. Compare In use, Available and Committed during the slow period; the committed figure includes memory-backed allocations and can exceed installed RAM. Resource Monitor can reveal which processes are committing memory. If pressure stays low, virtual memory tuning is unlikely to solve the lag.
Also check the system drive and the Performance tab’s disk and CPU graphs. Leave ample free space, commonly around 15–20 per cent, so the page file can expand and Windows does not struggle with temporary writes. During hot Australian summers, dust-restricted airflow and fan problems can also imitate a memory problem, particularly in older desktops.
If applications routinely exceed the available RAM, add capacity using modules matched for the motherboard, CPU and computer’s form factor. A matched dual-channel kit can improve memory bandwidth as well as capacity. Whether the machine came from a major Australian retailer or a local repair shop, return virtual memory to system managed after upgrading the RAM and then retest the workload.
Change the Windows page file safely
In Windows 11, press the Windows key, open Settings, choose System, then About and Advanced system settings. Under Performance, select Settings, open the Advanced tab and choose Virtual memory. Click Change to edit the drive, initial size and maximum size. Windows 10 uses the equivalent route through Control Panel, System and Security, System, Advanced system settings and Performance.
Before confirming a custom value, create a backup of important documents and use System Restore where practical. Do not clear both size boxes when choosing automatic management, and never set the maximum below the initial size. Restart Windows after applying a change. The restart confirms that the new configuration loaded and avoids judging performance during the installation activity that may immediately follow.
Updates can complicate any performance test. If the Settings route is unavailable because an installation is looping, use the fixing the windows update stuck at checking for updates loop notes guidance to restore normal servicing before tuning virtual memory. A page-file adjustment cannot repair a damaged update component, failing system file or incompatible driver.
Choose a custom size for demanding workloads
Use custom sizing only after recording the highest committed-memory demand during representative work. The initial size should cover normal peaks, while the maximum should leave room for temporary spikes without consuming the whole drive. A useful starting calculation is typical committed use minus installed RAM, followed by additional headroom for the page file.
For example, a 16 GB PC handling office work may begin with a 16–24 GB initial size and a 24–32 GB maximum. Video editing, large datasets or virtual machines may justify a 32–48 GB maximum. These figures are examples rather than guarantees: a 32 GB or 64 GB machine performing the same workload can require a different arrangement, and Windows’ own measurements should guide the final choice.
A page file that is too small can produce out-of-memory messages, failed launches or unstable applications. A maximum set excessively high does not make paging faster and can leave insufficient room for updates, temporary files and personal data. Avoid the No paging file option on everyday PCs because it lowers the commit ceiling and can interfere with features such as hibernation and memory-dump diagnostics.
Verify results and recognise repair needs
After restarting, test a cold boot, open the same applications, reproduce the earlier workload and watch Task Manager for several minutes. Compare responsiveness, memory pressure, disk activity and application errors rather than relying on a synthetic score. One busy disk graph does not prove the page file is faulty; repeated faults during memory spikes are more meaningful.
Restore the previous setting if the PC becomes less stable, and allow normal background maintenance to finish before judging the result. Persistent blue screens, corrupted files, unexplained reboots or a system drive that is nearly full call for broader diagnostics. A page-file adjustment cannot remove malware, repair storage hardware or correct a Windows installation that has already been damaged.
Movian Security can assess Windows performance, detect threats, tune the operating system or advise on suitable RAM and SSD upgrades, with data backed up before invasive work. This repair-led approach remains relevant in Australian cities and regional areas, where computers may combine shop-bought parts with older business equipment. Any repairer copying a drive should explain its handling, retention and privacy under the Australian Privacy Act, especially when it contains client records. Stable virtual memory preserves room to operate, but it works best alongside measured memory use, free storage and a clean Windows installation.