SOLVED
Home

KMS Issue 0xC004C003

%3CLINGO-SUB%20id%3D%22lingo-sub-331330%22%20slang%3D%22en-US%22%3EKMS%20Issue%200xC004C003%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331330%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20about%202500%20windows%207%20machines%20that%20use%20KMS.%26nbsp%3B%20A%20few%20days%20ago%20we%20started%20to%20see%20windows%2C%20not%20genuine%26nbsp%3Bpop-up.%20Called%20Microsoft%20they%20told%20me%20the%20key%20I%20was%20using%20is%20blocked.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20log%20on%20to%20the%20workstation%20I%20type%20slmgr%26nbsp%3B%2Fato%26nbsp%3Band%20get%20the%20error%26nbsp%3B0xC004C003%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20assumed%20because%26nbsp%3Bwe%20entered%20into%20a%20new%20year%20with%20our%20Volume%20licensing%2C%20I%20needed%20to%20update%20the%202008%20r2%20server%20with%20a%20new%20key.%20That%20did%20not%20fix%20it%2C%20so%20I%20decided%26nbsp%3Bit%20was%20time%20to%20upgrade%20the%20KMS%20server%20to%20a%20new%20server%202012r2%2C%26nbsp%3B%20that%20has%20not%20fixed%20it.%26nbsp%3B%20Still%20getting%20the%20same%20error.%26nbsp%3B%20Any%20ideas%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-331330%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-331925%22%20slang%3D%22en-US%22%3ERe%3A%20KMS%20Issue%200xC004C003%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331925%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20news.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-331923%22%20slang%3D%22en-US%22%3ERe%3A%20KMS%20Issue%200xC004C003%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331923%22%20slang%3D%22en-US%22%3E%3CP%3Ethis%20is%20not%20an%20actual%20product%20key%20its%20windows%20public%20published%26nbsp%3BKMS%20host%20key%20that%20correlates%20with%20win%207%20pro%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fget-started%2Fkmsclientkeys%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fget-started%2Fkmsclientkeys%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-331921%22%20slang%3D%22en-US%22%3ERe%3A%20KMS%20Issue%200xC004C003%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331921%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20news%2C%20I%20would%20not%20recommend%20posting%20product%20keys%20in%20a%20public%20forum.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-331905%22%20slang%3D%22en-US%22%3ERe%3A%20KMS%20Issue%200xC004C003%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331905%22%20slang%3D%22en-US%22%3E%3CP%3Ei%20found%20the%20issue%20it%20turns%20out%20that%20update%20kb971033%20has%20something%20to%20do%20with%20this%20issue.%20here%20is%20how%20you%20fix%20it%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Erun%20this%20from%20an%20elevated%20command%26nbsp%3Bprompt%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewusa%20%2Funinstall%20%2Fkb%3A971033%3CBR%20%2F%3Enet%20stop%20sppuinotify%3CBR%20%2F%3Esc%20config%20sppuinotify%20start%3D%20disabled%3CBR%20%2F%3Enet%20stop%20sppsvc%3CBR%20%2F%3Edel%20%25windir%25%5Csystem32%5C7B296FB0-376B-497e-B012-9C450E1B7327-5P-0.C7483456-A289-439d-8115-601632D005A0%20%2Fah%3CBR%20%2F%3Edel%20%25windir%25%5Csystem32%5C7B296FB0-376B-497e-B012-9C450E1B7327-5P-1.C7483456-A289-439d-8115-601632D005A0%20%2Fah%3CBR%20%2F%3Edel%20%25windir%25%5CServiceProfiles%5CNetworkService%5CAppData%5CRoaming%5CMicrosoft%5CSoftwareProtectionPlatform%5Ctokens.dat%3CBR%20%2F%3Edel%20%25windir%25%5CServiceProfiles%5CNetworkService%5CAppData%5CRoaming%5CMicrosoft%5CSoftwareProtectionPlatform%5Ccache%5Ccache.dat%3CBR%20%2F%3Enet%20start%20sppsvc%3CBR%20%2F%3Ecscript%20c%3A%5Cwindows%5Csystem32%5Cslmgr.vbs%20%2Fipk%20FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4%20%26lt%3B---win%207%20kms%20key%3CBR%20%2F%3Ecscript%20c%3A%5Cwindows%5Csystem32%5Cslmgr.vbs%20%2Fato%3CBR%20%2F%3Esc%20config%20sppuinotify%20start%3D%20demand%3CBR%20%2F%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-331395%22%20slang%3D%22en-US%22%3ERe%3A%20KMS%20Issue%200xC004C003%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331395%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3E0xC004C003%20%3D%20The%20activation%20server%20determined%20the%20specified%20product%20key%20is%20blocked%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20can%20also%20try%20phone%20activation%20(slui%204)%20but%20will%20likely%20need%20a%20new%20key.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F938450%2Fhow-to-troubleshoot-volume-activation-error-codes-in-windows-7-in-wind%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F938450%2Fhow-to-troubleshoot-volume-activation-error-codes-in-windows-7-in-wind%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20a%20volume%20licensing%20issue%20I'd%20contact%20them%20here.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fsupportrequestform%2F2afa6f15-b710-db46-909a-8346017c802f%3Fsl%3Den%26amp%3Bsc%3DUS%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fsupportrequestform%2F2afa6f15-b710-db46-909a-8346017c802f%3Fsl%3Den%26amp%3Bsc%3DUS%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
troma76
New Contributor

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? 

5 Replies

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.

https://support.microsoft.com/en-us/help/938450/how-to-troubleshoot-volume-activation-error-codes-in...

 

If a volume licensing issue I'd contact them here.

https://support.microsoft.com/en-us/supportrequestform/2afa6f15-b710-db46-909a-8346017c802f?sl=en&sc...

 

 

 

 

Solution

i 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
 

Good news, I would not recommend posting product keys in a public forum.

 

 

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

Good news.

 

 

Related Conversations
Using Azure VM as KMS server
ilyas_n19 in Windows Server for IT Pro on
0 Replies