What does HRESULT 0xC004F011 (SL_E_LICENSE_FILE_NOT_INSTALLED) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The Software Licensing Service reported that the license file is not installed.

Previous	Next
SL_E_INVALID_PKEY	SL_E_VALUE_NOT_FOUND

SL_E_LICENSE_FILE_NOT_INSTALLED

Where this result is produced

SL_E_LICENSE_FILE_NOT_INSTALLED is HRESULT 0xC004F011. It belongs to the local Software Protection Platform. Its narrow boundary is: the expected license file is not installed in the local licensing repository.

Windows reports “The Software Licensing Service reported that the license file is not installed”.

Minimum diagnostic record

license/package identity, version, digest and dependency	Which signed package or dependency was evaluated, and does its version or digest match the expected product state?
Code-specific distinction	Does the evidence support “identify the package by Activation ID and reinstall it from supported media” rather than a file that exists but contains an invalid package?

How to reproduce the same condition

Capture license/package identity, version, digest and dependency.
Before remediation, confirm that the failure is not instead the neighboring condition: a file that exists but contains an invalid package.
Record 0xC004F011, UTC time, caller and the first method or server request that returned it.

REM Evidence context: SL_E_LICENSE_FILE_NOT_INSTALLED
cscript %windir%\system32\slmgr.vbs /dlv
powershell -NoProfile -Command "Get-CimInstance SoftwareLicensingProduct | Where-Object PartialProductKey | Select Name,ApplicationID,ID,LicenseStatus,LicenseStatusReason,PartialProductKey"

Do not merge these conditions

Result	Different condition
`SL_E_VALUE_NOT_FOUND`	a requested key/value item is absent from the selected licensing object or policy store
`SL_E_RIGHT_NOT_GRANTED`	the evaluated licenses do not grant the requested right to run or use the feature
`SL_E_MISMATCHED_SECURITY_PROCESSOR`	the license targets a different security-processor implementation or version than the one running

A focused reproduction for this exact result

Control	Design
Failing fixture	Image customization removes a required.xrm-ms license file.
Single variable	Change only one protected file or language resource against a known-good component-store copy.
Positive control	The repaired file hash matches the expected build while licensing inputs stay constant.
Different result	If the experiment instead proves “a requested key/value item is absent from the selected licensing object or policy store”, diagnose that condition separately rather than treating it as this HRESULT.

Recovery without broad resets

To correct this using supported mechanisms, identify the package by Activation ID and reinstall it from supported media.

Technical references

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