You open Task Manager for the first time, see memory sitting at eighty-something percent, and quietly panic. Then you spend the rest of the evening trying to get it down.
The advice for that search is always the same: close things, disable startup items, clean something. Most of the time there was never anything to fix.
I read the raw counters on this machine while it was doing nothing in particular. Of the memory Windows called available, nearly all of it was already holding data. That is deliberate.
What the percentage in Task Manager counts
The whole confusion comes down to three lines. Empty memory does nothing for you, and RAM that is sitting unused is money you paid for and are not spending.
So Windows fills it deliberately, with copies of files and program code it expects you to want next. That filled memory shows up in the percentage. A high number usually means Windows is caching well, not that you are running out.
Ours: what eighty percent looked like here
Ours, read off an idle machine straight from the performance counters, and the split is the point. This laptop has 15.25 GB usable and reported 2.84 GB available with 398 processes running.
That reads as roughly 81 percent in use, which looks alarming, and it was not. Of that 2.84 GB called available, 2.57 GB was standby cache, which is memory already holding data. The machine had no problem at all.
So genuinely free memory was under 300 MB. Nothing was waiting on anything. Standby is available and busy at the same time. Windows hands it over to your programs the instant one asks, and until then it uses it as a cache.
Available is not free, and that is the whole lesson
Say this bit twice and the panic goes away. Task Manager shows available, not free, and available includes every page Windows can hand over immediately, cached or not.
A system with nothing cached is not a healthy one. It has to fetch everything back off disk while you sit and wait. Ours, and I will stand behind it: chasing a lower percentage only empties the cache.
The machine then gets slower, not faster. If it genuinely feels slow rather than just showing a big number, read a different one. Disk activity is the number that predicts lag.
The number that actually matters
Not the percentage, this one.
Documented by Microsoft in its introduction to the page file:
"The system commit charge is the total committed or 'promised' memory of all committed virtual memory in the system."
Microsoft states what going over it looks like: "If the system commit charge reaches the system commit limit, the system and processes might not get committed memory. This condition can cause freezing, crashing, and other malfunctions."
Documented by Microsoft: the committed charge and limit "can be measured on the Performance tab in Task Manager". It is the line marked Committed under the memory graph, one number over another. That pair is your warning light.
Ours: committed was bigger than the RAM, and nothing was wrong
The reading that catches people out. Ours, measured here at the same moment as everything else: committed memory was 21.21 GB against a limit of 43.01 GB. Read that again.
Committed was 21.21 GB on a machine with 15.25 GB of RAM. That is normal. Committed memory is promised, not occupied. Roughly half the limit was in use, which is the healthy picture.
That healthy picture is invisible if you only ever look at the percentage. Ours: the page file on this machine is 28,432 MB, and its highest recorded usage ever is 283 MB. All that promised memory was never actually needed on disk.
When high memory really is the problem
Three signs say it is real, and none of them is a percentage. Committed creeping towards the limit is one, and that is the condition Microsoft warns causes freezing and crashes.
One process climbing without ever falling back is another. Sort Task Manager by memory and watch the top row for a few minutes rather than a few seconds.
When that top row is Desktop Window Manager and it keeps rising all day, the graphics driver is the usual cause.
If the top row is Windows Push Notifications User Service holding gigabytes, one owner got the memory back with a single folder rename.
Disk pinned high while memory is full is the third, the machine paging rather than caching. Everything else is Windows working. A PC that feels slow usually has a different cause entirely.
What not to do about it
The popular advice that costs you performance starts with memory cleaners. All one does is force programs to drop their cached pages, which they then read back off disk.
Do not disable the page file to save space either. Microsoft's guidance says 100 percent usage of a page file "doesn't indicate a performance problem" while the commit limit is not being reached.
Do not turn off SysMain to fix a high percentage. That service exists to fill memory with what you are about to open. Ours: closing browser tabs beats all three of those, and it reduces real demand rather than hiding it.
If it is genuinely running out
Then the fix is ordinary and it is short. Restart, and look again after ten minutes. A leak shows itself by climbing back up quickly.
Find the process, not the percentage. Task Manager, Details tab, sort by memory, and note what sits at the top over time. Leave the page file on system managed so Windows can raise the commit limit when it needs to.
And if committed genuinely lives near the limit, more memory is the answer. Check whether your laptop can even take it first, because plenty cannot.
If one Windows 11 process, WorkloadsSessionHost, holds gigabytes while you do nothing, the WorkloadsSessionHost page shows how owners freed it.
Status: read against Microsoft's page file and commit charge docs, 26 August 2026, on Windows 11. Every figure came from performance counters on this idle PC. Nothing was changed to get them.
Is 80 percent memory usage bad in Windows 11?
On its own, no. Windows deliberately fills unused memory with cached data, so a high percentage usually means it is caching well.
On the machine measured here, 2.57 GB of the 2.84 GB Windows called available was standby cache. Watch the Committed line in Task Manager instead, because that is the one Microsoft warns about.
Why is my memory usage high when nothing is open?
Because Windows keeps working while you are not. Background services, indexing, security scanning and the cache all use memory by design, and the idle machine tested here still had 398 processes running.
If your percentage is high but the Committed line sits well under its limit, you are fine.
Should I use a memory cleaner or RAM booster?
No. Those tools force programs to give up their cached pages, and your PC then reads the same data back off disk.
You get a lower number in Task Manager and a slower machine. Closing tabs and unused apps is the only version of this that helps you.
How do I know if I actually need more RAM?
Look at the Committed line under the memory graph in Task Manager, not the percentage.
If the first number regularly approaches the second, you are genuinely short and Microsoft documents that as the condition that causes freezing and crashes. Check whether your laptop has a free slot before you buy anything.
The Short Version
- A high memory percentage is usually Windows caching, not Windows struggling.
- Task Manager shows available memory, not free memory. They are different.
- On the idle PC measured here, 2.57 GB of 2.84 GB available was cache.
- The number to watch is Committed, under the memory graph in Task Manager.
- Committed here was 21.21 GB on a machine with 15.25 GB of real memory.
- That is normal, because committed memory is promised rather than occupied.
- Memory cleaners empty your cache and make your PC read it back off disk.
- If Committed sits near its limit, then you genuinely do need more memory.
Where to Next
If it is a spreadsheet rather than the machine giving you trouble, one button in Excel does more damage than any memory leak. Remove Duplicates deletes permanently and does not ask.
Open Task Manager, click Performance, then Memory, and find the Committed line under the graph. That single line tells you more than the percentage ever will.
If the first number is nowhere near the second, close this page and stop worrying. Nothing is wrong with your PC.
If it is close, sort the Details tab by memory and watch the top row for a few minutes. You are looking for one process that climbs and never comes back down.
Leave the page file on system managed while you do it, and leave SysMain alone. Both are there to help you.
And if you got here after a blue screen naming memory, that stop code is a separate question. Only two of the causes Microsoft lists for it are hardware.
If you were about to buy memory, check first whether your laptop can take any. Half of them cannot, and here is how to tell.
If you find one process eating everything on your machine, name it in the comments. Some of them turn up again and again and it is worth a list.
Isaac Smith is the founder and editor of PC Glance, a website that covers computers, laptops, and technology. He is a tech enthusiast and a computer geek who loves to share his insights and help his readers make smart choices when buying tech gadgets or laptops. He is always curious and updated about the latest tech trends.