| Previous | Next |
| SL_E_VL_NOT_WINDOWS_SLP | SL_E_VL_BINDING_SERVICE_NOT_ENABLED |
SL_E_VL_NOT_ENOUGH_COUNT
What this result narrows down
SL_E_VL_NOT_ENOUGH_COUNT identifies a specific point in volume activation and KMS/ADBA: the volume-activation path that selects KMS, Active Directory-based activation, or another volume channel for a particular Activation ID. Its diagnostic consequence is that the KMS host is reachable but its current unique-client count has not reached the activation threshold required for this product family.
Telemetry should retain 0xC004F038, this result, and the affected Activation ID. The same computer can expose several licensing products, and a state read from the wrong instance can contradict the operation that actually failed.
Two platform rules are especially relevant to this result. A Generic Volume License Key identifies a KMS or Active Directory-based activation client; it is not a retail key and does not activate directly against Microsoft hosted activation services. KMS discovery, KMS-host activation, the client-count threshold, and client renewal are separate checks, while ADBA relies on a suitable activation object in Active Directory.
A useful diagnostic record
To verify this, compare the KMS host Current Count and Required Client Count, inspect recent unique CMIDs, and verify that cloned systems do not share an identity. Before changing the system, add the following context:
- Product identity: slmgr.vbs /dlv output for the exact Activation ID.
- Activation context: installed key channel and partial product key.
- State at failure: KMS host name, port, DNS SRV answer, current count and required count.
- Correlation evidence: client and host UTC time.
- Change history: AD activation object name/DN and domain/schema level.
Choose recovery by the producing stage
| Result | Different condition |
|---|---|
SL_E_VL_BINDING_SERVICE_NOT_ENABLED | Relative to this result: the local or selected volume-activation binding service is disabled for the requested KMS operation. |
SL_E_VL_NOT_WINDOWS_SLP | Different condition: the installed Windows lineage or qualifying-license state does not permit activation with the supplied volume key. |
SL_E_VL_KEY_MANAGEMENT_SERVICE_NOT_ACTIVATED | Different condition: the KMS service exists, but the KMS host key itself has not been successfully activated. |
Work from state to cause
- Select the exact licensing product or Activation ID that returned it; do not rely only on the first line of
slmgr /dlv. - Confirm the mechanism in use: the volume-activation path that selects KMS, Active Directory-based activation, or another volume channel for a particular Activation ID.
- Prove the code-specific condition by collecting: compare the KMS host Current Count and Required Client Count, inspect recent unique CMIDs, and verify that cloned systems do not share an identity.
- Apply the distinction “the host responded; DNS, TCP reachability, and host activation are therefore different from the count-threshold condition” before choosing a key, network, certificate, firmware, time, or entitlement repair.
- Change one relevant precondition, rerun one activation/evaluation operation, and verify the resulting LicenseStatus and LicenseStatusReason.
the host responded; DNS, TCP reachability, and host activation are therefore different from the count-threshold condition. A broad instruction to “try another key” or “check the Internet” would discard the more specific condition already established by the code.
Actions that usually make this harder to diagnose
- Avoid installing an unrelated key merely to force another activation attempt.
- Avoid treating all volume activation failures as DNS or firewall problems.
Recovery without damaging licensing evidence
The appropriate correction is to allow enough distinct eligible clients to request activation, correct duplicate CMIDs in improperly cloned images, and then retry after the count changes. Keep the original evidence until a subsequent status query confirms that the intended Activation ID reached the expected state.
Representative failure: The first few Windows Server clients contact a new KMS host successfully, but the host count is still below the server threshold.
Verification after the change
After remediation, repeat the original operation rather than relying on the absence of a notification banner. Confirm that it is no longer produced and that the intended product instance reports the expected durable licensing state.
Technical references
- Microsoft volume activation overview — platform behavior relevant to this HRESULT.
- Plan for volume activation — diagnostic and operational context.
- KMS troubleshooting guidance — supported tools and state fields used to verify the resulting state.
- SoftwareLicensingProduct WMI class — Microsoft guidance for the activation mechanism represented by this HRESULT.
Looking for a different code? Search another status or error code.