0xC004F009ActivationHigh

Error 0xC004F009 — SL_E_GRACE_TIME_EXPIRED | Windows Activation Fix

Windows 10Windows 11Windows Server 2016Windows Server 2019Windows Server 2022

What Does 0xC004F009 Mean?

The Software Licensing Service reported that the grace period has expired. The system must be activated before the grace period ends to continue using all features.

Real-World Causes

  1. 1Windows was installed but never activated within the grace period
  2. 2KMS activation failed to renew before the 180-day window expired
  3. 3System clock was changed, causing the grace period to appear expired
  4. 4Network issues prevented automatic reactivation

Symptoms

  • Desktop wallpaper turns black and cannot be changed
  • 'Activate Windows' watermark appears on desktop
  • Hourly shutdown notifications in some server editions
  • Reduced functionality mode warning messages

DIY Fix

Beginner-friendly steps you can try at home

  1. 1Enter a valid product key: slmgr /ipk <product-key>
  2. 2Activate online: slmgr /ato
  3. 3Reset the grace timer: slmgr /rearm (limited to 3 uses)
  4. 4Check your system clock is set correctly

Advanced Fix

For experienced users and IT professionals

  1. 1For KMS clients, verify the KMS host is reachable: nslookup -type=srv _vlmcs._tcp
  2. 2Reset Windows activation: slmgr /upk then slmgr /ipk <key> then slmgr /ato
  3. 3Check the registry key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform for SkipRearm value
  4. 4Use VAMT (Volume Activation Management Tool) for enterprise environments

Frequently Asked Questions

How long is the Windows activation grace period?
For retail and OEM installations, the grace period is typically 30 days. For KMS-activated volume license installations, it is 180 days with automatic renewal.
Can I extend the grace period?
You can use 'slmgr /rearm' up to three times to reset the 30-day grace period. After that, you must activate Windows with a valid product key.

Related Error Codes

About the Author

Windows Troubleshooting Team

Verified against official Microsoft documentation and real-world diagnostic data. Error behavior confirmed across Windows 10, Windows 11, and Windows Server.