My Windows 11 PC is showing around 89% memory usage immediately after startup, even with no programs open besides my VPN. With Firefox open, usage rises to roughly 97% with only one tab. Firefox itself reports about 2 GB, although I have two extensions installed. RAMMap also shows approximately 10 GB associated with svchost.exe. Windows is kept up to date through the normal shutdown prompts. A couple of months ago, I could run Firefox with around 10 tabs, including video, while playing a game without this happening. Is this normal caching or background activity, or could something be leaking memory?
4 Answers
If a specific svchost.exe instance is using 10 GB, identify the services hosted inside it instead of treating svchost as one single program. One of those services, or a related driver, could be responsible. If memory keeps climbing over time and does not fall when applications are closed, that points more toward a leak than ordinary Windows caching.
A more detailed memory viewer can reveal allocations that Task Manager groups together. Tools such as System Informer may help distinguish normal cache usage from a genuine process or driver leak. Compare the results after a clean reboot and after letting Windows sit idle for a while. Also review startup applications and run a malware scan if the usage remains unusually high.
The percentage by itself does not prove there is a problem. The important questions are whether the computer becomes slow, applications crash, or Windows starts paging heavily to disk. Windows can fill unused RAM with cache, but active programs should still be able to reclaim it. Check the Memory and Commit values in Task Manager rather than focusing only on the percentage.
Windows does use otherwise-available memory for caching and background tasks, and that memory should be released when an application needs it. However, nearly all 32 GB at startup is higher than expected. In Task Manager or RAMMap, right-click the svchost.exe entry and use the option to view its associated services. That can help identify which Windows service is responsible. After an update, maintenance or indexing may temporarily increase usage, so check whether memory returns to normal after several minutes and a restart.
Windows has used caching like this for a long time, including older releases, but the cache should still be released promptly when a game or other application requests memory. Persistent growth or crashes would be a reason to investigate further.