Office 2010 Activation 0xc004f074

Office 2016 Activation Failed Method 1: Download and Install Latest Microsoft Office 2016 Volume License Pack. As mentioned in Microsoft support article, if your system co-hosts the Office 2013 KMS host and Office 2016 KMS host and the operating. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.

Kms Error 0xc004f074
Office 2010 Activation Error 0xc004f074
Error Code 0xc004f074 Activation Microsoft
Office 2010 Activation 0xc004f074
Windows 10 0xc004f074 Activation Error

-->

This article was written by Eric Ashton, Senior Support Escalation Engineer.

The second way to activate Microsoft Office 2010 is to use the help of the KMSAuto activator. This software is very easy to use and is able to overcome the warning of product activation failed at Office 2010. How to activate Microsoft Office 2010 without a product key: First, download the KMSAuto file here. After that extract the RAR file.
Update Your KMS Host 9 (Windows Server 2003) Are you running later versions of Windows Server?
Download & Install the latest MS Office 2016 Volume License Pack. From the official report of.

Symptoms

You try to activate Microsoft Office 2013 or Office 2016 through the Key Management Service (KMS) host by using any of the following methods:

Volume Activation Management Tool (VAMT)
Office activation wizard from a client computer
OSPP.vbs /act script

However, you receive the following error message:

Cause

This issue occurs because the Office KMS pool contains fewer than five unique client computers.

Resolution

To resolve this problem, increase the number of client computers in the Office KMS pool to five or more.

Note

To determine how many client computers are currently in the Office KMS pool on the KMS host, run the following command in an elevated Command Prompt window from c:windowssystem32, and then press Enter:

Cscript slmgr.vbs -dlv all >c:tempKMSInfo.txt

Go to c:temp (or any custom location where you put the output), and then open KMSInfo.txt. Search for Office to find your Office KMS host installation details. Check the Current Count value. If the Office KMS count value is less than 5, Office clients will not activate.

When the Office KMS pool contains five or more client computers, try to activate Office by using the Office activation wizard, OSPP.vbs, or VAMT.

If you use System Preparation (Sysprep) in your environment, it is possible that Office was not rearmed before the image creation. Therefore, computers may have the same client computer ID (CMID) for Office.

If you have more than five computers that are trying to activate, and you still see this error message, check the KMS host log on Event Viewer on the KMS server. For example, you see entries that resembles the following:

0x0,5,Ignite1.ignite.local,930bd202-a335-4c7e-bd9d-7305361f0d37,Date/Time,0,5,0,6f327760-8c5c-417c-9b61-836a98287e0c
0x0,5,Ignite2.ignite.local,2f362dd3-fb39-4d18-94e6-de1d30dd27d5,Date/Time,0,5,0,6f327760-8c5c-417c-9b61-836a98287e0c
0x0,5,Ignite5.ignite.local,930bd202-a335-4c7e-bd9d-7305361f0d37,Date/Time,0,5,0,6f327760-8c5c-417c-9b61-836a98287e0c

In this example, notice that Ignite5 and ignite1 have the same CMID (930bd202-a335-4c7e-bd9d-7305361f0d37). This indicates that the Office rearm was skipped even though the base operating system image may have been generated.

Note

Before Sysprep prepares the image, make sure that you run one of the following commands, based on your Office bit version, to guarantee a unique Office CMID.

32-bit Office:
C:Program Files (x86)Microsoft OfficeOffice16ospprearm.exe

64-bit Office:
C:Program FilesMicrosoft OfficeOffice16ospprearm.exe

For detailed information about how to rearm the Office installation, see the following articles:

You can run the following startup script on these computers to rearm Office and generate new, unique Office IDs. In this script, replace XX with the appropriate value, based on your Office version:

XX = 15 for Office 2013

XX = 16 for Office 2016

@echo off

:OSPP

reg query HKLMSoftwareMicrosoftOfficeXX.0CommonOSPPREARM if %errorlevel%1 (goto RUN) else (goto END)

:RUN set ProgramFilesPath=%ProgramFiles%

'%ProgramFilesPath%Microsoft OfficeOfficeXXOSPPREARM.EXE'

Kms Error 0xc004f074

C:Windowssystem32cscript.exe '%ProgramFilesPath%Microsoft OfficeOfficeXXospp.vbs' /act set ProgramFilesPath=%ProgramFiles(x86)%

'%ProgramFilesPath%Microsoft OfficeOfficeXXOSPPREARM.EXE'

C:Windowssystem32cscript.exe '%ProgramFilesPath%Microsoft OfficeOfficeXXospp.vbs' /act REG ADD 'HKLMSoftwareMicrosoftOfficeXX.0CommonOSPPREARM'

:END

Exit

-->

This article helps fix the error 0xC004F074 that occurs when you activate Windows.

Original product version: Windows 7 Service Pack 1, Windows Server 2012 R2
Original KB number: 974998

Symptom

When trying to activate Windows 7 or Microsoft Windows Server 2008 R2 KMS client machines, you may get this error message:

0xC004F074 with description 'The Key Management Server (KMS) is unavailable'

At the same time, the following entries may get logged in the KMS Event Log on KMS Client and KMS Host

In the application event log on KMS Client, you see the following event:

Log Name: Application
Source: Microsoft-Windows-Security-SPP
Date:

Event ID: 12288
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer:

Description:
The client has sent an activation request to the key management service machine.
Info:
0xC004F06C, 0x00000000, <KMS Host FQDN>:1688, 36f27b39-2fd5-440b-be67-a09996d27a38, 2010/09/29 17:52, 0, 2, 41760, 68531fb9-5511-4989-97be-d11a0f55633f, 5

In the application event log on KMS Host, you see the following event:

Log Name: Key Management Service
Source: Microsoft-Windows-Security-Licensing-SLC
Date:

Event ID: 12290
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer:
Description:
An activation request has been processed.
Info:
0xC004F06C,5,<KMS Client name>,36f27b39-2fd5-440b-be67-a09996d27a38,2010/9/29 21:46,0,2,41520,68531fb9-5511-4989-97be-d11a0f55633f

Cause

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.

Office 2010 Activation Error 0xc004f074

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).

Error Code 0xc004f074 Activation Microsoft

Resolution