Fix it now
Microsoft’s published text for this code says it plainly: to activate you need a valid Multiple Activation Key or retail key, because a volume licence requires a qualifying operating system licence underneath it. The activation service looked for that underlying entitlement and did not find one.
slmgr /dli
DISM /Online /Get-CurrentEdition
wmic bios get serialnumber
- Read which channel the installed key belongs to from
slmgr /dli, and the edition actually running from the DISM output. They are often not the same product. - On a branded PC, check whether a firmware licence is present at all:
(Get-CimInstance -ClassName SoftwareLicensingService).OA3xOriginalProductKeyin elevated PowerShell. A blank result means nothing is there to read. - If there is no qualifying licence, install a full licence for the base edition first:
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXXthenslmgr /ato. - Only once the base edition is genuinely activated, install the volume or upgrade key and activate again.
The WMI property in step two is widely used and is not listed in Microsoft’s published SoftwareLicensingService class reference. Treat a blank result as a prompt to check with the manufacturer rather than as proof.
If the machine activates on a full licence, you are done. If you want to know what the qualifying test is actually checking, the next section covers it.
Why it happens
Volume-licensed Windows client editions are sold as upgrades, and part of that is enforced in the activation stack rather than only in the contract. Microsoft’s published error text for 0xC004F035 says you must have a qualifying operating system licence as well as a volume upgrade licence, or a full licence from a retail source, and that any other installation is outside your agreement. The machine is what fails the test; the key and the agreement are usually fine.
Microsoft’s OEM activation article puts the same code in concrete terms. It describes 0xC004F035 appearing when a computer uses the ACPI_SLIC table in its BIOS and that table holds no valid Windows marker – either because the marker is corrupted or because it was never there. That is the shape the qualifying-licence test takes on branded hardware: the firmware is asked whether this machine was ever licensed, and it answers no.
Which is why the three situations that produce this code look so different from each other. A self-built machine has no firmware marker because nobody wrote one. A branded machine that had one has lost it, usually with the board. And a machine that never lost anything can still fail if the key being installed is an upgrade key and the installation is clean. 0xC004F061, which Microsoft’s knowledge base covers as the failure returned when activating with an upgrade product key, is the code that names that last case directly.
0xC004F033 and 0xC004F07D turn up alongside these and Microsoft publishes no meaning for either. Read them as the licensing service declining a key on this installation, and diagnose from the edition and the channel rather than the digits.
The machine has never held a Windows licence
You have this one if A self-built PC, a barebones unit, or a machine bought without an operating system. The firmware key query returns nothing and there is no earlier activation on this hardware.
- Accept that no configuration change creates an entitlement nobody bought.
- Install a full licence for the edition you want to run:
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX. - Activate:
slmgr /ato, and confirm withslmgr /dlv. - If the machine also has to sit under a volume agreement for management purposes, apply the volume key afterwards, on top of the now-licensed base.
This is the most common cause of the code and it is a purchasing question rather than a technical one. Everything else in this article is about ruling it out.
The firmware marker is gone after board or BIOS work
You have this one if A branded machine that used to activate itself, until a motherboard was replaced or the firmware was reflashed.
- Check the serial the firmware reports:
wmic bios get serialnumber. Default or placeholder text is the signal. - If the board was replaced under warranty, go back to the manufacturer. Microsoft’s documented resolution for the neighbouring BIOS code is exactly that: ask the OEM to update the firmware with the correct serial number or service tag.
- If a digital licence was linked to a Microsoft account before the change, sign in and run the troubleshooter from Start, Settings, System, Activation.
- If neither applies, the OEM entitlement went with the old board and the machine needs a licence of its own.
The key is upgrade-only and the installation is clean
You have this one if 0xC004F061 accompanies the failure, and the same key activated other machines that already had Windows on them.
- Install and activate the base edition with its own full licence first.
- Then install the upgrade key:
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX. - Activate again with
slmgr /ato. - Confirm the edition and channel afterwards with
slmgr /dlv.
The key does not match the edition on disk
You have this one if The key installs but no matching licence is found, or the key is refused outright.
- Read the current edition with
DISM /Online /Get-CurrentEdition. - Compare it against the edition your key was issued for. Enterprise, Education, Pro and the long-term servicing variants use different key ranges.
- Either install the key that matches what is running, or change the edition to match the key you hold.
- Reactivate and confirm with
slmgr /dli.
Full reference
Matching the situation to what is actually missing
| Situation | What is missing |
|---|---|
| New build, blank disk, key installs but will not activate | No licence has ever existed on this hardware |
Branded PC, and wmic bios get serialnumber returns placeholder text |
The firmware identity was lost, usually with the board or a reflash |
| The machine ran licensed Windows before it was reimaged | An entitlement may exist; check the firmware and any linked Microsoft account first |
| 0xC004F061 rather than 0xC004F035 | The key is an upgrade key used on a clean installation |
| Enterprise entitlement on a device running Home | Enterprise applies on top of Pro; Home is not a qualifying base for it |
Commands, and what each one settles
| Command | What it answers |
|---|---|
slmgr /dli |
Which key is installed, and on which channel |
slmgr /dlv |
The same with more detail, including licence status |
DISM /Online /Get-CurrentEdition |
Which edition is actually running |
DISM /Online /Get-TargetEditions |
Which editions this installation can be moved to |
wmic bios get serialnumber |
Whether the firmware still reports a sane machine identity |
slmgr /ipk <key> |
Installs a key, validating it against the installed operating system |
slmgr /ato |
Attempts activation now |
slmgr /upk |
Removes the installed key. The system is Unlicensed after restart until a new key is installed |
slmgr /upk leaves the machine unlicensed. Microsoft’s own description is that the system enters an Unlicensed state after restart unless a new product key is installed. Do not remove a working key until the replacement is in front of you.
What the qualifying test is not
- It is not a registry flag. It reads the licence store and the firmware, so registry edits change what nothing is looking at.
- It is not fixed by reinstalling Windows. A reinstall does not create an entitlement; it only helps where a firmware licence or a linked digital licence already exists for setup to pick up.
- It is not fixed by a different volume key. A generic volume client key is precisely the kind of key that triggers this, so trying another one produces the same result.
- It is not a network problem. The check happens locally against the licence store and the firmware.
Old stickers and old entitlements
A certificate of authenticity sticker on a case tells you what the machine was sold with. It is not what Windows reads, and on modern hardware there is often no printed key at all. Free upgrade offers that once carried older licences forward have long finished, so treat an old sticker as history rather than as an entitlement for what is on the machine now.
Deciding whether this costs you anything
- If the machine is a branded PC and the fault followed a warranty repair or an OEM firmware update, go back to the manufacturer first. Restoring firmware identity is their operation, and it costs you nothing.
- If a digital licence was linked to a Microsoft account before the hardware changed, try the activation troubleshooter from Start, Settings, System, Activation.
- If the machine genuinely never had a licence, you are buying one, and no amount of troubleshooting changes that.
- If you already hold a full licence for the base edition, install and activate that first, then layer the volume key on top.
When a licence is the actual fix
This is one of the few activation errors where a licence really is the fix rather than a workaround. A volume or upgrade key cannot manufacture the base entitlement it is designed to sit on top of, so a machine with no qualifying licence needs a full one. Arco supplies Windows 11 Pro volume licences as well as the base licences that have to sit underneath them, and can tell you which of the two your situation calls for. Send the output of slmgr /dlv along with the result of wmic bios get serialnumber, and it is usually one look to say whether you are a base licence short or simply holding the wrong key – and if the machine is in warranty, the answer may be to talk to the manufacturer instead.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC004F035 |
Invalid volume licence key: activation requires a qualifying operating system licence as well as the volume upgrade licence, or a full licence from a retail source. On OEM hardware Microsoft ties it to the ACPI_SLIC table holding no valid Windows marker | Microsoft Learn |
0xC004F033 |
The licensing service declining the key on this installation. No published meaning; diagnose from the edition and channel | not published by the vendor |
0xC004F061 |
Microsoft’s knowledge base covers this as the failure returned when a copy of Windows is activated using an upgrade product key | Microsoft Support |
0xC004F07D |
Another licence-installation refusal in the same area. No published meaning; read it with the key channel and the edition in view | not published by the vendor |
Confirm the fix worked
slmgr /dlvreports Licence Status: Licensed and the description names the edition and channel you expect.- Start, Settings, System, Activation reports the machine as activated with no remediation link offered.
DISM /Online /Get-CurrentEditionmatches the key you installed.- Reboot and re-check, so you know the state survives a restart rather than sitting in a grace window.
- If you layered a volume key on top of a full licence, confirm the channel in
slmgr /dliis the one you intended.
Questions people ask about this
Can I get around this with a registry edit or a generic key?
No. The check reads the licence store and the firmware rather than a registry value, and a generic volume client key is exactly the kind of key that triggers the error. Anything claiming to bypass it is either changing nothing or leaving the machine in a state that fails again at the next validation.
Does an old Windows 7 or Windows 8 licence still qualify?
The free upgrade offers that once carried older licences forward are finished. Treat a sticker from that era as evidence of what the machine once ran rather than as a licence for what is on it now.
What does this cost to fix?
It depends on whether the entitlement exists. If a branded PC lost its firmware licence during a warranty repair, the manufacturer should restore it and it costs you nothing. If the machine genuinely never had a licence, you are buying one.
Will reinstalling Windows clear the error?
Not on its own, because a reinstall creates no entitlement. It helps only where the machine has a firmware licence or a linked digital licence that setup picks up automatically, which the firmware checks tell you before you start.
I get 0xC004F061 instead. Is that the same problem?
It is the same family with a sharper cause. Microsoft covers 0xC004F061 as the failure returned when activating with an upgrade product key, so the answer is to license and activate the base edition first and then apply the upgrade key on top of it.
