Get in touch with us!

Azure VM activation error 0xC004F074

Last week when I was deploying some VMs in Azure I got this nice water stamp.

First I blamed expressroute, but then I got the same message on another tenant.
Then trying to do an activation I got this error.

Error 0xC004F074

This error can occur with a support version mismatch between the KMS client and the KMS host machine. 

Most commonly we are seeing this when the KMS host is running on Windows Server 2003 or Windows Server 2008 and the KMS client is Windows 7 or Windows Server 2008 R2. An update is needed for the KMS host running on Windows Server 2003 and an update is needed for the KMS host running on Windows Server 2008 to be able to activate KMS clients that are Windows 7 or Windows server 2008 R2. 

This error also can occur when there may be a time difference between the KMS client and KMS host machine.

The error 0xC004F06C listed in the info section may occur if the difference between system time on the client computer and the system time on the KMS host is more than 4 hours. We recommend that you use a Network Time Protocol (NTP) time source or the Active Directory service to synchronize the time between computers. Time is coordinated between the KMS host and the client computer in Coordinated Universal Time (UTC). ” – from https://support.microsoft.com/en-us/kb/974998

And NO, “w32tm /resync” didn’t help.

After some {favorite search engine}ing if found this blog post.

http://blogs.msdn.com/b/mast/archive/2014/12/23/troubleshooting-windows-activation-failures-on-azure-vms.aspx

Long story short. Hammering -ato didn’t do it, neither did changing the key.

Then I found this : http://technet.microsoft.com/en-us/library/dn303421.aspx

Not sure what caused this, but the AVMA key worked just fine.

iex "$env:windirsystem32cscript.exe $env:windirsystem32slmgr.vbs /ipk Y4TGP-NPTV9-HTC2H-7MGQ3-DV4TW"
iex "$env:windirsystem32cscript.exe $env:windirsystem32slmgr.vbs /ato"

If you have had the same issue or know something about it, please send a message or tweet me @meapax

Submit a Comment

Your email address will not be published. Required fields are marked *