Skip to content

Est. 2011·Microsoft Partner 7033487·Delivery under 3 min·Support 7 days a week

Your vault is empty.

License Error 0xC004F057

0xC004F057 and 0xC004F063: OEM Licence Missing From Your PC BIOS

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

Fix it now

Microsoft publishes 0xC004F063 as the Software Licensing Service reporting that the computer BIOS is missing a required licence, and attributes it to Windows being unable to read the SLIC table in firmware – most often because the OEM did not update the serial number or service tag after a board replacement. The documented fix is a firmware repair by the manufacturer.

Run these in an elevated Command Prompt

wmic bios get serialnumber
slmgr /dli
  1. Read the serial. Default text, a placeholder or an empty value is the signal Microsoft’s own article points at.
  2. Check whether a firmware key can be read at all: (Get-CimInstance -ClassName SoftwareLicensingService).OA3xOriginalProductKey in elevated PowerShell.
  3. If the board was replaced by the manufacturer, go back to them with the service reference. Restoring firmware licence and identity data is their operation and Microsoft’s documented resolution.
  4. If the machine had a digital licence linked to a Microsoft account before the hardware changed, run the troubleshooter from Start, Settings, System, Activation.
  5. If none of those applies, the OEM entitlement went with the old board and the machine needs a licence of its own.

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 ask the manufacturer, not as proof.

If the manufacturer restores the firmware data and Windows activates itself, you are done at no cost. If not, the next section explains what is actually missing.

Why it happens

Factory-installed Windows does not rely on anyone typing a key. The manufacturer writes licensing data into the machine’s firmware and Windows reads it during installation, which is why a new laptop is already activated the first time it reaches the desktop and why a clean reinstall on the same machine activates itself without being asked for anything.

Microsoft’s article for 0xC004F063 names what is being read: the SLIC table, the Software Licensing Description Table in the BIOS, which validates the OEM key and the manufacturer’s certificate so the machine can self-activate. Its published cause is that Windows cannot read that table, and the three situations it lists are a service tag or serial number the OEM did not update after replacing the motherboard, a BIOS holding a default or meaningless value for the service tag, and a BIOS carrying incorrect product information.

The resolution Microsoft publishes follows directly from that: contact the OEM vendor to update the BIOS with the correct serial number or service tag. This is one of the few activation errors where the documented fix is a hardware vendor’s operation rather than anything you can type, and it is why the diagnostic Microsoft gives is wmic bios get serialnumber rather than a licensing command.

0xC004F057, 0xC004F058 and 0xC004F07C keep this code company and none of them is published by Microsoft. They appear on the same machines in the same circumstances, so read them as the same absence reported from a different point rather than as separate diagnoses.

The board was replaced and the firmware data was not restored

You have this one if An authorised repair, a machine still in warranty, and wmic bios get serialnumber returning placeholder or default text.

  1. Go back to the repair channel with the service reference and state plainly that the firmware serial or service tag was not restored.
  2. Ask them to reinstate it rather than asking for a product key; Microsoft’s documented resolution is a BIOS update on their side.
  3. Re-run wmic bios get serialnumber when the machine comes back, and check activation.

This is Microsoft’s documented case and it costs you nothing when the machine is in warranty. Try it before anything else.

The board was replaced outside warranty

You have this one if The board was changed by you, a repair shop or a parts supplier, and the firmware reports nothing useful.

  1. Confirm the serial really is missing rather than the command failing to run.
  2. Ask the manufacturer whether they can write the correct data for this chassis; some will, for a fee.
  3. Check whether a digital licence was linked to a Microsoft account before the change and try the troubleshooter if so.
  4. If neither route works, license the machine: slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX then slmgr /ato.

An OEM licence is tied to the machine it first activated, which is a large part of why it costs less than a retail licence. Replacing the board is the case that boundary was written for.

A firmware update wrote an image without the data

You have this one if No board change, but a firmware update was applied shortly before activation stopped working.

  1. Check the manufacturer’s support site for a tool or documented procedure that restores licence and identity data after an update.
  2. Do not attempt to write licence data with third-party utilities.
  3. If the vendor cannot restore it, treat the entitlement as gone and license the machine.

There was never a firmware licence to lose

You have this one if A self-built machine, a barebones unit, or a system that shipped with no operating system.

  1. Confirm with the supplier what the machine was sold with.
  2. License the machine for the edition you want to run and activate normally.
  3. Keep the invoice; it is what makes a future reactivation after a hardware change straightforward.

Full reference

What was done, and where that leaves you

What happened Where you stand
The manufacturer replaced the board under warranty They should restore the firmware data. Ask before buying anything
You or a third party replaced the board The OEM entitlement does not transfer to a new board
The vendor’s own firmware utility was used The data may be recoverable with their tooling. Ask them first
The machine shipped without an operating system There was never a firmware licence to lose
A digital licence was linked to a Microsoft account Try the activation troubleshooter first. It costs nothing
The serial reads as placeholder text This is exactly the case Microsoft’s article describes

Commands and checks

Check What it tells you
wmic bios get serialnumber Whether the firmware still reports a real service tag. Microsoft’s own diagnostic for this code
(Get-CimInstance -ClassName SoftwareLicensingService).OA3xOriginalProductKey Whether a firmware product key can be read. Not in Microsoft’s published WMI reference, so treat a blank as inconclusive
slmgr /dli Which key is installed and the current licence status
slmgr /dlv The same with more detail
slmgr /ipk <key> Installs a key, validating it against the installed operating system
slmgr /ato Attempts activation now
Start, Settings, System, Activation Whether Windows reports the machine as activated, and offers the troubleshooter

Stickers, keys and what Windows actually reads

A certificate of authenticity sticker on a case tells you what the machine was sold with. It is not what Windows reads on modern hardware, and on many machines there is no printed key at all. Where a sticker key does exist and is typed in, it may activate and it may not; what it cannot do is restore a firmware table the board no longer holds.

The same distinction applies to the key a tool reads out of firmware. Being able to read a key tells you the firmware still holds licensing data. Being unable to read one tells you rather less than people assume, because the tool may be looking in a place this machine does not use. Microsoft’s own diagnostic here is the serial number, and it is the one worth trusting.

Talking to the manufacturer

  1. Have the service reference for the repair, if there was one, and the machine’s original serial from the chassis label.
  2. State the symptom in their terms: Windows will not self-activate and the BIOS is not reporting the correct service tag or serial.
  3. Ask for the firmware serial or service tag to be restored. This is a documented resolution, not an unusual request.
  4. Ask whether they have a tool you can run yourself, since some vendors publish one for exactly this.
  5. If the machine is out of warranty, ask what it costs. It is often less than a licence.

Reflashing firmware to recover licensing data is not a routine repair. An interrupted or incorrect flash can leave a machine unable to boot at all, and recovery from that point often means replacing the board you were trying to save. Use the manufacturer’s own tooling and procedure, or let them do it.

When the entitlement really has gone

If the board was replaced outside warranty, the manufacturer will not write the data, and no digital licence was ever linked to a Microsoft account, then the entitlement went with the old board and there is nothing left on this machine to repair. That is the case an OEM licence is defined by rather than an unfortunate outcome: it is tied to the machine it first activated, and the price reflects that.

The one thing worth doing before accepting that is checking for a linked digital licence, because it is free and it resolves a fair share of these cases. Sign in with the Microsoft account the machine used, open Start, Settings, System, Activation, and run the troubleshooter. It works only where the licence was linked before the hardware changed, but where it was, it is a two-minute fix.

When a licence is the actual fix

When the board is new, the manufacturer will not restore the firmware data and no digital licence was linked beforehand, there is nothing left on the machine to repair and a licence is the fix. Arco supplies Windows 11 Home OEM keys, which is the right choice where the machine will keep this licence for the rest of its working life. If you expect to move the licence to different hardware later, say so before ordering: a retail licence is the one that transfers, and paying the difference once is better than repeating this exercise. Either way, run wmic bios get serialnumber first and tell us what it says, because a machine in warranty should be going back to its manufacturer rather than to a reseller.

Every code this article covers

Code What it points at Source
0xC004F057 Reported on machines whose firmware licensing data cannot be read. Microsoft publishes no meaning for it; diagnose from the firmware serial and the repair history not published by the vendor
0xC004F058 Seen in the same circumstances as the code above. No published meaning not published by the vendor
0xC004F063 The Software Licensing Service reported that the computer BIOS is missing a required licence. Microsoft attributes it to the SLIC table being unreadable, typically a service tag or serial the OEM did not restore after a board replacement Microsoft Learn
0xC004F07C Another refusal reported on machines in this state. No published meaning not published by the vendor

Confirm the fix worked

  1. wmic bios get serialnumber returns the machine’s real serial rather than placeholder text.
  2. slmgr /dli reports Licence Status: Licensed.
  3. Start, Settings, System, Activation shows the machine activated with no remediation link.
  4. Reboot and re-check, since firmware-backed activation is evaluated again at start-up.
  5. If the manufacturer restored the firmware data, confirm a clean reinstall still self-activates before closing the job.

Questions people ask about this

Does the sticker on the case count as my licence?

Not for activation on modern machines. Windows reads licensing data written into the firmware rather than a printed key, and on many machines there is no printed key at all. A sticker tells you what the machine was sold with; it does not restore what the board no longer holds.

Can I move the OEM licence to the new board myself?

No. The entitlement is tied to the machine it first activated and the licensing data is written by the manufacturer as part of the build. This is the specific case where an OEM licence does not follow the hardware.

Is the troubleshooter worth trying first?

Always, if the machine ever had a digital licence linked to a Microsoft account. Sign in, open Start, Settings, System, Activation and run it. It is free and it resolves a fair proportion of these cases without any purchase.

What is Microsoft’s actual fix for this code?

For 0xC004F063 it is to contact the OEM vendor and have them update the BIOS with the correct serial number or service tag. That is unusual among activation errors and it is why the first diagnostic is wmic bios get serialnumber rather than a licensing command.

What is the difference between OEM and retail?

Transferability rather than function. An OEM licence stays with one machine; a retail one can be moved. Which is better value depends entirely on whether you expect to move it, which is worth deciding before you order.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error 0x8004FE21 and 0x8004FE33: This Copy of Windows Is Not Genuine License Error 0xC004D307: Maximum Rearms Exceeded and the Grace Timer Is Gone License Error 0x803F900A: Your Windows Subscription Expired and Activation Stopped License Error 0x803FABC0 and 0x803FABC2: Device or Licence Blocked From Transfer
← Back to Knowledge Base