Skip to content

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

Your vault is empty.

License Error 0xC004F035

Office 0xC004F035: a volume key on a machine with no volume entitlement

11 min read Updated October 5, 2026 Office & Microsoft 365 Licensing

Fix it now

Microsoft publishes this code in the Windows activation error list, where it means the device has no qualifying licence to put a volume key on top of: you need a qualifying operating system licence plus a volume upgrade licence, or a full retail licence. There is no separately published Office meaning, so read it the same way and license the device in its own right.

Run the first in an elevated Command Prompt and the second in elevated PowerShell

slmgr /dli
(Get-CimInstance -ClassName SoftwareLicensingService).OA3xOriginalProductKey
  1. For Office, read the channel from cscript ospp.vbs /dstatus in the Office folder instead. A licence description naming a volume or KMS client channel on a device with no agreement is the answer.
  2. The PowerShell line reads a manufacturer licence embedded in firmware. An empty result means there is none, which is exactly the situation the published text describes.
  3. If the device is in scope of an agreement and other machines on it activate, stop here. That is an infrastructure fault, not this one, and the next section separates them.
  4. If it is not in scope, remove the volume key: slmgr /upk for Windows, or cscript ospp.vbs /unpkey:<last five> for Office, then install the licence the device is actually covered by.

slmgr /upk leaves the machine unlicensed after a restart until a new key is installed. Have the replacement ready before you run it.

If the correct licence activates, you are done. If you hold an agreement and the device should be covered, the next section explains which of the five situations you are in.

Why it happens

Microsoft’s published text for 0xC004F035 is unusually blunt, and worth reading in full before anything else: “Invalid Volume License Key. In order to activate, you need to change your product key to a valid Multiple Activation Key (MAK) or Retail key. You must have a qualifying operating system license AND a Volume license Windows 7 upgrade license, or a full license for Windows 7 from a retail source.” An older Microsoft page words the same code more generally, as the computer not being activatable with a volume licence product key.

The version names in that text are historical, and the principle behind it is not. Windows volume licences are upgrade licences. They assume the device already carries a qualifying licence underneath, typically the manufacturer’s licence recorded in firmware. A volume key handed to a device with nothing underneath is refused, and that refusal is a licensing statement rather than a software fault.

One thing needs saying plainly because it changes how you read the rest. Microsoft publishes this code for Windows. There is no Office-specific description for it anywhere on learn.microsoft.com or support.microsoft.com. Office volume licensing runs on the same Software Protection Platform and can surface the same codes, but if you have this in an Office context you are reading across from documentation written about Windows, and you should treat the specifics as Windows specifics.

For Office the analogous gap is the agreement rather than a firmware licence. A volume key belongs to an agreement covering a defined set of devices or users, and a machine outside that set has no entitlement however correct the key looks. The two companion codes, 0xC004F012 and 0xC004F022, have no published descriptions at all.

A Windows volume upgrade key on a machine with no qualifying licence

You have this one if A self-built PC, a bare virtual machine or a machine reinstalled from generic media refuses a key that works on the business laptops next to it.

  1. Check for a manufacturer licence in firmware: (Get-CimInstance -ClassName SoftwareLicensingService).OA3xOriginalProductKey in elevated PowerShell. An empty result means there is none.
  2. If there is none, the device needs a full licence rather than an upgrade: slmgr /ipk <key> then slmgr /ato.
  3. For virtual machines, license through the host entitlement where the host licensing permits it, rather than applying an upgrade key per guest.

The device is not covered by the agreement the key belongs to

You have this one if The key came from an employer, a former employer, a client or a friend’s organisation, and this is not one of that organisation’s devices.

  1. Remove the key: cscript ospp.vbs /unpkey:<last five> for Office, or slmgr /upk for Windows.
  2. License the device in its own right, then install and activate the new key.

Volume agreements are counted and audited. A key on a device the agreement does not cover creates an exposure for the organisation that owns the agreement, not for the device.

The device is in scope and the activation infrastructure is not reachable

You have this one if You do hold an agreement, the device is covered, and other machines on the same agreement activate normally.

  1. For Office: cscript ospp.vbs /sethst:kms.contoso.local then cscript ospp.vbs /act.
  2. For Windows: slmgr /skms kms.contoso.local:1688 then slmgr /ato.
  3. Test the path from the client subnet: Test-NetConnection kms.contoso.local -Port 1688 and read TcpTestSucceeded.
  4. For directory-based activation, confirm the device can see the object with slmgr /ao-list.

An in-scope device failing where others succeed is an infrastructure problem, and it is the one branch of this article that costs nothing to resolve.

The agreement has lapsed, or the seats are used up

You have this one if Activation worked historically and has stopped across several devices at once.

  1. Check the agreement status and the deployment count in your volume licensing portal.
  2. Bring the agreement current, or reduce deployments to the number you hold.
  3. Re-run activation on the affected devices once the position is corrected.

A volume key was sold to you as a single licence

You have this one if You paid for what was described as a licence and received a volume key with no agreement and no documentation.

  1. Treat it as a bad purchase and open a refund. Volume agreements cannot be divided into single seats and sold on.
  2. Remove the key, then buy and activate a licence appropriate to one device.

This overlaps with keys that are later blocked outright. A volume key offered as a single perpetual licence is a warning sign in itself.

Full reference

Which situation applies to this device

Situation What the device actually needs
Personal machine, key borrowed from an employer Its own licence. The agreement does not extend to it
Business machine out of scope, or a lapsed agreement To be brought back into scope, or its own licence
Custom-built PC with a Windows volume upgrade key A full Windows licence; there is no qualifying licence to upgrade from
Virtual machine with no host entitlement Licensing through the host, or its own licence
Volume key bought as a single licence online A legitimate licence; a split volume key is not one
In-scope device, other devices activate fine Nothing bought. Fix the path to the KMS host or the directory object

The commands, and what each of them costs you

Command What Microsoft says it does
slmgr /dli Displays licence information for the installed edition
slmgr /upk Uninstalls the product key. After a restart the system is unlicensed unless a new key is installed
slmgr /cpky Removes the product key from the registry. Not required for MAK and KMS host keys, where clearing is already the default
slmgr /ipk <key> Installs a key after confirming it is valid and applicable to the installed operating system
slmgr /ato Attempts activation now
slmgr /ao-list Displays all activation objects available to the local computer
cscript ospp.vbs /unpkey:<last five> Uninstalls an installed Office key by its last five digits

slmgr /upk and cscript ospp.vbs /unpkey: both take the machine out of an activated state. Have the replacement key in hand first, and do not do it on a machine somebody is depending on that day.

Reading a firmware licence

(Get-CimInstance -ClassName SoftwareLicensingService).OA3xOriginalProductKey returns the manufacturer key embedded in firmware, or nothing. On a device that shipped with Windows there is usually a key there; on a self-built machine or a plain virtual machine there is not. That single line separates the two most common versions of this problem faster than any amount of licence archaeology, and it changes nothing on the machine.

What the two companion codes are

0xC004F012 and 0xC004F022 have no published descriptions. They appear alongside 0xC004F035 and are routinely given confident meanings by articles that have no source for them. Read what your own machine says with slui.exe 0x2a 0xC004F012 for Windows, or cscript ospp.vbs /ddescr:0xC004F012 for Office, and treat that as the authority.

Before you buy anything

  1. Establish whether an agreement exists at all, and whether this device is inside it. That is a question for whoever owns the agreement, not for the machine.
  2. If it is inside, prove the activation path: DNS record, TCP 1688, the host or the directory object. Fixing that costs nothing.
  3. If it is outside, decide whether to bring it into scope or license it separately. For one or two devices, separate licences are usually simpler than amending an agreement.
  4. For Windows on a machine with no firmware licence, price a full licence rather than a base licence plus an upgrade. For a single machine, the combination is rarely the cheaper route.

When a licence is the actual fix

Where a device sits outside any agreement, the honest position is that it has never been licensed and no command changes that. For a single machine needing the core Office applications with no agreement to administer, Office LTSC 2024 Standard fits: perpetual, tied to the device, installed with /inpkey: and activated in one step, with no KMS host or directory infrastructure behind it. Arco supplies Office LTSC licences and can look at what your users actually run before recommending Standard or Professional Plus. If several devices are in the same position, we can also say at what point a small volume agreement becomes the better shape.

Every code this article covers

Code What it points at Source
0xC004F035 Invalid volume licence key: the device needs a qualifying operating system licence plus a volume upgrade licence, or a full retail licence. Published for Windows; there is no separate Office description Microsoft Learn
0xC004F012 Returned from the same licensing layer. No published description not published by the vendor
0xC004F022 Same layer, no published description not published by the vendor

Confirm the fix worked

  1. cscript ospp.vbs /dstatus for Office, or slmgr /dlv for Windows, reports a licensed status.
  2. The channel shown matches the licence you now hold, not the one you removed.
  3. The Windows activation page, or the Office application, reports no unlicensed state.
  4. For an in-scope device, Test-NetConnection <host> -Port 1688 from the client subnet returns TcpTestSucceeded True.
  5. Reboot and re-check, since slmgr /upk takes effect at restart and a half-finished change shows up there.

Questions people ask about this

Is this an Office code or a Windows code?

Microsoft publishes it in the Windows activation error list only. Office volume licensing runs on the same platform and can surface it, but there is no Office-specific published description, so read the Windows text and apply the principle rather than the version names in it.

Why does the same key work on my work laptop?

Because that device is covered by the agreement the key belongs to, and for Windows it also carries a manufacturer licence in firmware. The key is identical; what sits underneath it is not.

Can I add the qualifying licence afterwards?

For Windows, in principle yes. In practice, for a single machine, a full licence is usually simpler and no more expensive than a base licence plus an upgrade.

Is using my employer’s key on my home PC a real problem?

Yes. The agreement defines which devices are covered and deployments are counted. A device outside it creates an exposure for your employer at their next true-up or review, and the exposure is theirs rather than yours.

What do 0xC004F012 and 0xC004F022 mean?

Microsoft does not publish descriptions for them. Read your own machine’s text with slui.exe 0x2a for Windows or cscript ospp.vbs /ddescr: for Office, and do not rely on a gloss from an article that cannot cite the vendor.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Office 0xC004F001: the licensing service hits an internal error License Error Office 0xC004B001: the activation server says the licence is invalid Free Fix Office 0x8004FC12: activation fails after a Windows upgrade Free Fix Office 30102-11: an operating system fault or low disk space stops setup
← Back to Knowledge Base