Skip to content

The clnotifications tool cleans up thousands of Windows Push Notification Platform (WPN) and Windows Notification Facility (WNF) values from `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Notifications` registry key. To prevent high CPU usage and slow user logons.

Notifications You must be signed in to change notification settings

Lazy-256/clnotifications

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

clnotifications

The clnotifications tool cleans up thousands of Windows Push Notification Platform (WPN) and Windows Notification Facility (WNF) values from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Notifications registry key. To prevent high CPU usage and slow user logons.

By default the tool skip first 500 values ans clean up the rest. It puts the logs into the same directory as the execution.

 & .\clnotifications.exe -?
clnotifications v0.1.1
flag provided but not defined: -?
Usage of C:\Users\...\Documents\golang\clnotifications\clnotifications.exe:
  -cleanup
        command to start cleaning up (default true)
  -count-values-in-chunks int
        number of values to delete in one chunk (default 100)
  -count-values-to-read int
        number of values to read in one iteration (default 1000)
  -count-values-to-skip-key int
        number of values to skip deletion (default 500)

  • There is a correlation between amount of values at Notifications the registry key and long logon time.
    • Microsoft has acknowledged that the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Notifications can get bloated with a large number of entries, which can cause issues such as slow logons. This happens due to leaked WNF registrations.
  • The explorer.exe and frxsvc.exe reads thousands of WPN and WNF values from this registry key during user logon. This can lead to high CPU usage and slow logons. See: ~30 second delay on the "Please wait for the FSLogix Apps Services" portion of the login
  • To resolve this issue, Microsoft provides a fix for Windows Server 2012 R2 that prevents WNF and WNF registrations from being leaked after its installation. The fix also includes a tool called wnfcleanup that removes stale WNF registrations created before the installation of the leak fix.
  • There is no official input from Microsoft on how to fix this issue for Windows Server 2019.

Reference

About

The clnotifications tool cleans up thousands of Windows Push Notification Platform (WPN) and Windows Notification Facility (WNF) values from `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Notifications` registry key. To prevent high CPU usage and slow user logons.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Languages