How to Fix High RAM Usage in Windows 10 and Windows 11

Introduction

High RAM usage is one of the most common complaints from Windows users. You open Task Manager, see memory sitting at 85, 90, or even 98 percent, and the system starts to stutter. Applications take seconds to respond, alt-tabbing feels sluggish, and the hard drive light stays on because Windows is constantly paging data to disk. Whether you run Windows 10 or Windows 11, the symptoms and the fixes are largely the same, though a few tools and menus have moved between versions.

This guide covers How to Fix High RAM Usage in Windows 10 and Windows 11 in practical, step-by-step detail. It is written for two audiences at once: home users who just want their computer to feel fast again, and IT administrators who need a repeatable process they can document, script, or push through group policy. We will look at identifying what is actually consuming memory, stopping memory leaks, tuning virtual memory and startup items, and understanding when the real problem is simply that the machine does not have enough physical RAM for its workload.

Before going further, it helps to understand what normal looks like. A freshly booted Windows 10 machine typically idles between 1.5 GB and 2.5 GB of RAM used. Windows 11 often idles slightly higher, around 2 GB to 3 GB, because of additional services, widgets, and the redesigned shell. Browsers are the biggest variable: a single Chrome or Edge window with a dozen tabs can consume 1 GB to 3 GB by itself. That is not a leak, it is normal behavior, but it still pushes smaller systems into trouble. The goal of this guide is to separate the normal from the abnormal and fix the abnormal.

Prerequisites

Before you change any settings, confirm that you have the right access and information. Most of the steps below require an account with administrative privileges. If you are working on a managed corporate device, some options may be greyed out by group policy, and you should coordinate with your IT department rather than fighting the controls.

• Administrator access. You need an account in the local Administrators group to change virtual memory, disable services, and edit startup items.
• Windows edition and build. Run winver from the Run dialog to note your exact version and build number. Windows 10 and Windows 11 differ in where some settings live.
• Hardware architecture. Always verify software compatibility with your hardware architecture (ARM64 vs x86). Memory diagnostic tools, monitoring utilities, and driver updates must match your processor type, or they may install incorrectly or fail to run.
• Free disk space. If your drive is nearly full, Windows cannot manage the paging file properly, and memory pressure gets worse. Keep at least 10 to 15 percent of the system drive free.
• A backup or restore point. Create a System Restore point before making broad changes so you can roll back if performance degrades.

No prior Linux experience is required for anything in this guide. All commands are native Windows tools such as Task Manager, Resource Monitor, PowerShell, and the built-in Command Prompt. If you have used a terminal before, the PowerShell sections will feel familiar, but every step can also be completed with the graphical interface.

Preparation

Preparation is where most people skip ahead and later wonder why a fix did not stick. Keeping your operating system updated before installation prevents dependency conflicts, and the same logic applies to drivers and firmware. An outdated chipset or GPU driver can cause memory to be held and never released, which looks exactly like a leak.

Work through these preparation tasks first:

• Update Windows. Go to Settings, then Windows Update, and install all pending updates, including optional driver updates. Restart when prompted.
• Update your browser. Chrome, Edge, and Firefox ship memory fixes regularly. An outdated browser is a frequent culprit.
• Close unnecessary programs. Save your work and close everything you can before collecting a baseline measurement.
• Record a baseline. Open Task Manager with Ctrl+Shift+Esc, go to the Performance tab, and note the memory usage percentage and the total installed RAM. This number is your reference point.
• Check architecture. In Settings, under System and About, confirm whether your device is x64, ARM64, or x86. This matters when downloading diagnostic or cleanup utilities.

If you manage multiple machines, standardize the baseline measurement. A short PowerShell snippet run as administrator gives a quick snapshot you can log:

• Get-CimInstance Win32_OperatingSystem | Select-Object TotalVisibleMemorySize, FreePhysicalMemory

The values are returned in kilobytes. Divide by 1,048,576 to convert to gigabytes. Recording this before and after your fixes gives you objective evidence that the changes worked.

Installation Steps

Step 1: Review prerequisites and compatibility

Begin by confirming that you meet every item in the prerequisites section. Check your administrator rights, capture your Windows build with winver, and confirm your processor architecture. If you plan to install a third-party memory monitor or a driver update utility, verify that a build exists for your architecture, since an x86 installer on an ARM64 device will either fail or run under emulation, which defeats the purpose. Also confirm that your system firmware and Windows updates are current, because dependency conflicts during a cleanup or driver installation are far more likely on an unpatched system.

Step 2: Prepare the environment

Now create a clean slate for diagnosis. Close all non-essential programs, disconnect from VPNs if they are not needed, and create a System Restore point. Open Task Manager and let it run for a few minutes at idle without touching the machine. This tells you what the background baseline actually is. If idle usage is already above 60 percent with nothing open, the problem is services, startup apps, or a background process, not your normal workload. If idle usage is low but climbs steadily the longer you use the machine, you are likely dealing with a memory leak.

Step 3: Configure core settings

This is the heart of the fix. Work through the following configuration changes in order, testing after each one.

• Identify the top consumers. In Task Manager, click the Memory column header to sort descending. Expand browser entries to see individual tabs and extensions.
• Investigate suspicious processes. Right-click a high-usage process and choose Search online, or open the Details tab and compare the process name against known entries. Resource Monitor, opened from the Performance tab, shows memory commit and hard faults per process.
• Trim startup programs. Go to Settings, Apps, Startup, and disable anything you do not need at boot. On Windows 10 the path is Settings, Apps, Startup; on Windows 11 it is Settings, Apps, Startup as well, with the same toggle behavior.
• Disable unnecessary background apps. In Settings, Privacy, Background apps, switch off apps you do not need running when not in focus.
• Adjust virtual memory. Open System Properties, Advanced, Performance Settings, Advanced, Virtual Memory, Change. If your drive is an SSD with plenty of space, letting Windows manage the paging file automatically is usually best. If you have disabled it in the past, re-enable it, because some applications fail or behave badly without a paging file.
• Review services. Type services.msc in the Run dialog. Look for third-party services you no longer use, such as old printer utilities, cloud sync clients, or security tools from uninstalled software. Set them to Manual rather than Disabled if you are unsure.
• Run memory diagnostics. Type mdsched.exe and choose to restart and check for problems. This rules out failing physical RAM, which can manifest as rising usage and system instability.

If you are comfortable with PowerShell, you can list startup impact and top memory processes in a single pass. Start PowerShell as administrator and run commands such as Get-Process | Sort-Object WorkingSet64 -Descending | Select-Object -First 15 to see the fifteen largest processes by memory. This is faster than clicking through the GUI on multiple machines and produces output you can paste into a ticket.

Step 4: Run the main installation procedure

In this guide, the “installation” is the application of the fixes themselves. Run them as a sequenced procedure rather than all at once, so you can attribute any improvement or regression to a specific change.

• Apply the startup and background app changes from Step 3.
• Restart the computer and re-measure idle memory usage.
• Update or roll back the GPU driver, since graphics drivers are a common source of non-released memory. Use Device Manager, Display adapters, right-click, Update driver, or download directly from the vendor. Match the package to your architecture.
• Uninstall unused applications through Settings, Apps, Installed apps. Pay attention to utilities that run at startup or inject into other processes.
• Scan for malware with Windows Security or your managed endpoint tool. Some unwanted programs consume memory continuously and hide from casual inspection.
• If leaks persist, use Windows Performance Recorder or Resource Monitor to capture a short trace while reproducing the problem, then examine which process grows over time.

For administrators, this sequence can be packaged as a script that reports baseline usage, disables a defined list of startup entries, rechecks usage, and writes results to a log file for compliance records.

Step 5: Verify the installation

Verification is simple but must be done consistently. Restart the machine, let it idle for ten minutes, and record memory usage again. Compare against your baseline. A healthy outcome is idle usage that drops by at least 15 to 25 percent on a machine that was previously bloated, or memory that stays flat instead of climbing during a normal work session.

• Confirm idle usage is stable over 30 minutes.
• Open your usual set of applications and watch whether usage plateaus or keeps rising.
• Check that no previously working application now fails to launch, which can happen if you disabled a required service.
• Review the Windows Event Viewer under Windows Logs, System for recurring errors related to memory or drivers.

Step 6: Configure post-install options