What does HRESULT 0x803FA073 (SL_REMAPPING_MDOLLAR_INVALID_PRODUCT_DATA_ID) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The activation server determined the license is invalid.

Previous	Next
SL_REMAPPING_MDOLLAR_MAXIMUM_UNLOCK_EXCEEDED	SL_REMAPPING_MDOLLAR_INVALID_PRODUCT_DATA

SL_REMAPPING_MDOLLAR_INVALID_PRODUCT_DATA_ID

The exact failure boundary

HRESULT 0x803FA073 is exposed as SL_REMAPPING_MDOLLAR_INVALID_PRODUCT_DATA_ID by a remapped activation-service response. The code says more than the friendly message: the product-data identifier in the activation request is unknown or inconsistent with the selected product record.

This family represents a service response translated into the Windows licensing namespace. The server has evaluated at least part of the key, program, binding or entitlement request before returning the result. The code is not interchangeable with a malformed product key string, which is validated independently.

AllStat records “The activation server determined the license is invalid” for this HRESULT. That identifies the official outcome; the additional value is the producing object, evidence set, nearby conditions and safe verification path.

How the request reaches this stage

Stage	Role for this HRESULT
Local request source	Edition, Activation ID, key channel and binding evidence originate on the client.
Service submission	The request carries product/key data and correlation that can be matched to the server decision for this HRESULT.
Entitlement decision	The activation service applies the particular block, range, quota, time-window or mapping rule named by this result.
Response remapping	Windows exposes that remote decision locally as this result; changing client files does not rewrite the server rule.

A later unlicensed, notification or grace-state message describes a consequence. Preserve the earliest event carrying this HRESULT for the same product object or service request.

What the constant itself tells you

The MDOLLAR remapping indicates that the decisive classification originated in an activation-service response.
validation rejected the named object; it was present but not acceptable.
product/key identity must remain tied to the exact SKU and Activation ID.
The suffix names the object or transition to inspect before any broad activation reset.

Inputs worth preserving

Evidence	Question answered
Activation ID, installed edition and activation channel	For this HRESULT: Did the server recognize the key channel and product range?
partial product key and authoritative key source	For this HRESULT: Was the same request accepted previously for this Activation ID?
request UTC time, response HRESULT and service correlation	For this HRESULT: Does the response identify a block, quota, time window or binding rule?
Product ID/configuration data and originating image	For this HRESULT: Can caller identity and elevation be captured before changing state?
caller identity and elevation	For this HRESULT: Does the evidence support “capture the Product ID, Activation ID and edition, then regenerate product data with supported tooling” rather than a malformed product key string, which is validated independently?

Redact full keys, activation blobs, account tokens, private certificate material and raw hardware identifiers. Partial keys, hashes, IDs and UTC timestamps retain correlation value without publishing secrets.

Triage without destroying evidence

Record 0x803FA073, UTC time, caller and the first method or server request that returned it.
Capture request UTC time, response HRESULT and service correlation specifically for this HRESULT.
Prove the distinction between the named boundary and a malformed product key string, which is validated independently before remediation.
After one supported change, repeat the same operation and compare state, events and response correlation for this HRESULT.
Bind this result to the exact Application ID, Activation ID, edition and partial key.

REM Evidence context: SL_REMAPPING_MDOLLAR_INVALID_PRODUCT_DATA_ID
cscript %windir%\system32\slmgr.vbs /dlv
cscript %windir%\system32\slmgr.vbs /ato

Use the status output as evidence. Run an activation retry only after the collected state supports the identified prerequisite; blind retries can add quota, throttle or cleanup noise.

Results that require different fixes

Result	Different condition
`SL_REMAPPING_MDOLLAR_INVALID_PRODUCT_DATA`	the product-data payload fails server-side validation even though the request reached the activation service
`SL_REMAPPING_MDOLLAR_MAXIMUM_UNLOCK_EXCEEDED`	the server has reached the permitted number of unlock or exception uses for this key
`SL_REMAPPING_MDOLLAR_INVALID_ACTCONFIG_ID`	the Activation Configuration identifier does not name a configuration accepted by the service

A focused reproduction for this exact result

Control	Design
Failing fixture	An image carries stale product-data identifiers from a different SKU.
Single variable	Change only the narrow input or state named by the HRESULT while product identity remains fixed.
Positive control	A known-good value at that boundary succeeds and the failing fixture still reproduces the code.
Different result	If the experiment instead proves “the product-data payload fails server-side validation even though the request reached the activation service”, follow that neighboring boundary rather than treating it as this result.

This controlled comparison is stronger than a broad reset because it changes one prerequisite and leaves product identity, evidence source and observation method stable.

Supported correction and proof

A supported correction is to capture the Product ID, Activation ID and edition, then regenerate product data with supported tooling. A representative incident is an image carries stale product-data identifiers from a different SKU.

Changes that make this code harder to diagnose

avoid deleting Tokens.dat to attack a remote rule or quota; it changes evidence without proving the named boundary.
avoid changing network location to evade a regional entitlement; it changes evidence without proving the named boundary.
avoid cycling complete product keys through repeated requests; it changes evidence without proving the named boundary.

Technical references

Slmgr.vbs options — official reference for the mechanism surrounding it.
Plan for volume activation clients
Windows activation error help
MS-ERREF Windows Error Codes

Looking for a different code? Search another status or error code.