0xC004F061 / 0xC004F200

Windows Not Genuine – Fix Build 7601 Error Fast

Windows Errors Intermediate 👁 7 views 📅 Jun 22, 2026

This 'Windows not genuine' popup (0xC004F061) hits when activation keys mismatch or corrupted tokens block validation. I'll show you how to force rearm and re-activate without reinstalling.

Quick answer: Open Command Prompt as admin and run slmgr /rearm, then slmgr /ato. Reboot. If the popup returns, you have a corrupted token file – skip to fix step 2.

Why Windows Thinks You're a Pirate

This 'not genuine' message appears when the activation timestamp gets out of sync with Microsoft's servers or when the token store file (tokens.dat) gets corrupted. What's actually happening here is that Windows checks for a valid license key at boot. If the key is correct but the validation fails anyway, the problem is almost always a broken token file or a misapplied update (KB971033, looking at you).

I've seen this a lot on Windows 7 after a motherboard swap, or on Windows 10 after a failed update. The popup shows up in the bottom-right corner, and you get error codes like 0xC004F061 (time mismatch) or 0xC004F200 (key not valid for this build).

Fix Steps – Try This First

  1. Open Command Prompt as admin. Type 'cmd' in Start, right-click, 'Run as administrator'.
  2. Check current activation status: Run slmgr /dli. This shows if Windows thinks you're activated or not. Write down the description line.
  3. Rearm the activation timer: Run slmgr /rearm. This resets the activation grace period (60 days on Win7, 30 on Win10 by default). You'll see a message that the command succeeded.
  4. Reboot your machine. Not optional. The rearm only takes effect after a restart.
  5. Attempt activation: After reboot, run slmgr /ato. This tells Windows to try activating online. If it says 'activation succeeded', you're done.
  6. If it fails: Check the error code. 0xC004F061 means the system's time is off – fix your date and time in BIOS first, then retry step 5.

When Step 1 Doesn't Work – Corrupted Token Fix

If the popup returns after a few days, or if slmgr /ato0xC004F200, the token file is corrupted. Here's the fix that actually works:

  1. Stop the Software Protection service: Open Services.msc (Win+R, type services.msc), find 'Software Protection', right-click, Stop.
  2. Delete the old token file: Go to C:\Windows\System32\spp\store\2.0 (or store on Win7). Delete the file named tokens.dat. Don't delete anything else.
  3. Rebuild the token file: Open Command Prompt as admin again. Run slmgr /rilc. This re-licenses Windows – it rebuilds the token file from scratch. Wait maybe 30 seconds.
  4. Restart the service: Go back to Services.msc, start 'Software Protection' again.
  5. Activate again: Run slmgr /ato. Should work this time.

Why this works: The tokens.dat file stores your activation state. When it corrupts, Windows sees no valid key and shows the bogus 'not genuine' message. Deleting and rebuilding it forces Windows to re-validate the actual product key embedded in the BIOS or registry. The reason step 3 works is that slmgr /rilc writes a fresh, clean token file based on the installed key – not whatever garbage was there before.

Alternative Fixes if the Main One Fails

If you're still stuck, try these in order:

Option A – Remove KB971033

This update (KB971033) is a Windows activation validation patch that sometimes bricks genuine keys. On Windows 7, uninstall it:

  1. Go to Control Panel > Programs > View installed updates.
  2. Search for KB971033.
  3. Right-click, uninstall. Reboot.
  4. Run slmgr /ato again.

This is the first thing I try on any Windows 7 machine with this error. Half the time, that's the only problem.

Option B – Use Safe Mode to Force Re-Registration

  1. Boot into Safe Mode (F8 at startup, or Shift+Restart on Win10).
  2. Open Command Prompt as admin.
  3. Run slmgr /upk (uninstalls the product key).
  4. Run slmgr /ipk YOUR-PRODUCT-KEY-HERE (re-installs it). Replace with your actual 25-char key.
  5. Then slmgr /ato. Safe mode bypasses some validation hooks that might be blocking activation.

Option C – Activation with Phone

If nothing online works, do offline activation:

  1. Run slui 4 from Command Prompt (admin). This opens the phone activation wizard.
  2. Pick your country, call the number, give the installation ID to the robot, type back the confirmation ID.
  3. This works even when Microsoft's server says your key is 'not genuine'. The phone system is more forgiving.

Prevention – Don't Let This Happen Again

Three things cause this error most often:

  • Changing hardware without reactivating. If you swap a motherboard or hard drive, always run slmgr /ato after. Do it before you install updates.
  • Running outdated Windows with no updates. Missing security patches can corrupt the activation stack. Keep Windows Update running – but hide KB971033 on Win7.
  • Using a 'generic' or volume license key. If you installed with a KMS key and don't have a KMS server, you'll see this error. Use a retail key instead.

One more thing: if you're on Windows 10 and getting this error, check if you have the Windows Activation Technologies service set to Automatic. If it's disabled, enable it:

sc config watsvc start= auto
sc start watsvc

That's it. The popup should be gone for good. If it comes back, you have a counterfeit key – no fix for that except buying a real license.

Was this solution helpful?