Slmgr error 0x80041008 is the kind of error that makes you doubt yourself. After the November 2026 Windows updates, a command most of us have typed more times than we can count, slmgr.vbs /ipk, suddenly answers with Invalid parameter (SWbemObjectEx), and so does slmgr.vbs /skms-domain. My first suspects were the key and the KMS host. Neither is the problem. Microsoft has confirmed it as a known issue in the November security updates, and on November 13 it shipped out-of-band updates that fix it. Below is what is affected, which KB you need for each Windows version, how to install it when it is not on Windows Update, and how to check that activation works again.
What Slmgr Error 0x80041008 Looks Like
Microsoft’s known-issue entry in KB5131080 is titled Windows activation and licensing commands might fail with error 0x80041008. According to Microsoft, affected devices might see error 0x80041008, Invalid parameter (SWbemObjectEx), when they run commands to activate Windows, configure Key Management Service (KMS) or manage product keys with the Software Licensing Management Tool. The two commands Microsoft names are:
slmgr.vbs /skms-domain <domain>
slmgr.vbs /ipk <product key>Code language: HTML, XML (xml)
The hex code itself is a WMI code (WBEM_E_INVALID_PARAMETER). slmgr.vbs is a VBScript wrapper around the WMI licensing classes, which is why the message mentions SWbemObjectEx. It is not telling you that your key is wrong, so do not burn an hour retyping it.
Microsoft is clear that this is mostly a problem for organizations that manage activation with command-line tools or automation: imaging task sequences, golden image scripts, post-deployment configuration, MAK key swaps. In plain terms, the slmgr error 0x80041008 bites when something needs to change, not when nothing does.
- Devices that were already activated stay activated.
- Devices that already have the KMS client setup key in the image and do not run further slmgr.vbs commands are not affected.
- KMS-activated devices keep their activation for up to 180 days, so nothing expires overnight.
Which November 2026 Windows Updates Cause Slmgr Error 0x80041008
The problem came with the November 2026 Windows updates released on November 10. For Windows Server 2025 that is KB5131080 (OS Build 26100.33822), where Microsoft added the known issue on November 11. BleepingComputer reported the Microsoft service alert listing Windows 10 21H2 and 22H2, Windows 11 23H2 and Windows Server 2019, 2022 and 2025 as affected. I could not find the issue listed for Windows 11 24H2 or 25H2, and Microsoft did not publish an out-of-band update for them, so treat those versions as unaffected unless Microsoft says otherwise.
You may also have read reports from Citrix admins whose MCS image preparation failed to rearm Windows after the November updates. That issue was reported in the community and is under investigation, but Microsoft’s known-issue text only names /skms-domain and /ipk. I would not assume the slmgr error 0x80041008 fix also covers a rearm failure until Citrix or Microsoft confirms it.
How to Fix Slmgr Error 0x80041008: Install the Out-of-Band Update
Microsoft’s resolution is short: the issue is fixed in Windows updates released on and after November 13, 2026. The Windows message center entry from that day says out-of-band (OOB) updates were released to address licensing and activation errors on a limited number of enterprise devices. Every one of these packages has the same fix note: certain Windows licensing and activation operations using SLMGR might fail with error 0x80041008 (Invalid parameter).
Here is the mapping I put together from the Microsoft KB pages:
- Windows Server 2025: KB5136489 (OS Build 26100.33828)
- Windows Server 2022: KB5136487 (OS Build 20348.5873)
- Windows Server 2019 and Windows 10 Enterprise LTSC 2019: KB5136490 (OS Build 17763.9488)
- Windows 10 22H2 (ESU) and Windows 10 Enterprise LTSC 2021: KB5136493 (OS Builds 19045.7850 and 19044.7850)
- Windows 11 23H2: KB5136483 (OS Build 22631.7714)
Two details matter before you start. First, these are cumulative updates and each one includes the November 10 security update, so you do not lose any security fixes and you do not need to uninstall anything. Second, they are optional non-security releases. For the server versions and Windows 10, Microsoft lists Windows Update and WSUS as not available: you get them from the Microsoft Update Catalog. Windows 11 23H2 is the exception, where KB5136483 also shows up under Settings > Windows Update > Advanced options > Optional updates.

Step 1: Check the Current Build
Before downloading anything, I confirm which build the machine is on. If the update build revision is already at or above the OOB build in the list, the slmgr error 0x80041008 fix is already in place:
$cv = Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion"
"{0} build {1}.{2}" -f $cv.ProductName, $cv.CurrentBuild, $cv.UBR
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5 HotFixID, InstalledOnCode language: PHP (php)Step 2: Download and Install the Package
Search the Microsoft Update Catalog for the KB number of your version and download the .msu file for your architecture. On Windows Server 2022, Windows Server 2019 and Windows 10, a single package does the job. From an elevated PowerShell prompt:
# Example for Windows Server 2022. Change the folder and KB for your version.
$msu = Get-ChildItem C:\Packages -Filter "*kb5136487*.msu" | Select-Object -First 1
Start-Process wusa.exe -ArgumentList "`"$($msu.FullName)`" /quiet /norestart" -Wait
Restart-ComputerCode language: PHP (php)Windows Server 2025 uses checkpoint cumulative updates, and the KB5136489 page lists a checkpoint package (KB5043080) next to the main .msu. Put all the .msu files from the KB page in the same folder and point Add-WindowsPackage at the KB5136489 file. DISM picks up the checkpoint from the folder if the server still needs it:
$msu = Get-ChildItem C:\Packages -Filter "*kb5136489*.msu" | Select-Object -First 1
Add-WindowsPackage -Online -PackagePath $msu.FullName -NoRestart
Restart-ComputerCode language: PHP (php)If you patch through WSUS or Configuration Manager, import the update from the catalog into WSUS (Updates > Import Updates in the WSUS console), then synchronize and deploy it as usual. Because the package is optional and catalog-only, it will not appear on its own, which is why it is easy to conclude that Microsoft has not fixed the slmgr error 0x80041008 yet.
Step 3: Rerun the Failed slmgr Commands
After the restart, run the commands that failed earlier. For a KMS client, that usually means setting the KMS domain or host, installing the generic volume license key (GVLK) for your edition from Microsoft’s KMS client keys list, and triggering activation:
slmgr.vbs /skms-domain corp.example.com
slmgr.vbs /ipk <GVLK for your edition>
slmgr.vbs /atoCode language: HTML, XML (xml)Replace the domain and key placeholders with your own values. If your clients already find the KMS host through the DNS SRV record, you may not need /skms-domain at all, since KMS auto-discovery is the default behaviour. The full list of switches is on Microsoft’s slmgr.vbs options page.
Verify the Slmgr Error 0x80041008 Is Gone
I never call an activation issue closed until I see the license status with my own eyes. These two checks are enough:
slmgr.vbs /dlv
Get-CimInstance SoftwareLicensingProduct -Filter "PartialProductKey IS NOT NULL" |
Format-Table Name, LicenseStatus, KeyManagementServiceMachineCode language: JavaScript (javascript)
slmgr.vbs /dlv should show the license status as Licensed, and in the CIM output a LicenseStatus value of 1 means Licensed. If slmgr error 0x80041008 still appears after the reboot, check the build again with Step 1. In my experience the usual reason is that the package simply did not install, for example because the wrong architecture was downloaded or the server was never restarted.
Slmgr Error 0x80041008 Workaround If You Cannot Patch Yet
Change windows exist, and not every team can push an optional catalog update on a Saturday. Here is how I would handle the slmgr error 0x80041008 in the meantime, based on what Microsoft has said:
- Do not uninstall the November security update. The November 2026 Windows updates fix a long list of vulnerabilities, and this month includes an Outlook zero-day. The OOB package contains it, so moving forward is safer than rolling back.
- Pause automation that changes licensing. Find task sequences and scripts that call
slmgr /ipkorslmgr /skms-domainand hold those steps until the OOB update is in the image or on the machine. - Lean on images that already contain the KMS client key. Microsoft says these devices are unaffected if no further slmgr configuration is needed.
- Need a mitigation today? Microsoft points organizations that need immediate help to Microsoft Support for business. The mitigation itself is not published, so I am not going to guess at it here.
The lesson for me was simple: slmgr is part of the build pipeline, and the pipeline needs a smoke test after Patch Tuesday just like the applications do. A two-line test that runs slmgr /dlv and slmgr /ipk with your GVLK on a test VM catches a problem like slmgr error 0x80041008 in minutes.
Read more: KB5132061 Fails to Install? Proven Fix for Error 0x800f0993
Read more: Windows Update Error 0x800f081f? The Proven DISM Fix
Read more: Kerberos RC4 Failures After Windows Updates? The Proven Fix
FAQ
What causes slmgr error 0x80041008 after the November 2026 updates?
It is a known issue in the November 10, 2026 Windows security updates, such as KB5131080 on Windows Server 2025. Commands like slmgr.vbs /ipk and slmgr.vbs /skms-domain can fail with Invalid parameter (SWbemObjectEx). Microsoft fixed it in out-of-band updates released on November 13, 2026.
Which update fixes slmgr error 0x80041008?
KB5136489 for Windows Server 2025, KB5136487 for Windows Server 2022, KB5136490 for Windows Server 2019, KB5136493 for Windows 10 22H2 ESU and LTSC 2021, and KB5136483 for Windows 11 23H2. All are cumulative and include the November security update.
Why do I not see KB5136489 in Windows Update or WSUS?
The November 13 out-of-band updates for Windows Server and Windows 10 are optional non-security releases available only from the Microsoft Update Catalog. Download the .msu file, or import it into WSUS manually.
Will my already activated servers lose their activation?
No. Microsoft says devices that were already activated remain activated, and KMS-activated devices keep activation for up to 180 days. The problem only affects new activation or licensing changes made with slmgr.
Should I uninstall the November security update to fix the activation error?
No. The out-of-band updates include the November security fixes and resolve the activation error, so installing them is the recommended path. Uninstalling would leave the device without this month’s security patches.
References
Microsoft Support: November 10, 2026 – KB5131080 (OS Build 26100.33822)
Microsoft Support: November 13, 2026 – KB5136489 (OS Build 26100.33828) Out-of-band
Microsoft Support: KB5136487, KB5136490, KB5136493, KB5136483
Microsoft Learn: Windows message center
Microsoft Learn: Key Management Services (KMS) client activation and product keys and slmgr.vbs options for volume activation
BleepingComputer: Microsoft confirms Windows activation failures after November updates






