Here’s more on that Registry process you may be seeing in Windows 10 build 17063

Reading time icon 2 min. read

Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

At the end of today’s blog post for Windows 10 build 17063, Microsoft made note of a new process labeled “Registry.” which may be seen in the Task Manager in the past couple Windows Insider builds. This process may be concerning for some Windows 10 users, but there’s no need to worry. Microsoft is providing the following explanation for the purposes of the Registry process.

  • In recent Insider Preview builds, you may have noticed a new process labelled “Registry” in Task Manager. The purpose of this process is similar to that of the memory compression store process in that it is a minimal process whose address space is used to hold data on behalf of the kernel. However, while the memory compression process is used to hold compressed pages, the registry process is used to hold registry hive data (e.g. HKEY_LOCAL_MACHINE\SOFTWARE, HKEY_CURRENT_USER).
  • Storing registry hive data in the registry process gives the registry access to more powerful memory management capabilities which will allow us to reduce the registry’s memory usage in the future.
  • Today’s Insider Preview build is the first to store hive data in the registry process and this is visible in Task Manager as increased memory usage by that process. Since this data was previously in kernel paged pool there is also a corresponding decrease in paged pool usage so overall there is no net change in hive data memory usage.

Did you find this registry process bothersome after you’ve installed this build? Let us know your thoughts below.