High memory usage in Windows 11
Distinguish normal caching from a memory leak or insufficient RAM.
- Updated
- September 3, 2026
- Reading time
- 7 min read
- Windows support
- Windows 11 · Windows 10
Quick diagnosis
Distinguish normal caching from a memory leak or insufficient RAM. The key distinction is whether “Memory stays near capacity” occurs by itself or together with “apps reload or disk thrashes.” That difference helps separate many apps from application leak.
Symptoms
- Memory stays near capacity
- Apps reload or disk thrashes
Likely causes
- Many apps
- Application leak
- Too little RAM
Quick reversible checks
- Sort Task Manager by Memory
- Close one app normally
Establish the scope
Confirm when memory stays near capacity and whether apps reload or disk thrashes. Note the exact time and the last relevant change, then compare the closest known-good device, account, connection, or application using the same task.
Apply the safer fix first
Review Processes and Performance > Memory, including committed memory. Cached memory is reusable and is not alone a fault.
- Record the current state related to sort task manager by memory.
- Apply the narrow change, then check whether memory stays near capacity.
- Continue only if the result still points toward application leak.
Investigate the cause
Update a process whose use grows after restart. Keep the page file system-managed unless a documented workload says otherwise.
Protect the recovery path
Before work that could affect performance, protect relevant files and sign-in or recovery credentials. Keep the original error wording and the results involving many apps, application leak, too little ram for support.
Verification
- Repeat the affected task under the same conditions used to confirm memory stays near capacity. Confirm the symptom is gone, not merely that a Windows status label changed.
- Repeat the relevant connection, startup, sign-in, sleep, application, or device transition and specifically check whether apps reload or disk thrashes.
When to stop
Do not continue with broader resets when memory errors, crashes, or use grows without bound after clean startup. Preserve the observations already collected and use the device maker, network administrator, Microsoft support, a qualified repair technician, or data-recovery help according to the evidence.
Review the safe troubleshooting workflow before any broader recovery step.