If you’ve encountered the message “The grace period expired before Windows was activated,” you’re looking at error code 0xC004F009. This activation error appears when your Windows installation ran past its grace period — typically 30 days — without successfully activating with Microsoft’s servers.
I see this error most often in three scenarios: fresh installations that never got around to activation, cloned machines where the activation got lost in translation, or systems that were offline during the critical first month. Whatever brought you here, let’s get it sorted.
Error 0xC004F009 means your Windows installation exceeded its 30-day activation grace period without successfully contacting Microsoft’s servers. To fix it, open Command Prompt as Administrator and run slmgr.vbs /rearm to reset the grace period, restart your computer, then activate immediately using your product key through Settings > System > Activation > Change product key. If you have a valid license and working internet connection, this resolves the error in most cases within a few minutes.
When you install Windows, Microsoft gives you a grace period to activate the product. Think of it as a trial run. Once that window closes without activation, the operating system locks you out of certain features and starts displaying watermarks and warnings.
Common causes include:
Before anything else, make sure you can actually reach the internet. Open a browser, visit a few sites. If that works, Windows should be able to reach the activation servers.
Sometimes it’s as simple as re-entering the key:
If you purchased Windows through MCAKey or another authorized reseller, double-check that you’re using the exact key from your confirmation email or license certificate.
When the GUI doesn’t cooperate, the command line often does. Open Command Prompt as Administrator and run:
slmgr.vbs /ipk YOUR-PRODUCT-KEY-HERE
slmgr.vbs /ato
The first command installs the key; the second attempts online activation. Watch for any error messages — they’ll tell you exactly what’s going wrong.
If the grace period expired but you have a valid key, you can reset the licensing timer:
slmgr.vbs /rearm
This command resets the activation grace period, giving you another 30 days to sort out any underlying issues. Note that you can only use this a limited number of times (usually three).
After running the rearm command, restart your computer, then try activating again.
Internet activation not working? Microsoft still offers phone activation:
slui 4.This method bypasses most network-related issues entirely.
If you’re in an organization using Key Management Service, error 0xC004F009 often means the client lost contact with your KMS host:
slmgr.vbs /ckms
slmgr.vbs /skms your-kms-server:1688
slmgr.vbs /ato
Confirm with your IT team that the KMS server is running, has available activations, and is reachable from the affected machine.
Sometimes the underlying problem is simply that your license isn’t valid for your current hardware or situation. This happens with:
In these cases, you’ll need to purchase a new Windows license. As an Authorized Microsoft Reseller, MCAKey can help you find the right licensing option — whether that’s a single retail key, volume licensing for your organization, or subscription-based options through Microsoft 365.
A few habits can save you from seeing 0xC004F009 again:
Error 0xC004F009 sounds intimidating, but it’s usually straightforward to resolve. The grace period expired — that’s all. With a valid product key and working internet connection, most people can clear this error in under five minutes.
If you’ve tried these steps and you’re still stuck, or if you need assistance with Windows licensing for your organization, reach out to our team at MCAKey. We’ve helped thousands of businesses navigate Microsoft licensing, and we’re happy to help you too.
If you’re still running into Windows Activation Error 0xC004F009 after trying the steps above, work through them once more in order — most cases resolve without needing anything more advanced.
Windows Activation Error 0xC004F009 is frustrating, but it’s rarely a sign of serious hardware failure — in most cases it’s a driver or configuration issue like the ones covered here.
Keep this guide handy if Windows Activation Error 0xC004F009 comes back after a Windows update, since driver-related regressions are the most common repeat cause.
A fresh driver install resolves Windows Activation Error 0xC004F009 in the majority of cases we see, so start there before assuming it’s a hardware fault.
Windows Activation Error 0xC004F009 that returns right after a Windows update almost always points back to a driver conflict, not new hardware failure.
Most people fixing Windows Activation Error 0xC004F009 for the first time are done within ten minutes once they know which driver to update.
If none of the steps above resolve Windows Activation Error 0xC004F009, check whether it only happens on battery power or only when plugged in — that narrows it down fast.
Windows Activation Error 0xC004F009 caused by a driver issue is one of the most common support requests we see, and also one of the easiest to fix for good.
For more detail, see Microsoft’s own troubleshooting documentation.
For more Windows and Microsoft software activation guides, visit our Help Center.
Windows remains functional after the grace period expires, but you’ll see a persistent watermark on your desktop, lose access to personalization settings, and receive repeated activation reminders until you resolve the issue with a valid product key.
Microsoft limits the rearm command to three uses per Windows installation. Each rearm resets your 30-day grace period, giving you time to troubleshoot activation issues, but once you’ve exhausted all three, you’ll need to reinstall Windows or activate with a valid key.
No, fixing this activation error does not affect your personal files, installed programs, or settings. Activation is purely a licensing check between your computer and Microsoft’s servers — resolving it simply unlocks the features that were restricted during the expired grace period.
Cloned VMs inherit the activation state of their source image, including an already-running or expired grace period timer. To avoid this, always run sysprep with the /generalize flag on your source image before cloning, which resets the activation clock for each new deployment.
Save on your order — use code FIXIT10
Limited-time, limited-use offer. Redeem it before it's gone.