Windows Software Licensing Grace Period Registry Key

This article outlines where the Windows Registry records active configurations and counters for system-wide software licensing grace periods. Windows manages these grace periods through distinct components depending on the service, primarily leveraging the Software Protection Platform (SPP) for core operating system licensing and the Remote Desktop Connection Manager for Terminal Services. Below are the precise registry paths, associated values, and operational details for locating and interpreting these grace period configurations in Regedit.

Windows OS Software Protection Platform (SPP)

The primary registry path responsible for core Windows activation, grace period state, and rearm counter configuration is:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform

Key entries within this location include:

• SkipRearm: A DWORD value specifying whether the software licensing rearm process resets the grace timer without decrementing the allowable rearm count (1 enables skipping, while 0 enforces normal rearm counting).
• KeepCleanSLP: Determines the preservation state of software licensing policies and cached tokens during system updates.
• UserOperations: Controls whether non-elevated user contexts can query or trigger licensing validation operations.

The real-time countdown and cryptographic validation data are maintained in secure, trusted storage by the Software Protection service (sppsvc), referenced via HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sppsvc.

Remote Desktop Services (RDS) Grace Period

For systems utilizing Remote Desktop Licensing, Windows enforces a dedicated 120-day grace period counter before requiring a Remote Desktop Session Host license server. Regedit records this active configuration under:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod

Within this key, the system creates a REG_BINARY entry (typically named with an internal string such as L$RTMTCMD...) containing the encrypted timestamp and active countdown ticks for the grace period.

Because this configuration key is protected by default operating system access controls, modifying or viewing full administrative details requires taking ownership of the GracePeriod key from the default SYSTEM or TrustedInstaller identity.