Fix Windows Activation Error 0xC004F074 on Windows 10, 11, and Server

Ok so the 0xC004F074 activation error comes up a lot. Client called me a week ago, middle of dinner, her Dell Latitude on Windows 11 Pro decided it wasn’t activated anymore. She’d done nothing, just rebooted after an update. Screenshot in the text message showed 0xC004F074. I’ve dealt with this specific error maybe 30 or so times over the past couple years and finally got annoyed enough to dump everything I know into one article. Nobody should spend an hour googling this. Here’s the error text for SEO purposes and also because half the time the error dialog gets closed before you screenshot it: “The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted.” The bit about KMS is misleading btw, the error fires on home PCs that never had anything to do with KMS. What follows is my actual workflow, in the order I run through it, not whatever Microsoft’s KB recommends.

Quick video walkthrough if you prefer watching over reading. FIXsage covers the basic Windows 10/11 fix here:

Quick Reference: 0xC004F074 Activation Error at a Glance

Detail	Info
Error Code	0xC004F074
Full Message	The Software Licensing Service reported that the computer could not be activated. No KMS could be contacted.
Affected Systems	Windows 10, Windows 11, Windows Server 2016/2019/2022/2025
Primary Cause	KMS activation server unreachable or wrong key type installed
Fastest Fix	Reinstall product key with slmgr /ipk then slmgr /ato
Microsoft KB	KB 974998

What Actually Causes the 0xC004F074 Activation Error

Read this before you do anything. Seriously. Last thing you want is to flush DNS 3 times and reboot when your actual problem is a dead CMOS battery. Four buckets of causes, ranked by how often I run into each one:

KMS server unreachable. Maybe 6 out of every 10 cases I see. Your box tries to connect to a Key Management Service host over TCP port 1688 and the packet goes into the void. Firewall rule somewhere dropped it. Or a VPN grabbed outbound 1688 and routed it wrong. Or (the nasty one) sppsvc on the KMS host crashed and nobody set up alerting for it. Happened to me on a client’s Hyper-V cluster last March. Took me an hour to find because nothing external showed the service was down.

Wrong product key type. Retail key but Windows thinks KMS, or KMS but Windows thinks retail. Weird stuff that happens post-update. The 24H2 Windows 11 cumulative was horrible for this. I had like 4 laptops through my bench in December all hit this, all Home editions, none had ever touched a domain network. Go check the HP Support forum thread titled something like “24H2 VOLUME_KMSCLIENT notification mode” if you want to see hundreds of people with the exact same problem. Microsoft hasn’t officially acknowledged it afaik.

Clock drift. System clock more than 4 hours off from whatever the KMS expects = quiet activation failure. No useful error. No “hey your clock is wrong” message. Just 0xC004F074. Sub-error in Event Viewer for the timing case is 0xC004F06C if you wanna check. Usual suspects: dead CMOS battery on desktop, a VM cloned off an old snapshot, a laptop that sat in a closet for 10 months after someone quit.

DNS. Activation client needs to find its KMS host through a DNS SRV record (_vlmcs._tcp specifically). If that record is missing or stale, activation fails. This is strictly a corporate network thing. Home users, skip this cause, your router has no idea what a KMS host is and that’s fine.

First Step: Check Your Activation Channel

Before doing anything, figure out what license you actually have right now. Skip this and you might reinstall a retail key on a KMS channel and still hit the 0xC004F074 activation error. Open CMD as admin:

slmgr.vbs /dlv

Two things matter in the output. The Description line, it’ll say RETAIL channel, OEM_DM channel, or VOLUME_KMSCLIENT channel. And the License Status, licensed, notification mode, or unlicensed. Screenshot this. Seriously. If the fix goes sideways you’ll want to compare before and after.

Retail key on a home PC but the channel says VOLUME_KMSCLIENT? Windows update flipped you. Go to fix #1.

On a company network, channel says VOLUME_KMSCLIENT, and activation fails? Different problem entirely. Skip ahead to fix #5.

Fix #1: Reinstall Your Product Key with slmgr

Start here. This one alone solves maybe 8 out of 10 0xC004F074 activation error cases I run into. Open Command Prompt with admin rights (on Win11 it’s Terminal Admin from the right-click Start menu, on Win10 it’s Command Prompt Admin, same idea). You’re going to run three commands:

1. slmgr.vbs /upk pulls the current key out of Windows
2. slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX puts yours back in. Use your real key obviously, 25 chars total with the 4 dashes. No quotes. Spaces don’t matter but I’d keep the standard formatting.
3. slmgr.vbs /ato tells Windows to go activate now

Reboot once it’s done. Then Settings > System > Activation. Top of that page should say “Windows is activated” in green-ish text. If yes, you’re done, close the tab, have a nice day.

Don’t have your key handy? Happens. Hit Win+R, type slui 3, Enter. That pops a cleaner GUI where you can paste from a screenshot or wherever you wrote it down. Saves you from typing 25 characters manually into CMD (which I’ve fat-fingered more times than I’ll admit).

Activation still throwing errors even with the right key? Try slui 4. That opens phone activation. You get a 54-digit installation ID split into 9 groups of 6. Call the number Windows gives you. Automated system, no human, punch the digits in with your keypad. It reads back a confirmation ID you type into the dialog. Tedious. Takes maybe 5 minutes. Works when Microsoft’s online activation servers are having a bad day.

Fix #2: Sync Your System Clock

Clock off by more than 4 hours, activation dies. That’s it, that’s the rule. Common triggers for the 0xC004F074 activation error in this scenario: CMOS battery died on a desktop you haven’t touched in a while, or you cloned a VM from a snapshot and the clock inside the VM is two years behind, or you dug out an old laptop from a drawer. Before you do anything, glance at the clock in the taskbar. Obviously wrong? Bingo, you found it.

Force sync from admin CMD:

w32tm /resync /force

Or if you’d rather click through GUI, Settings > Time & Language > Date & time. Two toggles, “Set time automatically” and “Set time zone automatically”, flip both on. Should snap to correct within half a minute once Windows reaches NTP.

Occasionally w32tm fails with something like “the time provider is not registered.” The Windows Time service itself got corrupted somehow. Rebuild it:

net stop w32time
w32tm /unregister
w32tm /register
net start w32time
w32tm /resync /force

Then retry slmgr.vbs /ato.

Fix #3: Flush DNS and Reset Network

DNS being broken means your PC can’t find the KMS host even though it’s sitting right there on the network. Classic way to hit the 0xC004F074 activation error in a corporate environment. Happens mostly in office setups. Home users, this one rarely applies to you, but I’ve seen it go wrong after bouncing between Wi-Fi networks or disconnecting from corporate VPN without properly logging out.

Standard network reset sequence in admin CMD:

ipconfig /flushdns
ipconfig /registerdns
ipconfig /release
ipconfig /renew

If you’re on a domain, you should also check the SRV record itself is resolvable:

nslookup -type=srv _vlmcs._tcp

If nothing comes back, the record is missing or broken in your DNS. That’s a conversation with whoever runs your Active Directory. On home PCs this command always returns nothing, don’t panic, you’re supposed to have no KMS SRV record. If you’re at home, go back to Fix #1, DNS isn’t your problem.

Fix #4: Run the Activation Troubleshooter

Microsoft built an activation troubleshooter into Windows. Does it fix the 0xC004F074 activation error? Sometimes yes, sometimes it just sits there doing nothing. Takes 10 seconds to run so I always click it between other fixes. Zero downside to trying.

Windows 11 path: Settings > System > Activation. Click the “Troubleshoot” button near the top.

Windows 10 path: Settings > Update & Security > Activation. Same “Troubleshoot” button.

What the tool is actually good at is digital license problems, especially post-hardware-change. If the wizard offers you “I changed hardware on this device recently”, click that option, sign in with the Microsoft account you originally used to activate Windows, and pick your device from the list it shows. Works pretty often for that specific scenario.

Being straight with you, KMS activation problems? This tool almost never fixes those. It’s meant for consumer digital license stuff. Runs maybe 20% success rate in my use, but since it’s basically one click I keep running it as a first resort.

Fix #5: Check the sppsvc Service and Port 1688 (Enterprise/Server)

If you’re a home user you can skip this section entirely, your PC doesn’t care about a KMS server. This bit is specifically for sysadmins troubleshooting the 0xC004F074 activation error on a Windows Server box or on domain-joined workstations that activate through KMS.

Jump on the KMS host (not the client). Run PowerShell as admin. Check whether the licensing service is even alive:

Get-Service sppsvc

Status line says Stopped? Problem found. Start it:

Start-Service sppsvc

While you’re at it, make sure it’s set to start automatically with the machine so this doesn’t bite you again after the next reboot:

Set-Service sppsvc -StartupType Automatic

Now go back to the client that was failing. Test port connectivity to the KMS host:

Test-NetConnection -ComputerName YOUR-KMS-HOST -Port 1688

What you want: TcpTestSucceeded: True in the output. Got False instead? Something between the two machines is dropping the traffic. Walk through the usual blockers in this rough order of likelihood. Windows Firewall on the KMS host (way more common than on the client). Actual network firewall appliance between your subnets. Azure NSG or AWS Security Group rules if it’s a cloud VM. Windows Firewall on the client itself (least common, but happens).

One Azure gotcha burned me pretty good once. Your Windows VMs in Azure are set up with forced tunneling, meaning all outbound traffic gets hairpinned through your on-prem VPN gateway. Guess what? Your on-prem firewall has no rules for Azure’s internal KMS endpoint at kms.core.windows.net because it didn’t even know that endpoint existed. Traffic dies in your own datacenter. Fix laid out in KB 974998, you basically need a NAT Gateway attached to the subnet, or outbound rules on a Standard Load Balancer, so Azure KMS traffic has a path out that doesn’t go through your on-prem infrastructure.

Fix #6: Firewall Workaround for the 0xC004F074 Activation Error

Not thrilled to recommend this but it’s the fastest way to confirm whether firewall is the culprit. Buys you 30 seconds of diagnosis time, then you turn it right back on. Don’t forget that part, turning it back on I mean, I’ve seen enough “why is my PC infected” threads that started with “I disabled my firewall to fix an issue and forgot about it.”

Control Panel > Windows Defender Firewall > “Turn Windows Defender Firewall on or off” (left sidebar link). Switch off all three profiles, Domain, Private, Public. Save. Run slmgr.vbs /ato.

Activation worked? Great. Flip the firewall back on right now. Then go into advanced settings and add an outbound allow rule for TCP 1688 specifically so this works with the firewall enabled. Activation still fails with firewall off? Wasn’t the firewall, turn it on, move to the next fix.

Third-party antivirus is suspect number two. Kaspersky, Norton, Bitdefender, ESET, McAfee, all the paid suites have aggressive outbound filters as part of their web shield modules. Don’t disable the whole product. Just the web shield or network protection feature. Retry slmgr /ato. If that works, the AV is blocking activation traffic, go into its settings and add an exception for either the Windows licensing process or the KMS host you’re talking to.

Fix #7: Run SFC and DISM to Repair System Files

Made it this far and nothing worked? Probably corrupted system files causing the 0xC004F074 activation error. A botched Windows Update can wreck the licensing DLLs and sppsvc then refuses to start properly. System File Checker finds and fixes this. DISM is the bigger hammer if SFC can’t.

Admin CMD, kick off the scan:

sfc /scannow

This takes a while. Usually 8 to 15 minutes, longer on mechanical drives. Grab coffee, check your email, whatever. When it finishes look at the last line. If it tells you it “found corrupt files and successfully repaired them”, reboot immediately and try slmgr /ato. Sometimes SFC alone is enough to fix this.

If SFC says it found nothing or couldn’t fix everything, DISM is next:

DISM /Online /Cleanup-Image /RestoreHealth

Also slow. Downloads clean copies of system files from Microsoft’s update servers to replace damaged ones. Reboot after that too. Last try: slmgr.vbs /ato.

Windows Server has its own DISM-based activation recovery path that’s slightly different. Wrote that one up separately: how to activate via DISM on Windows Server.

Check the Event Log for Activation Clues

Genuinely don’t understand why none of the other guides for the 0xC004F074 activation error mention the Event Log. Windows is literally writing down exactly why activation failed in there every time it fails, you just need to know where to look. Win+R, type eventvwr.msc, hit Enter. In the tree on the left expand Windows Logs > Application. Up top there’s a “Filter Current Log” option, use that to filter by Event ID 12288.

Every single activation attempt logs a 12288 event. Inside each event there’s an Info line with the real sub-error code, which is usually more descriptive than the top-level 0xC004F074. If you see 0xC004F06C in the Info line, that’s the clock-off-by-4-hours error, fix your time. See 0xC004F074 repeated in the sub-error with no further info, that literally means the KMS host didn’t send any reply at all, which points at network or DNS.

Server side, if you run the KMS host, look at the Key Management Service log on that machine for Event ID 12290. Every time a client hits your KMS host, the host logs a 12290 with details on whether activation worked. No 12290 events around the time the client was trying to activate? Means the request never made it to the host. That’s either DNS (client couldn’t resolve the host name) or firewall (request got dropped in transit).

One time I burned an entire afternoon on a Server 2022 box that wouldn’t activate clients. Checked DNS, checked firewall, checked NSGs, checked the clients themselves. Nothing. Eventually opened Event Viewer on the KMS host out of desperation. sppsvc had crashed at 11:47 AM that morning and never restarted. Quick Start-Service sppsvc and every client activated in seconds. Now I check Event Viewer immediately after running slmgr /dlv. Saves a ton of time.

Quick PowerShell Diagnostic Script

Here’s something I copy-paste from a text file when I first look at a machine throwing the 0xC004F074 activation error. It runs 5 diagnostics in one shot, no need to type 5 different commands:

Get-Service sppsvc | Select Status; cscript C:\Windows\System32\slmgr.vbs /dlv; w32tm /query /status; nslookup -type=srv _vlmcs._tcp 2>$null; Test-NetConnection -ComputerName kms.core.windows.net -Port 1688

Admin PowerShell, paste it, hit enter. Output comes back in 5 chunks. First chunk is the sppsvc service status, should say Running. If it says Stopped, there’s your problem already, go start it. Second chunk is full license details, look at the Description line for your channel (RETAIL vs VOLUME_KMSCLIENT). Third chunk is time sync health, look at the “Last Successful Sync Time” line. Fourth is DNS SRV lookup, empty output on home PCs is expected and fine. Fifth is a TCP reachability test to Microsoft’s Azure KMS endpoint, useful as a check even on home machines since some ISPs block outbound port 1688 (seen it exactly twice, both on weird regional ISPs). For corporate users, replace the last hostname with whatever your internal KMS is called.

0xC004F074 Activation Error After a Hardware Change

New motherboard, new CPU, or enough RAM/disk changes at once? That’ll do it. Windows ties activation to a hardware hash, motherboard and CPU are the biggest weighted components. Change too much, Windows sees a “new” machine and yanks the license.

If you linked your license to a Microsoft account before the swap, this is easy:

1. Settings > System > Activation
2. Click “Troubleshoot”
3. Pick “I changed hardware on this device recently”
4. Sign in with the account tied to your license
5. Select your device from the list, reactivate

Never linked it to a Microsoft account? Then you’re on the phone. slui 4, call the number, explain the hardware swap. Reactivation usually happens within a few minutes. Microsoft support is actually reasonable about this.

Disable Fast Startup (Edge Case Fix)

Weird one. Genuinely thought I was losing my mind the first time I ran into it. Windows Fast Startup is that hybrid shutdown Microsoft added back in Windows 8 that makes boot feel faster by saving the kernel state to disk instead of doing a full shutdown. Helpful feature most of the time. On some laptops though it messes up the load order for background services, and sppsvc sometimes doesn’t come up cleanly. Result: activation fails with 0xC004F074 until you do a real shutdown.

Not something I’d bet on but it does happen. Three laptops I know of personally where Fast Startup caused the 0xC004F074 activation error. ThinkPad T480 my buddy bought refurbished. Dell Latitude 7490 at a client office. HP EliteBook 840 G7 I was rebuilding for a family friend. All laptops, zero desktops, zero VMs. Might not be your issue but it’s the last thing to try before throwing your hands up.

How to kill it: Control Panel (the old one, not Settings). Power Options. Click “Choose what the power button does” on the left side. At the top of that page there’s a link “Change settings that are currently unavailable” with a little shield icon, click it. Now scroll down and uncheck “Turn on fast startup (recommended)”. Save changes.

Now do a genuine shutdown, not restart. Start menu, Power, Shut Down. Wait for the machine to fully power off. Physical power button to turn it back on. Once you’re booted, run slmgr.vbs /ato. If activation works now, leave Fast Startup disabled permanently, you’ll lose about 2 seconds of boot time on an SSD which nobody notices.

0xC004F074 Activation Error with Microsoft Office

Worth mentioning before we wrap up. This error isn’t exclusive to Windows, volume-licensed Office 2016 and Office 2019 installs throw the exact same 0xC004F074 when their KMS activation fails. Microsoft has a dedicated KB for it separate from the Windows one. Same underlying problem though, client can’t reach the KMS host.

Office uses its own activation script called ospp.vbs instead of slmgr. Admin CMD, cd into your Office installation folder (usually C:\Program Files\Microsoft Office\Office16 for 64-bit Office 2016 or 2019), then:

cscript ospp.vbs /act

If it fails with 0xC004F074, the troubleshooting steps are identical to Windows: check port 1688 to the KMS host, confirm sppsvc is running, verify DNS, check the clock. Office-specific thing to also check though, the Office Volume License Pack on the KMS host has to match or exceed the Office version on the client. If someone is still running a 2013-era Office VLP on their KMS server and a user installs Office 2019, that pair won’t activate. Upgrade the VLP on the KMS host. Microsoft’s docs specifically call out the cohosted 2013+2016 scenario on Server 2008 R2 / Windows 7 as a known broken setup.

Related Activation Errors

If your error code is slightly different, here is how they compare:

Error Code	Meaning	Key Difference from 0xC004F074
0xC004F074	No KMS could be contacted	Network/DNS/service issue (this article)
0xC004C003	Product key blocked	The key itself is invalid or revoked, not a connectivity issue
0xC004F038	KMS count too low	KMS host exists but does not have enough clients (need 25 for Windows, 5 for Server)
0x8007232B	DNS name does not exist	The SRV record is completely missing from DNS
0xC004F050	Invalid product key	Key format is wrong or does not match any Microsoft product

See 0xC004C003 in the logs instead of 0xC004F074? Completely different problem. Your key is blocked or revoked on Microsoft’s side. No troubleshooting will bring it back, you need a new key. 0xC004F074 means the key is fine but the connection isn’t.

Registry Fix for the 0xC004F074 Activation Error

For people who want to poke around in regedit, Windows keeps the licensing config at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform. The interesting value there is KeyManagementServiceName. That’s the hostname the client is currently trying to reach for KMS activation. Decommissioned your old KMS host 2 years ago but the registry value still points at it? The 0xC004F074 activation error fires forever until someone updates it.

Don’t actually need to touch regedit for that. slmgr /skms overrides it:

slmgr.vbs /skms your-kms-host.domain.com:1688

Then slmgr.vbs /ato. This bypasses DNS auto-discovery entirely. Useful in a corporate environment where DNS is messed up but you already know your KMS host’s FQDN.

The Windows 11 24H2 Update Problem

Own section because this one got a lot of people in late 2024 and early 2025. After the 24H2 cumulative, some home PCs flipped from a retail digital license to VOLUME_KMSCLIENT channel. Confirm it with slmgr /dli. If your home PC shows “VOLUME_KMSCLIENT channel,” you got hit.

The HP Support Community thread on this is a horror show. Laptops that had been activated for a year suddenly in notification mode, VOLUME_KMSCLIENT channel, no warning. wmic path softwarelicensingservice get OA3xOriginalProductKey returned empty, Windows wasn’t even reading the OEM key baked into the BIOS anymore.

What actually works, in order:

1. Activation Troubleshooter first (Settings > System > Activation > Troubleshoot), it re-reads the digital license in a bunch of cases
2. Know your key? Reinstall with slmgr /ipk YOUR-KEY
3. Digital license on a Microsoft account? Use the “I changed hardware” option in the troubleshooter even if you didn’t change hardware. Weird hack, works a lot
4. None of that worked? Call the OEM (HP, Dell, Lenovo, whoever). If your laptop shipped with Windows, they can usually restore the original license entitlement

0xC004F074 Activation Error on Windows Server

Server 2016, 2019, 2022, 2025, all affected. On Server this almost always comes back to KMS infrastructure breaking somewhere. Client can’t reach the host, full stop.

Run through this in order:

• Is sppsvc running on the KMS host? (This is the silent killer)
• Port 1688 open between client and host? Test-NetConnection is your friend
• DNS SRV record _vlmcs._tcp resolving to the right host?
• KMS host version old enough to not support the client? Server 2008 KMS host can’t activate Windows 11 clients without updates. Known issue
• Clock difference between client and host under 4 hours?
• Does the KMS host have the activation threshold met? (25 client machines for Windows, 5 for Server. Under that and KMS refuses to activate anything)

Using MAK (Multiple Activation Key) instead of KMS? Different flow, MAK keys talk to Microsoft directly, skip KMS entirely. slmgr.vbs /ipk YOUR-MAK-KEY then slmgr.vbs /ato. If that fails it’s a connectivity issue to Microsoft, not to your KMS.

0xC004F074 Activation Error Without a Product Key

PC had a digital license at some point and you can’t find any key anywhere? Check if it got linked to your Microsoft account. Head to the activation settings, hit Troubleshoot, sign in with your MS account. Takes maybe 30 seconds.

Need a fresh key? Your options, from most expensive to least: Microsoft Store direct (full retail price, instant), Amazon or Newegg (usually cheaper, couple bucks off), or a reseller like us for a Windows 11 Pro key at a steeper discount. Whatever you do, skip the random “free activation key generator” sites, they’re either selling stolen volume keys that’ll get revoked in 3 months, or they’re running a crack script that phones home to Microsoft and flags your machine. Not worth the risk for what amounts to $20 saved.

We keep a page of free Windows 10 and Windows 11 generic keys that’s worth bookmarking. Important: those are Microsoft’s official installation keys. They let you install Windows, pick Pro vs Home during setup, and get the OS running. They don’t permanently activate anything. You still need a paid license for that. But they’re useful if you’re rebuilding a machine and don’t want to buy a key until you’re sure the install works.

All slmgr Commands You Might Need

Command	What It Does
slmgr.vbs /dlv	Shows detailed license info (channel, status, key type)
slmgr.vbs /dli	Shows basic license info
slmgr.vbs /xpr	Shows activation expiration date
slmgr.vbs /upk	Uninstalls the current product key
slmgr.vbs /ipk KEY	Installs a new product key
slmgr.vbs /ato	Forces online activation attempt
slmgr.vbs /cpky	Clears product key from registry (security measure)
slui 3	Opens the “Change product key” GUI
slui 4	Opens phone activation wizard

When to Contact Microsoft Support

Tried everything and still stuck with the 0xC004F074 activation error? Time to bring in Microsoft. They can verify your key against their database, reset activation on their backend, or hand you a replacement key if yours got wrongly blocked. It’s not a premium support thing, it’s free, just slow.

Two ways in: the Get Help app (just search “Get Help” from Start) or the Microsoft Support site. slui 4 for phone activation is often faster than chat if you just need the key activated, not a whole troubleshooting session. Automated system, no hold time, takes maybe 5 minutes total.

One thing I learned the hard way: if your key keeps failing and you keep retrying, stop. Microsoft’s servers throttle repeated activation attempts from the same key within a short window. Walk away for a few hours, come back, try once. Spamming slmgr /ato 15 times in 10 minutes is how keys get temporarily locked.

Frequently Asked Questions

What does 0xC004F074 activation error mean?

Windows tried to phone home to activate and got nothing back. The Key Management Service (KMS), Microsoft’s or your company’s, didn’t respond. Root cause is usually network, a wrong key type, a clock that’s 4+ hours off, or the licensing service being dead on the KMS host.

How do I fix 0xC004F074 activation error on Windows 10 or 11?

Admin CMD, three commands: slmgr.vbs /upk to drop the current key, slmgr.vbs /ipk YOUR-KEY to put yours back, slmgr.vbs /ato to activate. If those don’t cut it, flush DNS, sync the clock, run the Activation Troubleshooter. Works 9 out of 10 times.

Can 0xC004F074 happen with a genuine retail product key?

Yeah, all the time. Not just a “pirated Windows” error. Genuine retail keys hit this after Windows updates, hardware swaps, or firewalls blocking activation traffic. The 24H2 update broke activation on a lot of totally legit home PCs.

Does 0xC004F074 affect Windows Server?

Yes, all supported versions, 2016, 2019, 2022, 2025. On Server it’s almost always infrastructure: sppsvc stopped on the KMS host, TCP 1688 blocked, or the KMS host is too old to activate newer clients.

What is the slmgr /ato command?

“Activate online.” Run slmgr.vbs /ato from an admin CMD and Windows immediately tries to reach Microsoft’s servers (or your KMS host) to activate. Usually the last command you run after reinstalling a product key.

Why did 0xC004F074 activation error appear after a Windows update?

Certain cumulative updates, 24H2 being the big one for Windows 11, flip the activation channel from retail to VOLUME_KMSCLIENT. Your PC starts looking for a KMS server that doesn’t exist. Fix: reinstall your retail key with slmgr /ipk.

How do I check if my Windows key is retail or KMS?

Admin CMD, slmgr.vbs /dlv. Look at the Description line. “RETAIL channel” = retail key. “VOLUME_KMSCLIENT channel” = KMS/volume. Home users should see RETAIL. Seeing VOLUME_KMSCLIENT on a personal laptop? Something flipped your channel, probably the 24H2 update.

Last updated: April 2026