Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

License Error 0xC004F059

0xC004F059: The Windows Licence Stored in Your BIOS Is Invalid

12 min read Updated October 5, 2026 Windows Activation & Licensing

Fix it now

Microsoft publishes this as the Software Licensing Service reporting that a licence in the computer BIOS is invalid, and attributes it to no valid Windows marker being found in the machine’s ACPI_SLIC table – the marker is either corrupt or not present. Its documented answer is to move the machine to a key that does not depend on firmware.

Run these in an elevated Command Prompt, in order

wmic bios get serialnumber
slmgr /dlv
slmgr /rilc
  1. Read the serial first. Placeholder or default text means firmware work has changed the machine’s identity, and the manufacturer is the route.
  2. Check the clock while you are there: w32tm /resync. A badly wrong date fails validation on its own and produces a confusing mixture of symptoms.
  3. Rebuild local licence state: after slmgr /rilc, run net stop sppsvc then net start sppsvc, then slmgr /ato.
  4. If the identity strings are placeholder text or belong to another model, contact the manufacturer. Restoring them is a firmware operation with their tooling.
  5. If the firmware cannot be repaired, Microsoft’s documented answer is to activate with a Multiple Activation Key or a retail key instead.

This code is not the same as a missing firmware licence. That is 0xC004F063, and it has a different documented cause and a different fix.

If the machine activates, you are done. If it does not, the next section covers what validation is actually rejecting and what it is not.

Why it happens

On a machine that came from a manufacturer with Windows preinstalled, activation does not depend on anyone typing a key. Licensing data written into the firmware lets the machine self-activate, and Windows validates that data at start-up as well as at install time. This code is that validation failing while data of some kind is present, which is a different situation from the firmware holding nothing at all.

Microsoft’s published text for 0xC004F059 is that the Software Licensing Service reported that a licence in the computer BIOS is invalid, and the cause it gives is specific: no valid Windows marker is found in the ACPI_SLIC table in the computer’s BIOS, because the marker is either corrupted or not present. The same article documents 0xC004F035 in the same way, which is why the two so often appear together on the same machine.

Microsoft’s documented resolution is also worth reading before you start dismantling anything. It is to change the product key to a Multiple Activation Key, obtain one through the Volume Licensing Service Center, or use a retail key – in other words, to stop relying on the firmware. Contacting the OEM is the route where the machine is in warranty and the firmware can be repaired; where it cannot, a key that does not depend on the SLIC table is the answer.

0xC004F060, 0xC004F020 and 0xC004E024 appear alongside this and Microsoft publishes no meaning for any of them. They show up on the same machines in the same circumstances, so treat them as company rather than as separate faults to chase.

Firmware work changed the machine’s identity

You have this one if wmic bios get serialnumber returns placeholder or default text, and activation broke immediately after a firmware update or a board replacement.

  1. Check the manufacturer’s support site for a tool or documented procedure that restores identity and licensing data.
  2. Give them the service tag or serial from the chassis label, since the machine can no longer report it.
  3. Once the strings are restored, run slmgr /ato and confirm activation.

Third-party utilities that claim to write these strings exist. They are not worth the risk on a machine you need working, and they do not restore the licensing data itself.

A replacement board came from a different machine

You have this one if A used or donor board was fitted, some firmware data is readable, and validation still fails.

  1. Ask the supplier whether the board was cleared before resale.
  2. Ask the manufacturer whether the correct data can be written for this chassis.
  3. If neither is possible, follow Microsoft’s documented answer and activate the machine with a Multiple Activation Key or a retail key of its own.

The local licence files are damaged

You have this one if The firmware serial reads correctly, other machines of the same model activate normally, and only this one fails.

  1. Reinstall the system licence files: slmgr /rilc.
  2. Restart the licensing service: net stop sppsvc then net start sppsvc.
  3. Run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth if the scan reports repairs.
  4. Retry activation with slmgr /ato.

The clock is far enough out to fail validation

You have this one if A machine that sat unpowered for a long period, or one with a failed hardware clock, reporting a date well outside the present.

  1. Correct the date, time and time zone by hand if the drift is large.
  2. Run w32tm /resync and confirm with w32tm.exe /query /status /verbose.
  3. Replace the motherboard battery if the clock resets at every power cycle.
  4. Retry activation once the clock is stable.

The edition installed is not the one the firmware covers

You have this one if The firmware data is readable and the installed edition is not what the machine shipped with.

  1. Check the running edition with DISM /Online /Get-CurrentEdition.
  2. Install the edition the firmware entitlement covers, or license the edition you have chosen to run.
  3. Activate and confirm the description in slmgr /dlv names the edition you expect.

Full reference

Reading the evidence

What you find What it points at
The firmware reports no serial and no licensing data at all A different problem: the licence is missing rather than invalid. That is 0xC004F063
Serial or model read as placeholder or default text Firmware work reset the machine’s identity strings
Everything reads correctly and it still fails The local licence files rather than the firmware
The board came from another machine The data belongs to that machine and will not validate here
The system date is wildly wrong Fix the clock before investigating anything else
A different edition is installed from the one it shipped with The firmware entitlement and the installed edition do not match

Commands used here, and what they touch

Command Effect
wmic bios get serialnumber Reads the service tag from firmware. Microsoft’s own diagnostic for the neighbouring BIOS code
slmgr /dlv Detailed licence status, including the description of the installed key
slmgr /rilc Reinstalls licence files from the OEM and token folders under the Windows directory
net stop sppsvc / net start sppsvc Restarts the Software Protection service so it reloads state
w32tm /resync Corrects the clock, which fails validation independently
sfc /scannow Checks and repairs protected system files
DISM /Online /Cleanup-Image /RestoreHealth Repairs the component store when the file check reports damage
DISM /Online /Get-CurrentEdition Reports the edition actually running

Invalid, missing, and why the distinction decides the fix

A missing firmware licence and an invalid one produce different codes with different documented causes. 0xC004F063 is published as the BIOS missing a required licence, with the SLIC table unreadable and a serial the OEM did not restore. 0xC004F059 is published as a licence in the BIOS being invalid, with no valid Windows marker in the ACPI_SLIC table. The practical difference is what you ask the manufacturer for, and whether a repair is plausible at all.

In both cases Microsoft’s documented alternative is the same: stop depending on the firmware and activate the machine with a key of its own. That is worth knowing early, because it means a machine out of warranty with a donor board is not a puzzle to be solved, it is a machine that needs a licence.

Before you conclude the firmware is beyond repair

  1. Confirm the serial is genuinely wrong rather than the command failing to run under a non-elevated prompt.
  2. Confirm the clock. A machine years out of date fails validation for reasons that have nothing to do with firmware.
  3. Rebuild the local licence files with slmgr /rilc and restart the Software Protection service, then retry once.
  4. Check the warranty. A machine in warranty, or one whose fault followed the vendor’s own firmware update, is the vendor’s problem to fix.
  5. Ask the vendor specifically whether they can restore the service tag and licensing data for this chassis, and whether they publish a tool for it.

Reflashing firmware to repair identity or licensing data can leave a machine unable to boot if it is interrupted or the wrong image is used, and recovery from that point usually means replacing the board. Use the manufacturer’s own tooling and procedure, and take a full backup of the disk before starting.

What this code does not tell you

  • It does not say the machine is unlicensed in a legal sense. It says validation of firmware data failed.
  • It does not say the hardware is faulty. A perfectly working board can carry data that does not match the chassis it is in.
  • It does not say a reinstall will help. Setup reads the same firmware and reaches the same conclusion.
  • It does not say your product key is bad. In the ordinary case there is no typed key involved at all.

Buying a used board

This is the practical lesson worth taking away, because it is cheap to act on before the fact and expensive afterwards. A board taken from another machine of the same model carries that machine’s licensing data, and the machine you fit it to will not validate against it. The board may be entirely serviceable and still leave you buying a Windows licence you did not budget for. Ask the supplier whether the board was cleared, and price the repair with a licence included if they cannot say.

When a licence is the actual fix

Where the firmware data cannot be restored, Microsoft’s own documented answer is to activate the machine with a Multiple Activation Key from your volume agreement or with a retail key – that is, to stop depending on the firmware entirely. Arco supplies Windows 11 Pro OEM keys, which suit a machine that will keep this licence for the rest of its working life, and retail keys where you expect to move the licence to different hardware later. Check with the manufacturer first if the machine is in warranty or the fault followed their own firmware update, because restoring identity data is a routine operation for them and costs you nothing. Send the serial and the model strings and it is usually clear within a minute which of the two you are looking at.

Every code this article covers

Code What it points at Source
0xC004F059 The Software Licensing Service reported that a licence in the computer BIOS is invalid. Microsoft attributes it to no valid Windows marker being found in the ACPI_SLIC table, corrupt or absent Microsoft Learn
0xC004F060 Reported on machines in this state. Microsoft publishes no meaning for it; diagnose from the firmware serial and the local licence files not published by the vendor
0xC004F020 Another refusal seen alongside the above. No published meaning not published by the vendor
0xC004E024 Reported with these codes rather than on its own. No published meaning not published by the vendor

Confirm the fix worked

  1. slmgr /dli reports Licence Status: Licensed.
  2. wmic bios get serialnumber returns the machine’s real serial rather than placeholder text.
  3. Start, Settings, System, Activation shows no remediation link.
  4. w32tm.exe /query /status /verbose shows a recent successful sync, ruling the clock out.
  5. Reboot and re-check, since firmware-backed activation is evaluated again at start-up.

Questions people ask about this

Is this the same as a missing BIOS licence?

No, and the distinction decides what you do next. 0xC004F063 is published as the BIOS missing a required licence. This code is published as a licence in the BIOS being invalid, with no valid Windows marker found in the ACPI_SLIC table. One is an absence, the other is data that does not validate.

Can a CMOS reset cause this?

There is no published statement either way. If activation broke straight after one, check the clock and the firmware settings first, since both affect validation, and do not assume the licensing data has gone until the serial tells you so.

The board is from the same model. Why does it still fail?

Because the licensing data is written for one specific machine rather than for a model. A board from an identical unit carries that unit’s data, which validates against that unit and not against yours.

Do I have to buy a licence, or can this be repaired?

Check with the manufacturer first, particularly if the machine is in warranty or the fault followed their own firmware update. Restoring identity and licensing data is routine for them. A purchase is the answer only once that route is closed – and Microsoft’s own documented alternative is a Multiple Activation Key or a retail key.

Will reinstalling Windows help?

No. Setup reads the same firmware data and reaches the same conclusion. Nothing about the installation is what is being rejected.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix 0xC004F047: VAMT Proxy Activation Fails on a Stale Policy Cache Free Fix 0x803FA073 and 0x803FA074: Activation Service Rejects the Product Data Free Fix 0xC004E002 and 0xC004E003: The Windows Licence Store Is Corrupt License Error 0x803FABB8 and 0x803FABBA: Digital Licence Transfer Refused After Rebuild
โ† Back to Knowledge Base