Feb 05 2019 01:25 PM - edited Feb 05 2019 01:26 PM
We have about 2500 windows 7 machines that use KMS. A few days ago we started to see windows, not genuine pop-up. Called Microsoft they told me the key I was using is blocked.
When I log on to the workstation I type slmgr /ato and get the error 0xC004C003
I assumed because we entered into a new year with our Volume licensing, I needed to update the 2008 r2 server with a new key. That did not fix it, so I decided it was time to upgrade the KMS server to a new server 2012r2, that has not fixed it. Still getting the same error. Any ideas?
Feb 05 2019 04:04 PM - edited Feb 05 2019 04:07 PM
0xC004C003 = The activation server determined the specified product key is blocked
You can also try phone activation (slui 4) but will likely need a new key.
If a volume licensing issue I'd contact them here.
Feb 06 2019 12:26 PM
Solutioni found the issue it turns out that update kb971033 has something to do with this issue. here is how you fix it
run this from an elevated command prompt:
wusa /uninstall /kb:971033
net stop sppuinotify
sc config sppuinotify start= disabled
net stop sppsvc
del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-0.C7483456-A289-439d-8115-601632D005A0 /ah
del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-1.C7483456-A289-439d-8115-601632D005A0 /ah
del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\tokens.dat
del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\cache\cache.dat
net start sppsvc
cscript c:\windows\system32\slmgr.vbs /ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4 <---win 7 kms key
cscript c:\windows\system32\slmgr.vbs /ato
sc config sppuinotify start= demand
Feb 06 2019 12:45 PM
Good news, I would not recommend posting product keys in a public forum.
Feb 06 2019 12:46 PM - edited Feb 06 2019 12:47 PM
this is not an actual product key its windows public published KMS host key that correlates with win 7 pro
https://docs.microsoft.com/en-us/windows-server/get-started/kmsclientkeys
Feb 06 2019 12:26 PM
Solutioni found the issue it turns out that update kb971033 has something to do with this issue. here is how you fix it
run this from an elevated command prompt:
wusa /uninstall /kb:971033
net stop sppuinotify
sc config sppuinotify start= disabled
net stop sppsvc
del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-0.C7483456-A289-439d-8115-601632D005A0 /ah
del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-1.C7483456-A289-439d-8115-601632D005A0 /ah
del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\tokens.dat
del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\cache\cache.dat
net start sppsvc
cscript c:\windows\system32\slmgr.vbs /ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4 <---win 7 kms key
cscript c:\windows\system32\slmgr.vbs /ato
sc config sppuinotify start= demand