| Previous | Next |
| SL_REMAPPING_MDOLLAR_OSR_NO_ASSOCIATION | SL_REMAPPING_MDOLLAR_OSR_USER_THROTTLED |
SL_REMAPPING_MDOLLAR_OSR_NOT_ADMIN
Where this result is produced
SL_REMAPPING_MDOLLAR_OSR_NOT_ADMIN is HRESULT 0x803FABBB. It belongs to digital-license hardware-change reactivation. Its narrow boundary is: the current user lacks the local administrator context required to complete hardware-change reactivation.
The OS reactivation path compares a previously associated digital entitlement with the current device and signed-in account. It also evaluates administrator status, policy and anti-abuse limits; a failure here does not by itself invalidate the locally installed edition. The code is not interchangeable with an account association failure; the entitlement may be present but the local token is insufficient.
AllStat records “Error code indicating that user not eligible for reactivation because user is not an admin on device” for this HRESULT. That identifies the official outcome; the additional value is the producing object, evidence set, nearby conditions and safe verification path.
Objects and state transitions
| Stage | Role for this HRESULT |
|---|---|
| Previous entitlement | The donor device/license record must exist and be transferable. |
| Account link | The signed-in account association is evaluated independently for this HRESULT. |
| Target eligibility | Edition, hardware, policy and anti-abuse state can each produce the result denial. |
| Commit | No new device association is written while this result remains active. |
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
| Signal | Interpretation |
|---|---|
| Family | The OSR prefix places the result in the digital-license reactivation and transfer workflow. |
| Object | The suffix names the object or transition to inspect before any broad activation reset. |
| Operation | Its HRESULT severity is failure; later status messages can describe only the resulting state. |
| State | The exact first caller and object identity are needed to distinguish a producer error from cleanup noise. |
Minimum diagnostic record
| Evidence | Question answered |
|---|---|
| signed-in account identity in redacted form | For this HRESULT: Which prior device owns the digital entitlement? |
| selected donor-device record and target device | For this HRESULT: Is the signed-in account linked and locally elevated? |
| installed edition and digital-license status | For this HRESULT: Is the denial temporary throttling, policy, or a nontransferable/block decision? |
| local elevation and administrator membership | For this HRESULT: Can caller identity and elevation be captured before changing state? |
| caller identity and elevation | For this HRESULT: Does the evidence support “sign in as an administrator and rerun the supported Activation troubleshooter” rather than an account association failure; the entitlement may be present but the local token is insufficient? |
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.
How to reproduce the same boundary
- Prove the distinction between the named boundary and an account association failure; the entitlement may be present but the local token is insufficient 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.
- Record
0x803FABBB, UTC time, caller and the first method or server request that returned it. - Capture caller identity and elevation specifically for this HRESULT.
REM Evidence context: SL_REMAPPING_MDOLLAR_OSR_NOT_ADMIN
cscript %windir%\system32\slmgr.vbs /dlv
cscript %windir%\system32\slmgr.vbs /xprUse 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.
Do not merge these conditions
| Result | Different condition |
|---|---|
SL_REMAPPING_MDOLLAR_OSR_NO_ASSOCIATION | the signed-in account has no usable association between the selected digital license and prior device |
SL_REMAPPING_MDOLLAR_OSR_USER_THROTTLED | anti-abuse limits temporarily prevent this account from making another reactivation request |
SL_REMAPPING_MDOLLAR_OSR_GENERIC_ERROR | the reactivation service cannot complete eligibility evaluation and returns no narrower OSR reason |
Sort related HRESULTs by timestamp and object/request identity. The first code from the producing layer is usually more actionable than a later summary from Settings, deployment software or a wrapper.
A focused reproduction for this exact result
| Control | Design |
|---|---|
| Failing fixture | A standard user starts transfer of a digital license to the current device. |
| 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 signed-in account has no usable association between the selected digital license and prior device”, 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.
Recovery without broad resets
A supported correction is to sign in as an administrator and rerun the supported Activation troubleshooter. A representative incident is a standard user starts transfer of a digital license to the current device.
Verification for this HRESULT must repeat the original operation for the same product or request scope. Confirm the intended license status, binding, policy, record or server response persists after any required restart.
Changes that make this code harder to diagnose
- avoid selecting unrelated donor devices until one succeeds; it changes evidence without proving the named boundary.
- avoid assuming every digital license can transfer between devices or editions; it changes evidence without proving the named boundary.
- avoid publishing raw account tokens or hardware identifiers; it changes evidence without proving the named boundary.
Technical references
- SoftwareLicensingProduct WMI class — official reference for the mechanism surrounding this result.
- MS-ERREF Windows Error Codes — official reference for the mechanism surrounding it.
- Reactivate Windows after a hardware change
- Use the Windows Activation troubleshooter
Looking for a different code? Search another status or error code.