Is it ok if I disable Windows 10 memory compression?

Stealth3si

Distinguished
Dec 12, 2010
200
0
18,680
If I enable memory compression (via the mmagent cmdlet in powershell) I get this "error" in process explorer about a process called "memory compression" and the path reads "[a device attached to the system is not functioning.]":
YpxDhMe.jpg


When I try to access any kind of information on it via properties settings, which there is none, it says "Access Is Denied" the only info I can see is threads tab that shows "ntoskrnlGetCompressionWorkspace" error.

Anyways, if I disable memory compression via the mmagent cmdlet in powershell, I no longer get the "error" in process explorer! The image below shows that memory compression is disabled with its "False" value:
E4Jfwjm.jpg


But the other features having "True" values show that superfetch/prefetch is currently enabled. Normally superfetch enables memory compression by default when superfetch is on, until I manually disabled memory compression.

Suppose Superfetch (and memory compression) was enabled before then I disabled the Superfetch service in Service Manager, well this is what the mmagent cmdlet in Powershell looks like.
mTf8Cqc.jpg

With Superfetch disabled, it also disables memory compression.

Currently, I have enabled Superfetch but since I manually disabled memory compression it stayed disabled. Otherwise, memory compression would have been automatically enabled alongside the Superfetch features.
E4Jfwjm.jpg

 
Solution
ntoskrnl = new technology operating system kernel. The brains of windows 10, the supposed cause of many BSOD simply as it also deals with driver requests, and memory management and many other things.

win 10 uses memory compression when you close an application. Instead of putting it back on page file right away, it compresses the data so if you decide to open it again later, it loads instantly. It shows the amount of compressed data in the memory tab of task manager in brackets after in use.

I don't think you should turn it off as I don't know what the repercussions of it might be. It could cause out of memory errors as it may effect the level of commits...

Colif

Win 11 Master
Moderator
ntoskrnl = new technology operating system kernel. The brains of windows 10, the supposed cause of many BSOD simply as it also deals with driver requests, and memory management and many other things.

win 10 uses memory compression when you close an application. Instead of putting it back on page file right away, it compresses the data so if you decide to open it again later, it loads instantly. It shows the amount of compressed data in the memory tab of task manager in brackets after in use.

I don't think you should turn it off as I don't know what the repercussions of it might be. It could cause out of memory errors as it may effect the level of commits.

http://www.makeuseof.com/tag/ram-compression-improves-memory-responsiveness-windows-10/
 
Solution