• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Is it ok if I disable Windows 10 memory compression?

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Stealth3si

Member
Joined
Jul 12, 2007
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
 

Attachments

  • YpxDhMe.jpg
    YpxDhMe.jpg
    221.8 KB · Views: 258