Fix Error 0xC004F074: Windows Activation Without KMS
Error 0xC004F074 appears when Windows tries to activate and no KMS (Key Management Service) server answers. In the overwhelming majority of cases, the machine is carrying a volume licence key — the kind used to activate hundreds of PCs inside a company — without being connected to any organisation’s activation server. On a personal computer, no command will make that server appear out of thin air: you either restore contact with it, or you install a key that is valid for a standalone machine. Here is how to work out which situation you are in, in about thirty seconds, and how to fix it properly.
What error 0xC004F074 actually means
The full message is refreshingly clear: “The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted.” A volume licence does not check in with Microsoft. It checks in with an internal KMS host, discovered through a DNS SRV record (_vlmcs._tcp) and reached on TCP port 1688. What it grants is not a permanent activation but a 180-day lease, renewed silently every 7 days.
The documented causes are always the same handful:
- a GVLK (KMS client) key installed on a home PC, usually through a modified installation image or an “activator”;
- a work machine that has left the network: remote work without the VPN, a laptop kept after leaving the company, a refurbished PC resold with its old key still inside;
- a KMS host switched off or renamed, or a _vlmcs._tcp DNS record that no longer exists;
- port 1688 blocked by a firewall or a network policy;
- an obsolete KMS address forced manually at some point, a clock that has drifted, or a KMS host still sitting below the threshold of 25 client machines.
The fixes, from the simplest to the most decisive
1. Put the clock right and run the troubleshooter
Open Settings > Time & language > Date & time, switch on automatic time and time zone, then click Sync now. Activation requests are timestamped, so a clock that is hours or days out is enough to break the exchange on its own. Next, head to Settings > System > Activation: if a Troubleshoot button is showing, run it. Reboot, then check again. It is a two-minute detour, and on a machine that is genuinely licensed it occasionally ends the story right there.
2. Find out which key is actually installed
Right-click the Start menu, open Terminal (Admin), and run slmgr /dlv. The window that pops up reports the product key channel, and everything hinges on that one line.
| What slmgr /dlv shows | What it means | What to do next |
|---|---|---|
| Volume:GVLK (VOLUME_KMSCLIENT) | KMS client key, unusable outside a corporate network | Step 3, or step 4 on a personal PC |
| Volume:MAK (VOLUME_MAK) | MAK volume key, activates without any KMS | Run slmgr /ato again; if it still fails, the quota is exhausted |
| RETAIL or OEM_DM | Consumer key: this error code is abnormal here | A KMS address has been forced — see step 3 |
3. Work machine: restore contact with the server
If the PC really is covered by a volume licence agreement, the job is simply to give it access to the KMS host again. From an administrator terminal:
- reconnect to the internal network, or bring up the VPN;
- check DNS discovery with nslookup -type=srv _vlmcs._tcp, adding your domain if the short form returns nothing;
- test the port in PowerShell: Test-NetConnection kms.company.local -Port 1688. A False result points at a firewall rule or a server that is down;
- clear a stale address with slmgr /ckms, or force the correct one with slmgr /skms kms.company.local:1688;
- retry with slmgr /ato, confirm with slmgr /dlv, and if you need the detail, open Event Viewer and read the Application log filtered on the Security-SPP source.
If you have since left the company, or the PC was handed down to you, that key is no longer yours to use. Move on to step 4.
Key permanently blocked, or nowhere to be found?
There is no point losing hours over it: a brand-new, genuine licence costs less than €10 and lands in your inbox within 5 minutes. Windows 11 Pro at €9.90 — instant activation, lifetime guarantee.
4. Personal PC: swap the volume key for one that works
On a standalone machine this is the only clean way out. Everything below runs in an administrator terminal:
- slmgr /upk uninstalls the current key, and slmgr /cpky wipes it from the registry;
- slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX installs the new one. A Pro key on a Home installation will switch the edition over; the other way round, it is simply refused;
- slmgr /ato activates online, and slmgr /xpr confirms the result: “The machine is permanently activated.”;
- if online activation fails despite a correct key, slui 4 opens phone activation and slui 3 lets you type the key in again.
The other codes in this family are covered in our guide to Windows and Office activation errors, and if the replacement key is rejected as well, our page on what to do when a Windows product key is not working runs through the remaining checks.
5. The same error in Office? Reach for ospp.vbs
Volume editions of Office return 0xC004F074 for exactly the same reason, and slmgr has no say in it — Office keeps its own activation tool. Open an administrator command prompt in the Office folder (usually C:\Program Files\Microsoft Office\Office16, or the Program Files (x86) equivalent on a 32-bit install) and run cscript ospp.vbs /dstatus. A licence described as KMS_CLIENT confirms the diagnosis. From there, cscript ospp.vbs /sethst:kms.company.local followed by cscript ospp.vbs /act re-points a corporate machine at its server, while cscript ospp.vbs /unpkey:XXXXX (the last five characters of the installed key) and then cscript ospp.vbs /inpkey: with a proper key gets a home installation back on its feet. If Office is showing a yellow banner instead of a code, our unlicensed product fix covers that case step by step.
6. If an “activator” has been used on this PC
Let us be blunt about what those tools actually do: they install a GVLK key and run a fake local KMS server, kept alive by a scheduled task. The day your antivirus removes it, or a Windows update breaks the emulator, or the 180-day lease quietly runs out, 0xC004F074 comes straight back. It is not a licence in any meaningful sense — no right of use, no support, no guarantee, and most of those executables insist that you switch off your protection before they will even run. Cleaning up takes three commands — slmgr /upk, slmgr /cpky, slmgr /ckms — followed by a full antivirus scan and a real key.
If nothing has worked
Let us be clear about one thing: with 0xC004F074 the key is not necessarily dead. It simply has nowhere to activate, and no command in Windows can manufacture a KMS server. That said, genuinely dead keys do exist — a MAK key whose activation quota has run out, a key revoked after a contract was terminated or after it was distributed en masse, a key that came out of an activator in the first place. Neither slmgr /ato, nor slui 4, nor a clean reinstall will change any of that.
Which leaves two ways out. Legitimate case, a company machine under an active agreement: your IT department is the only party able to check the state of the KMS host, and Microsoft support is reachable from Settings > System > Activation > Get help. Otherwise, the whole thing is over in a few minutes with a genuine Windows 11 Pro licence at €9.90, delivered by email, covered by a lifetime guarantee and backed by EU-based support. If Office is in the same state on the same machine, Office 2021 Pro Plus is €19.90.
Frequently asked questions
Can I set up a KMS server at home to activate my PC?
No. A KMS host key is only issued under a volume licensing agreement signed with Microsoft, and those are reserved for organisations. On top of that, a KMS host will not activate a single client until at least 25 machines have checked in with it — below that threshold it refuses everything. At home, an individual licence is the only legal route.
Windows had been activated for months. Why is the error showing up now?
Because KMS activation is never permanent: it is a 180-day lease, renewed every 7 days in the background without anyone noticing. The day the computer leaves the network, the server is decommissioned, or the fake KMS left behind by an activator disappears, the lease expires and Windows drops back into notification mode. Nothing changed on your side — the renewal simply stopped happening.
How is this different from 0x8007232B or 0xC004F050?
Three separate failures. With 0xC004F074, no KMS server could be contacted at all. Error 0x8007232B stops one step earlier: the DNS lookup for the KMS host fails, so Windows never finds an address to try in the first place. Error 0xC004F050 has nothing to do with KMS at all — there, the key itself is rejected as invalid, usually because it belongs to a different edition or a different version of Windows, or because a character was mistyped.
Will reinstalling Windows make it go away?
Only if the installation media was the problem. Reinstall from a modified ISO carrying a GVLK key and the error returns the moment activation is attempted. Download the official image from Microsoft, skip the key during setup, then install your own afterwards with slmgr /ipk. Reinstalling on top of a dead or revoked key changes nothing whatsoever.
Is buying a second-hand licence legal in the EU?
Yes. The Court of Justice of the European Union settled the question in its UsedSoft v. Oracle ruling (C-128/11): once a software licence has been sold within the EU for unlimited use, the rights holder’s distribution right is exhausted and that licence can lawfully be resold, provided the first owner stops using it. That is exactly how a genuine pre-owned licence reaches you at €9.90 instead of full retail price — and unlike a GVLK key from an activator, it activates against Microsoft’s own servers, permanently, with no KMS anywhere in the picture.
