Fix it now
The KMS host is refusing you because its count is below the threshold: 25 for Windows client editions, 5 for Windows Server, both counting physical and virtual machines. Read the count on the host, then decide whether you are short of machines or short of machines that count.
slmgr /dlv
slmgr /dli
- Read the Current Count line. Below 25 with client machines waiting is the whole answer: the threshold has not been met.
- Decide which case you are in. Fewer than 25 client machines in total means KMS will never work here, and MAK or Active Directory-Based Activation is the supported answer.
- Twenty-five or more machines with a count that will not climb means they are not being counted. Check that the image was generalised, and that you do not have several KMS hosts splitting the count between them.
- Push activation from the clients with
slmgr /atoand watch the count move on the host between runs.
The threshold is enforced by the licensing service. There is no supported registry value, policy or command that lowers it, and every workaround that claims otherwise is fabricating a count.
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 not a fault. It is a KMS host declining, correctly, because it has not yet seen enough machines to start handing out activations. The published text is that the count reported by your Key Management Service is insufficient, and until the number rises every client asks and every client is refused.
The host counts unique machines that have contacted it within the last 30 days, and it stores the 50 most recent contacts. That window is the part people miss. A count does not fall because machines were decommissioned; it falls because machines stopped talking to the host inside the window. The number you can see tops out at 50 in a mixed estate, or 10 where only Windows Server has ever contacted the host.
The count is cumulative between operating systems – one pool, not one per product – and the thresholds applied to it differ by what is asking. A Windows client edition needs 25 or higher; Windows Server needs 5 or higher; both figures include virtual machines. Machines are identified by their CMID, and that is where most stuck counts come from: the host counts unique CMIDs, so a hundred machines deployed from an image that was never generalised present one identity between them and count once.
There are genuinely fewer than 25 client machines
You have this one if The count sits at a low number and stops climbing because there is nothing left to add.
- Accept that KMS is the wrong mechanism at this size and move to MAK activation.
- On each client:
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXXthenslmgr /ato. - Confirm with
slmgr /dlithat the description now names a MAK channel rather than VOLUME_KMSCLIENT.
If the estate is domain-joined, look at Active Directory-Based Activation before buying keys. It activates domain-joined machines with no host to maintain and no count threshold to meet.
The clients were deployed from an image that was not generalised
You have this one if Plenty of machines, all reaching the host, and the count stays flat at one or two.
- On two clients that should be distinct, compare the CMID in
slmgr /dlv. Matching CMIDs are the answer. - Rebuild the reference image and generalise it with
sysprep /generalize, then redeploy. - Confirm the count climbs as the rebuilt machines come online.
slmgr /rearm resets the activation timers. It does not issue a machine a new CMID, so it is not a fix for duplicates.
Several KMS hosts are splitting the count between them
You have this one if The estate is large enough, every host has a count, and no single host reaches the threshold.
- Find every host publishing a record: check the _vlmcs entries in each DNS zone.
- Decide on one host, and remove the KMS host key or the DNS record from the others.
- Let the clients re-discover, and watch the count consolidate on the host you kept.
The count was reset when the host was rebuilt
You have this one if KMS worked last month, the host was rebuilt or its licensing store was reset, and the count restarted at zero.
- Wait. Unactivated clients retry every two hours by default and the count rebuilds itself.
- To speed it up, push
slmgr /atothrough a startup script or your management tool. - Watch the count climb with repeated
slmgr /dlvcalls on the host.
Full reference
Which machine logs what
This is the detail that wastes the most time on this error, because the two events people are told to look for are not on the machine they are told to look at.
| Event ID | Logged on | Log | What it records |
|---|---|---|---|
| 12288 | The KMS client | Application | The client sent an activation request. A 12288 with no 12289 after it means nothing came back |
| 12289 | The KMS client | Application | The response arrived. Carries the activation flag – 1 for success, 0 for failure – and the current count on the host |
| 12290 | The KMS host | Key Management Service | A client contacted the host. Carries the client’s CMID and the count at that moment |
| 12293 | The KMS host | Key Management Service | The host failed to publish its DNS records |
So to answer “are my clients reaching the host at all”, read 12290 on the host. To answer “what did this particular client get told”, read 12288 and 12289 on the client. A flat count with plenty of 12290 entries is a counting problem; a flat count with no 12290 entries at all is a discovery or network problem, and this is the wrong article for it.
Reading the count without guessing
| What you see on the host | What it means |
|---|---|
| Current Count below the threshold, climbing slowly | Working as designed. Get the rest of the estate to check in |
| Current Count flat while 12290 events keep arriving | The same CMIDs are being counted repeatedly. Generalise the image |
| Current Count capped at 50 | That is the maximum stored, not a problem |
| Current Count capped at 10 | Only Windows Server has ever contacted this host |
| Count fell without machines being removed | Machines stopped contacting the host inside the 30-day window |
Choosing between KMS, MAK and ADBA
| KMS | MAK | Active Directory-Based Activation | |
|---|---|---|---|
| Minimum machines | 25 client, 5 server | None | None |
| Infrastructure | A host, a DNS record, TCP 1688 | None | The AD forest |
| Renewal | Every 180 days, automatically | One-off per machine | Automatic while domain-joined |
| Scope | Any machine that can reach the host | Any machine | Domain-joined machines only |
| Activations | Unlimited, renewing | A finite pool per key | Unlimited |
The choice usually makes itself. Below the threshold with domain-joined machines, Active Directory-Based Activation removes the problem entirely and costs nothing to run. 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 or a host-count problem to fix instead.
What the thresholds are not
- Not adjustable. No registry value, Group Policy setting or slmgr option lowers 25 or 5.
- Not separate per operating system. The count is cumulative; the thresholds differ, the pool does not.
- Not different for virtual machines. Both published thresholds include VMs.
- Not a licensing limit. Meeting the threshold is a technical precondition for the host to answer; it says nothing about what you are entitled to run.
That last point matters when someone suggests spinning up throwaway virtual machines to pad the count. It works technically, because a VM that contacts the host is counted like anything else. It does not create an entitlement for those machines, and the padding evaporates 30 days after you stop running them, taking the count back below the threshold at a moment nobody is watching.
When a licence is the actual fix
If the site will never reach 25 client machines, KMS is structurally the wrong tool and no configuration changes that. Check Active Directory-Based Activation first, because for domain-joined machines it removes the threshold at no cost. Where the machines are not domain-joined, Multiple Activation Keys are the supported answer: one key, a fixed pool of activations, no host to maintain. Arco supplies Windows 11 Enterprise MAK keys sized to your seat count, and will tell you if ADBA would serve you better before selling you anything.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC004F038 |
The count reported by the KMS host is below the threshold needed to activate this product | Microsoft Learn |
Event ID 12288 |
Logged on the KMS client, in the Application log, when it sends an activation request | Microsoft Learn |
Event ID 12289 |
Logged on the KMS client, in the Application log, when the response arrives, carrying the activation flag and the host’s current count | Microsoft Learn |
Confirm the fix worked
- On the host,
slmgr /dlvshows Current Count at 25 or above for clients, or 5 or above for servers. - On a client,
slmgr /atocompletes without an error dialog. slmgr /dlion that client reports Licence Status: Licensed.- The client’s Application log shows a 12289 with the activation flag set to 1.
- 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 I lower the 25-client threshold?
No. It is enforced by the licensing service and Microsoft publishes no setting that changes it. The documented remedies are to add machines to the pool or to use a different activation method.
Do servers count towards the client threshold?
They contribute to the same count, because the host keeps one cumulative pool across operating systems. What differs is the threshold applied: a client edition needs 25, a server needs 5. So five servers alone will not get a desktop over the line, but they are not counted in a separate tally either.
Do virtual machines count?
Yes. Both published thresholds include virtual machines. There is no separate, lower threshold for a virtual estate.
How long does the count stay up once it is reached?
The host counts machines that have contacted it in the last 30 days and stores the 50 most recent. As long as clients keep renewing on their seven-day cycle, the count holds. Take a large batch out of service and it will fall back below the threshold about a month later.
What happens to clients while the count is too low?
They sit in the initial 30-day grace period and retry every two hours. Nothing breaks straight away. If the grace period runs out before the count is met, Windows moves to notification mode.
