Edit

Memory leak in the remote registry service causes Windows to hang

  • Article

This article provides a workaround for a memory leak issue in the remote registry service that causes Windows to hang.

Note

This issue is fixed in Windows 10.

Applies to:   Supported versions of Windows Server and Windows Client
Original KB number:   3105719

Symptoms

On a Windows-based computer, you notice that more system memory and paged pool memory are being consumed than expected. This memory leak occurs after about 10 minutes of system uptime and eventually causes the system to hang.

Additionally, PoolMon analysis may show that the Windows Notification Facility (WnF) tag is consuming all the available paged pool memory.

Cause

The issue occurs in the Endpoint Mapper Logic component.

Note

The Remote Registry service is designed to stop running after the connection has been idle for 10 minutes.

This is a by design behavior in Windows.

Workaround

To work around this issue, follow these steps:

  1. Open the run command box by pressing the Windows key+R.

  2. Type regedit.exe, and then press Enter.

  3. Locate the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\RemoteRegistry

  4. In the details pane (on the right side), double-click DisableIdleStop.

  5. Change the value to 00000001.

    Note

    The default value is 00000000.

  6. Exit Registry Editor.