Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

License Error 0xC004F038

Office 0xC004F038: your KMS count is below the minimum of five clients

11 min read Updated October 5, 2026 Office & Microsoft 365 Licensing

Recommended fix

Microsoft Office 2024 Professional Plus - LTSC Volume key online activation

Original price was: 49,90 €.Current price is: 16,90 €.

Fix It Now

Fix it now

This is a refusal, not a fault. Microsoft publishes 0xC004F038 as the count reported by your KMS host being insufficient, and its Office page states the cause directly: the Office KMS pool contains fewer than five unique client computers. Read the count on the host, then decide whether you are short of machines or short of machines that count.

Run these on the KMS host, in an elevated Command Prompt. The first is Microsoft’s own instruction for this code

cscript slmgr.vbs -dlv all >c:\temp\KMSInfo.txt
notepad c:\temp\KMSInfo.txt
  1. Find the Office entry in that output and read its current count. Below five with Office clients waiting is the whole answer.
  2. If you have five or more Office devices, get them to check in: cscript ospp.vbs /act on each, from the Office folder, and watch the count move between runs.
  3. If the count will not move, check whether the clients share an Office client machine ID: cscript ospp.vbs /dcmid on two machines that should be distinct.
  4. If you genuinely have fewer than five Office devices, KMS cannot activate them. Move to MAK, or to Active Directory-based activation if the devices are domain-joined.

The threshold is enforced by the licensing service. Microsoft publishes no registry value, policy or command that lowers it.

If the count is climbing and clients are activating you are done. If it is stuck, the next section explains what the host is actually counting.

Why it happens

0xC004F038 is a KMS host declining correctly. Microsoft’s published text is that the computer could not be activated because the count reported by your Key Management Service is insufficient, and its dedicated Office page is blunter still: the issue occurs because the Office KMS pool contains fewer than five unique client computers. Until that number rises, every client asks and every client is refused.

The thresholds themselves are published, and they differ by what is asking. Clients running Windows activate if the count is 25 or higher; servers and volume editions of Office activate if the count is five or greater. The host counts unique connections from the past 30 days and stores only the 50 most recent contacts, so the number you can see has a ceiling as well as a floor.

There is a detail here that removes a lot of confusion about counting to five. Microsoft states that Office activates the first time it runs as long as the KMS host computer has received at least four prior activation requests. So the fifth machine to ask is the first to be activated, and machines one to four are refused while doing exactly what they should. Nothing is broken during that phase.

Machines are identified by a client machine ID rather than by name, and that is where most stuck counts come from. A dozen machines deployed from an image that was captured without rearming Office present one identity between them and count once. Microsoft’s documented remedy is to run OSPPREARM.EXE before Sysprep so the deployed machines get unique Office IDs. ospp.vbs /dcmid displays the ID, which is how you prove it rather than guess.

There are genuinely fewer than five Office devices

You have this one if The count sits low and stops climbing because there is nothing left to add.

  1. Accept that KMS is the wrong mechanism at this size rather than fighting it.
  2. Install a MAK on each device: cscript ospp.vbs /inpkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX, then cscript ospp.vbs /act.
  3. Confirm with /dstatus that the channel now reports MAK rather than a KMS client channel.

If the devices are domain-joined, look at Active Directory-based activation first. It activates volume Office on domain-joined computers, needs no host and no port, and Microsoft publishes no minimum count for it.

Cloned machines share one Office client machine ID

You have this one if Requests keep arriving at the host and the count refuses to move past one or two even though a dozen machines are trying.

  1. Compare the ID on two machines that should be distinct: cscript ospp.vbs /dcmid. Matching values are the answer.
  2. Fix the source image: run OSPPREARM.EXE on the template before Sysprep, which is Microsoft’s documented step for generating unique Office IDs.
  3. On machines already deployed, run cscript ospp.vbs /rearm, reboot, then cscript ospp.vbs /act.
  4. Watch the count on the host after each machine reactivates.

Clients are split across two hosts

You have this one if Two KMS hosts exist, DNS returns both, and neither reaches five because the estate is divided.

  1. Decide which host is authoritative for Office and remove the other’s _vlmcs service record from DNS.
  2. Pin the affected clients at the surviving host while you test: cscript ospp.vbs /sethst:kms.contoso.local.
  3. Once the count is above five and holding, return them to automatic discovery with cscript ospp.vbs /remhst.

Redundancy is sensible for a large estate and is the direct cause of this error in a small one, because each host has to reach the threshold on its own.

The count restarted when the host was rebuilt

You have this one if Office activated for months, the host was rebuilt or its licensing state reset, and everything failed from that day.

  1. Nothing is broken. The count is starting again and unactivated clients retry on their own.
  2. To speed it up, push cscript ospp.vbs /act through a startup script or your management tool.
  3. Re-check the Office count in slmgr /dlv all on the host until it passes five.

Machines dropped out of the 30-day window

You have this one if The count fell without anything being decommissioned, and a batch of devices has been off or off-network for a month.

  1. Check what changed a month ago rather than what changed yesterday. The host counts unique connections from the past 30 days.
  2. Bring the missing devices back on to the network and let them renew.
  3. If they are gone for good, the estate may now be below the threshold permanently, which is a MAK or directory-activation conversation.

Full reference

What the numbers actually are

Figure What Microsoft publishes
Threshold, Windows client editions Activate if the count is 25 or higher
Threshold, Windows Server and volume Office Activate if the count is five or greater
Counting window Unique connections from the past 30 days
Stored contacts The 50 most recent
First Office activation Succeeds once the host has received at least four prior requests
Licensed period 180 days, with a renewal attempt every seven by default

Windows and Office are counted per product on the host: slmgr /dlv all lists an entry for each product family it serves, each with its own current count, and Microsoft’s Office guidance talks about an Office KMS pool of its own. Two hundred activated Windows desktops therefore do nothing for four Office installations, however satisfying that would be.

Reading the host output without guessing

What you see on the host What it means
Office count below five and climbing Working as designed. Get the rest of the estate to check in
Office count flat while clients keep asking The same client machine IDs are being counted repeatedly
No Office entry at all The host has no Office licence pack. That is 0xC004F042 territory, not this
Count fell without machines being removed Machines stopped contacting the host inside the 30-day window
Two hosts, both with small counts The estate is split and neither will reach the threshold

Choosing between KMS, MAK and directory activation

KMS MAK Active Directory-based activation
Minimum count Five for Office None None published
Infrastructure A host, a DNS record, TCP 1688 None The Office Volume License Pack run on a domain controller
Scope Any machine that can reach the host Any machine Domain-joined computers
Renewal Automatic, 180-day licensed period One-off per activation Automatic, up to 180 days, by querying the directory
Activations Renewing A finite pool per key Renewing

The choice usually makes itself. Below the threshold with domain-joined machines, directory-based activation removes the problem entirely and needs no host to maintain. Below the threshold with machines that are not domain-joined, MAK is the answer. Above the threshold with a stuck count, none of this applies and you have an image problem to fix instead.

What the threshold is not

  • Not adjustable. Microsoft publishes no registry value, policy setting or command that lowers it, and anything claiming otherwise is either editing something unrelated or describing an activator.
  • Not a licensing limit. Meeting it is a technical precondition for the host to answer; it says nothing about what you are entitled to run.
  • Not different for virtual machines. Microsoft states KMS can activate physical and virtual computers, and publishes no separate threshold for either.
  • Not permanent once reached. The window is 30 days, so a count that was met last month can fall below the line without anyone doing anything.

That last point is worth planning around rather than reacting to. Padding a count with throwaway virtual machines works technically, because a machine that contacts the host is counted like any other, and it evaporates 30 days after you stop running them, at a moment nobody is watching. It also creates no entitlement for those machines.

The two companion codes

0xC004F00B and 0xC004F034 have no published descriptions. They turn up in the same exchange and are frequently given confident meanings without a source. Read what your machine says with cscript ospp.vbs /ddescr: and the code, and interpret the result alongside the count on the host rather than on its own.

When a licence is the actual fix

If your site will never have five Office devices, no amount of configuration changes that and the count is not going to rise. Multiple Activation Keys are the supported answer for small estates: one key, a fixed pool of activations, no host to build and no threshold to satisfy. Active Directory-based activation is worth looking at first if your devices are domain-joined, because it needs no extra product and removes the threshold entirely. Where MAK is the better fit, Arco supplies Office LTSC 2024 Professional Plus MAK keys sized to the device count you actually have, and will tell you plainly if your existing agreement already covers what you need.

Every code this article covers

Code What it points at Source
0xC004F038 The computer could not be activated because the count reported by your KMS host is insufficient. Microsoft’s Office page gives the cause as an Office KMS pool with fewer than five unique client computers Microsoft Learn
0xC004F00B Seen in the same exchange. No published description not published by the vendor
0xC004F034 Seen in the same exchange. No published description not published by the vendor

Confirm the fix worked

  1. On the host, the Office entry in slmgr /dlv all shows a current count of five or more.
  2. On a client, cscript ospp.vbs /act completes without an error.
  3. cscript ospp.vbs /dstatus on that client reports a licensed status with a remaining period in days.
  4. cscript ospp.vbs /dcmid returns different values on two machines that should be distinct.
  5. Re-check the count a week later and confirm it has held, which tells you the estate is renewing rather than having been pushed through once.

Questions people ask about this

Can the five-client minimum be lowered?

No. Microsoft publishes the thresholds and publishes no setting that changes them. Anything you find claiming otherwise is either editing something unrelated or describing an activator.

Do my Windows machines count towards the Office threshold?

No. The host keeps a count per product family, and slmgr /dlv all shows an entry for each with its own count. Microsoft’s Office guidance describes an Office KMS pool of its own, so a large activated Windows estate does nothing for a handful of Office installations.

Why did the fifth machine activate and the first four not?

Because Microsoft’s rule is that Office activates the first time it runs as long as the host has already received at least four prior activation requests. The first four are refused while doing exactly what they are supposed to.

How do I fix duplicate client machine IDs?

Prove it first with cscript ospp.vbs /dcmid on two machines. Then fix the image: Microsoft’s documented step is to run OSPPREARM.EXE before Sysprep so deployed machines get unique Office IDs. On machines already out there, ospp.vbs /rearm, reboot and reactivate.

What happens to Office while the count is too low?

Nothing immediately. Clients keep retrying. If the licensed period runs out before the count is met, Office enters the out-of-tolerance state for 30 days and then shows as unlicensed, with most features disabled.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error Visio 30053-4: a language pack installed without the matching Office build Free Fix Office 30015-4: the Click-to-Run install fails part way through License Error Office 0xC004C003: Microsoft has blocked this product key permanently License Error Office 0xC004B001: the activation server says the licence is invalid
โ† Back to Knowledge Base