Windows 10: Memory leak issue in Remote Registry Service causes Windows 10 to hang

In Windows 10, the Remote Registry service is a feature that enables remote access […]

This article Memory leak issue in Remote Registry Service causes Windows 10 to hang first appeared on TheWindowsClub.com.

read more...

 

netsvcs memory leak, need assistance identifying and fixing

My Windows 10 Pro laptop has a serious memory leak going on. If I leave it on overnight, I will often come back in the morning and memory usage will top 90%.When I check my processes, I see Service Host: Local System is where this is happening. When I drill into the services, I see that netsvcs services are causing it. The services running are:

• AppInfo
• BDESVC
• BITS
• Browser
• CertPropSvc
• DoSvc
• gpsvc
• IKEEXT
• iphlpsvc
• LanmanServer
• lfsvc
• ProfSvc
• Schedule
• SENS
• SessionEnv
• ShellHWDetection
• Themes
• UserManager
• Winmgmt

Things I Have Tried

• Stopping some of these indivually with mixed (temporary) results. One time stopping lfsvc (geolaction service) and iphlpsvc (ip helper) dropped the memory usage a bit but it eventually climbed back up. People suggest stopping BITS, but this didn't help either.
• I have tried running the Windows 10 Update Troubleshooter. It claims to have found and fixed issues every single time I run it, but in the long run, it's no help.
• sfc /scannow and DISM. I ran these and they found some issues, which I fixed with a Windows 10 Pro ISO to repair. Still I have a memory leak.
• Registry Updates. Updated TimeBroker and Superfetch per this article
• Full Anti-Malware Scans. No issues found with Norton Security Suite or Spybot
• Updated Killer Networking Drivers. No luck

Any assistance on running this down is much appreciated.

 

Memory leak issue

The term "memory leak" means that an application fails to return all its RAM to the operating system when it exits. The leftover RAM is unusable to the operating system.

Step one is to identify the application that is leaking memory. Step two is to contact the application's developers and provide as much detailed data on the memory leak as you can. For example: which processes are still in RAM after the application exits
and how much RAM they occupy. Application developers never want their applications to leak memory and they will be grateful for the details you provide, particularly if they can replicate the leak on their own computers.

 

Memory Leak.

I had a memory leak with the antimalware service after the fall creators update. At one point it was taking over 900MB and still growing. Event after reboots it would sometimes start off around 500 MB.

I remembered I had disabled real time protection via the registry (long time ago, before the upgrade), and tried reverting the setting. The problem with the antimalware service seems to have disappeared for me. It stays under 100MB.

But in any case, such setting, which is pretty much a feature. Shouldn't be causing a memory leak. So it's possible the process may trigger the memory leak in other ways. Keep an eye open for that particular process.