1–10 of 10 posts
The other stats in task manager for memory say:
In use (compressed) - 13 GB (371 MB)
Available: 2.5 GB
Committed: 15.0/27.0 GB
Cached: 2.5 GB
Paged Pool: 400MB
Non-paged Pool: 410MB
Probably pre-warming.
To OP. Back in the XP days, hw was slow, so M$ started logging the most frequently used programs used at startup and started caching parts of the PE file to speed up the loading process. Other tricks included moving parts of the program to the outside of the spin disk as more data is read per revolution, and other tricks.
Profiling the use of the OS and finding ways to speed up the experience to compensate for slow hw has been ongoing since.
So its probably just profiling your machine, and indexing any documents you have to make the search facility in windows work better for you. The more it stores in ram, the faster windows can run for you.
However it could be a glitch, they also happen as well.
Sysinternals can help you gain insights to help you decide whether this ram usage is a good thing or not. And if you feel really bold, a bit of CPU instruction set logging could also help give some insight as to what is going on.
The auto-started/suspended programs can be configured to not auto-start. If this is the Home edition some things may be hidden or harder to turn off unless one runs O&O's ShutUp 10 [2] which also runs on Windows 11 and there are some settings within Edge to turn off auto-starting and pre-loading some widgets required even if one does not use Edge.
[1] - https://learn.microsoft.com/en-us/sysinternals/downloads/
- Which memory column are you looking at? (differences between private, committed, shared, working set, etc.)
- Are you running WSL, virtual machines, or anything like that?
- Is your account an administrator on the box?
- Try Resource Monitor instead of Task Manager - there's a lot more memory information there
And your committed clearly says 15GBs.