Printable checklist

How to Fix Windows 11 Paging File Using Too Much Disk (pagefile.sys)

pagefile.sys grows when committed memory approaches the system limit, so a large paging file is usually a sign of RAM pressure or a memory leak rather than a broken file. Check the commit figure in Task Manager, then set a sensible custom size or move the paging file to a faster drive. Reducing leaks and adding RAM keeps disk activity low over the long term. This illustrated guide covers 3 methods and 22 steps, with a separate picture for every step.

By Co-authored by 52runoob Editorial Team · 22 steps · Performance & Speed · Updated November 21, 2026

Back to the guide
  1. 1. Open Task Manager

    Open Task Manager and switch to the Performance tab for memory details.

  2. 2. Read commit and limit

    Note the commit value and total commit limit shown under memory.

  3. 3. Check disk activity

    Look at the disk usage figure to see if paging is saturating the drive.

  4. 4. Add commit size column

    In the Details tab, add the commit size column to sort processes by reserved memory.

  5. 5. Find the top consumer

    Identify the process with the largest commit size that is driving paging.

  6. 6. Watch over time

    Leave Task Manager open and see whether commit keeps climbing during normal use.

  7. 7. Note the peak commit

    Write down the highest commit figure reached during a busy session for later comparison.

  8. 8. Open system properties

    Search for advanced system settings and open the performance section.

  9. 9. Open virtual memory

    Choose to change virtual memory from the Advanced tab of Performance Options.

  10. 10. Disable automatic management

    Clear the option to manage all paging files automatically so you can set a custom size.

  11. 11. Set initial and maximum

    Enter an initial size and a realistic maximum based on your peak commit figure.

  12. 12. Choose the drive

    Select a faster or less full drive for the paging file if appropriate.

  13. 13. Apply and restart

    Confirm the settings and restart so the new paging file size takes effect.

  14. 14. Check free space on the target drive

    Verify the drive you picked has enough free room to hold the paging file.

  15. 15. Let Windows manage the other drive

    Keep a small system-managed paging file on the system drive for crash dumps.

  16. 16. Reapply and restart

    Confirm the changes and restart so the relocated paging file becomes active.

  17. 17. Close heavy applications

    Close programs you are not using to lower committed memory immediately.

  18. 18. Fix the leaking app

    Update or reinstall the application whose commit size keeps growing.

  19. 19. Update device drivers

    Install optional driver updates through Windows Update for chipset and storage.

  20. 20. Free drive space

    Run storage cleanup so the drive has room for the paging file to grow.

  21. 21. Install more RAM

    Add a compatible memory module if commit regularly approaches the limit.

  22. 22. Verify the result

    Recheck commit and disk usage in Task Manager after the changes.