While troubleshooting a Windows Server 2025 system, I encountered an issue that initially looked like a corrupted Windows licensing store or an incorrect KMS configuration.
However, every repair attempt failed.
⚠️ The symptoms
Windows activation stopped working. Even basic licensing management commands failed:
❌ slmgr.vbs /ipk – Install a product key
❌ slmgr.vbs /skms – Configure the KMS server
❌ slmgr.vbs /ato – Activate Windows
The error message:
0x80041008 – Invalid parameter (SWbemObjectEx)
What stood out: the issue affected not only KMS activation itself, but also local Windows licensing management.
🔬 The cause – confirmed by Microsoft
The November 2026 security updates introduced an issue in the Windows Software Licensing WMI Provider.
As a result, certain licensing management operations failed with 0x80041008.
This also explains why our previous repair attempts had no effect.
There was no confirmed corruption of the licensing store, nor was the issue caused by connectivity to the KMS host.
🛠 Microsoft provides the fix
On November 13, 2026, Microsoft released an out-of-band update:
✅ KB5136489 – Windows Server 2025
✅ OS Build 26100.33828
Here is how I would proceed:
1️⃣ Check the installed update:
Get-HotFix -Id KB5136489
2️⃣ Install KB5136489 and restart the server.
3️⃣ Then test licensing management again:
|
1 2 3 4 |
slmgr.vbs /ipk <Product-Key> slmgr.vbs /skms <KMS-Host>:1688 slmgr.vbs /ato slmgr.vbs /dlv |
When installing manually, any required checkpoint updates must also be taken into account.
💡 My takeaway
Not every KMS error is a KMS problem!
If even /ipk and /skms fail with 0x80041008, check the Windows patch level first.
In this case, the cause was the Microsoft update.
A repair installation, deleting tokens.dat or making further changes to WMI was not required to resolve this confirmed issue.
📚 Source: Microsoft KB5136489
https://lnkd.in/e7JfT6hm