How to Extend Windows Server 2022 RDP 120-Day Grace Period?
Registry Method and Practical PsExec Solution
Narbulut · System Administration Guide
What Is RDP Grace Period and Why Doesn’t slmgr Work?
When you enable the Remote Desktop Services (RDS) role on a Windows Server installation, Microsoft grants you a free 120-day Grace Period. Once this period expires, users can no longer connect to the server via RDP unless you have valid RDS CALs (Client Access Licenses).
Many administrators assume the slmgr /rearm command — used to extend the operating system’s evaluation license — also resets the RDS grace period. This is not the case. slmgr only manages the Windows Server license; the RDS grace period is a completely separate mechanism, reset by deleting the relevant counter key in the Registry.
On Windows Server 2022 Standard or Datacenter, there is no single CMD command that directly resets the RDP grace period. The process requires deleting the relevant time counter key in the Registry. This guide walks you through both the manual Registry method and the practical PsExec alternative that performs the reset with a single command.
Note: Windows Server 2022 is the most widely deployed enterprise LTSC release for both on-premise and Azure environments. Mainstream support continues through October 2026. The procedure below is identical for both Standard and Datacenter editions of WS 2022.
Method 1: Manual Registry Reset
You can reset the GracePeriod counter by applying the following 4 steps in order. All operations must be performed with Administrator privileges.
Step 1: Open the Registry Editor
- On the server, click the Start menu and type
regedit in the search bar.
- Right-click the result and select “Run as administrator”.
- Use the left-side tree to navigate to the following path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod
Step 2: Modify Permissions (Take Ownership)
For security reasons, Windows does not allow you to directly delete keys in this folder. You must first take ownership and enable Full Control:
- Right-click the GracePeriod folder and select Permissions.
- In the dialog that opens, click the Advanced button.
- Click the Change link next to the Owner field at the top.
- Enter
Administrators in the box, click Check Names, then click OK.
- Check “Replace owner on subcontainers and objects”, then click Apply and OK to close the windows.
- Right-click the GracePeriod folder again and go to Permissions. Select the Administrators group from the list and check the Full Control permission under the Allow column. Click Apply to save.
Step 3: Delete the L$RTMTIMEBOMB Key
- Look at the right pane of the GracePeriod folder.
- Right-click the binary entry whose name starts with
L$RTMTIMEBOMB.
- Select Delete and confirm with Yes.
Note: The exact name of this key varies from server to server (example: L$RTMTIMEBOMB_1320153D-8DA3-4e8e-B27B-0D888223A588). Since it is the only key starting with L$RTMTIMEBOMB, you can easily identify it.
Step 4: Restart the Server
The reset will not take effect until the server is restarted. Quick restart command from the command line:
shutdown /r /t 0
When the server comes back up, Windows will automatically create a fresh L$RTMTIMEBOMB key, and your legitimate 120-day evaluation period will start from the beginning.
Method 2 (Alternative): One-Line PsExec + PowerShell
If you don’t want to deal with permissions and ownership settings, you can use Microsoft Sysinternals’ PsExec tool to open PowerShell with SYSTEM privileges and delete the key with a single command.
Step 1: Download PsExec
Download PsExec from the official Microsoft Sysinternals page and extract it to any folder on the server (for example, C:\Tools\).
Step 2: Open PowerShell with SYSTEM Privileges
Open Command Prompt (CMD) as Administrator, navigate to the folder containing PsExec, and run the following command:
psexec -s -i powershell.exe
The new PowerShell window that opens runs under the SYSTEM user; there is no need to take ownership or modify permissions.
Step 3: Delete the Key with a Single Command
Remove-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod' -Name 'L$RTMTIMEBOMB_*'
Step 4: Restart the Server
shutdown /r /t 0
Verification: Was the Reset Successful?
After the server restarts, run the following PowerShell command to verify that the grace period has been reset:
Get-WmiObject -Namespace 'root\cimv2\TerminalServices' -Class Win32_TerminalServiceSetting | Select-Object GracePeriodDays
The command output shows the number of days remaining. If the reset was successful, you should see 120 (or a value close to it). If you see a lower value, make sure the server has been restarted, or repeat the steps.
Common Issues and Solutions
“Access Denied” Error
You may have applied the permission/ownership steps in Step 2 incompletely or incorrectly. Retry the steps, or use Method 2 (PsExec) to run with SYSTEM privileges.
L$RTMTIMEBOMB Is Not Visible
If the GracePeriod folder is empty, the RDS role may not have started yet. Enable the Remote Desktop Services role, restart the server once, and check again.
Timer Didn’t Reset
If you skipped the server restart after deleting the key, the change won’t take effect. Restart with shutdown /r /t 0.
PowerShell Command Returns an Error
Make sure to open PowerShell with SYSTEM privileges (via PsExec). Regular administrator privileges may not be sufficient for this key.
Important — License Compliance: For long-term production use, purchasing Windows Server 2022 RDS CALs is mandatory. 2022 RDS CALs work backward-compatibly on 2019 hosts, but they do not work on 2025 hosts. This guide is intended solely for test/lab environments and PoC projects; it is not a substitute for actual licensing in production.
Quick Action Summary
Registry Path
HKLM\SYSTEM\CCS\Control\Terminal Server\RCM\GracePeriod
Key to Delete
L$RTMTIMEBOMB_*
PsExec One-Liner
psexec -s -i powershell.exe
Restart Command
shutdown /r /t 0