Windows Activation Error 0x80041008 After the November 2026 Update: What to Do
Getting 0x80041008: Invalid parameter (SWbemObjectEx) when running slmgr.vbs /ipk or slmgr.vbs /skms-domain? Microsoft has confirmed a Windows activation and licensing issue following the November 10, 2026 security updates. It mainly affects organisations that use command-line or automated KMS and product-key management. It is not the same as a normal Windows digital-licence or account activation problem.
Illustration of the failure pattern, not a captured screenshot.
Do not repeatedly reinstall the product key, reset the Windows licensing store or rebuild the WMI repository. Microsoft says already-activated devices remain activated. If the affected slmgr.vbs operations fail after a November update, record the Windows version, KB number and exact command, then contact Microsoft Support for business for the current mitigation. Microsoft says a resolution is being worked on; its public update notes do not yet provide a general end-user command that fixes this regression.
Your current Windows activation is not expected to disappear just because this command fails. Microsoft says devices that are already activated remain activated. KMS-activated devices typically remain activated for up to 180 days after a successful activation.
Microsoft’s public update notes still say that a resolution is being worked on and direct organisations needing an immediate mitigation to Microsoft Support for business. Citrix’s advisory says Microsoft expected to release a fix by the end of November 13, 2026. Treat that as a reported expectation, not confirmation that the fix has shipped; verify the relevant Microsoft KB and Citrix advisory before changing a production master image or KMS workflow.
Does this apply to you? A two-question check
Most people who see an activation error have a different problem. Answer these two questions before changing anything.
slmgr.vbs /ipk, slmgr.vbs /skms-domain, or a script or deployment task that calls them?What does Windows activation error 0x80041008 mean?
Advertisements
0x80041008 is the WMI error WBEM_E_INVALID_PARAMETER, which means that a parameter supplied to a WMI operation is not accepted. In the November 2026 incident, the error appears in the Windows Software Licensing Management Tool when certain activation, Key Management Service (KMS) or product-key operations are attempted.
- You run
slmgr.vbs /ipkor/skms-domain - Passed toSoftware Licensing WMI provider
- After Nov 10 updateProvider rejects a parameter
- You see0x80041008 Invalid parameter
Microsoft lists the message as “Invalid parameter (SWbemObjectEx)” and specifically identifies the /skms-domain and /ipk operations. The problem is tied to the November 10 security updates, not simply to a mistyped retail product key. Microsoft says the issue primarily affects organisations that automate Windows activation and licensing through command-line tools or scripts.
For reference, Microsoft documents /skms-domain as the option that specifies the DNS domain in which KMS service records are found. The /ipk option installs a Windows product key. See Microsoft’s Slmgr.vbs command reference.
Which Windows versions and November 2026 updates are affected?
Microsoft has added the 0x80041008 known issue to several November 10 update notes. The affected update depends on the Windows product and release. Check the KB number installed on the machine rather than assuming every Windows 11 release is affected.
| Windows product | November 10 update | Microsoft issue note |
|---|---|---|
| Windows 11, version 23H2 | KB5131087 | Activation and licensing commands may return 0x80041008. |
| Windows 10, versions 21H2 and 22H2 | KB5131096 | Activation and licensing commands may return 0x80041008. |
| Windows Server 2019 and Windows 10 Enterprise LTSC 2019 | KB5131085 | Known issue documented in the November update notes. |
| Windows Server 2022 | KB5131090 | Activation and licensing commands may return 0x80041008. |
| Windows Server 2025 | KB5131080 | Activation and licensing commands may return 0x80041008. |
The list above covers the update notes in which the November activation issue is documented. It does not mean every device on those versions will fail. Microsoft describes the impact as affecting certain activation and licensing operations, especially automated or command-line KMS management.
Which slmgr.vbs commands trigger error 0x80041008?
Microsoft specifically identifies these two command patterns:
1. KMS domain configuration fails
slmgr.vbs /skms-domain <domain>This command sets the DNS domain used to discover KMS service records. After the affected November update, the command may return 0x80041008 with the SWbemObjectEx invalid-parameter message.
2. Installing a product key fails
slmgr.vbs /ipk <product-key>This command installs a product key. If it fails with the same error after installing one of the affected November updates, do not assume that the key itself is invalid. Microsoft has documented this as a known Windows activation and licensing issue.
The public known-issue notes identify the two commands above. Microsoft does not say that every Windows activation method, retail licence, Settings activation screen or already-activated PC is broken.
How to handle Windows activation error 0x80041008 safely
There is currently no Microsoft-published universal command sequence that users can run to repair this specific November regression. Microsoft’s update notes say that an immediate mitigation is available through Microsoft Support for business and that a resolution is being developed. Use this order to avoid making a licensing problem harder to diagnose.
Step 1: Confirm the installed November update
- Open Settings and go to Windows Update.
- Open Update history.
- Record the installed November KB number and the installation date.
- Run
winverand record the Windows version and OS build.
Compare the KB number with the affected-update table above. This matters because the November update numbers differ between Windows 10, Windows 11 and Windows Server.
Step 2: Check whether the failed operation is one Microsoft lists
Record whether the failure happened while running slmgr.vbs /ipk, slmgr.vbs /skms-domain, an activation script, a deployment task or a KMS configuration workflow. Keep the exact command and the full error text for your support case. Do not publish or send your complete product key in screenshots or support posts.
Step 3: Avoid repeated key installation and destructive WMI repairs
Trial and error makes this harder to diagnose. Microsoft has not documented any of the actions in the right-hand column as a workaround, and they can create additional servicing or licensing problems.
- Leave already-activated devices as they are.
- Keep the exact command and full error text.
- Keep a pre-update master image snapshot.
- Mask product keys in screenshots and tickets.
- Rerunning the command with different keys or KMS hosts.
- Deleting the WMI repository.
- Resetting licensing files.
- Running unofficial activation scripts.
- Removing the security update only to bypass the error.
Step 4: Contact Microsoft Support for business if the operation is blocking deployment
For organisations that must configure KMS or install keys immediately, Microsoft’s stated workaround is to contact Microsoft Support for business. Include the Windows edition, OS build, installed KB, affected command, error text and whether the device is already activated.
If the machine is already activated and its current KMS configuration is correct, Microsoft says devices that do not need to run the affected commands are not expected to be affected. Avoid unnecessary changes while waiting for Microsoft’s resolution.
Citrix MCS image preparation: Windows rearm failed after KB5131085, KB5131090 or KB5131080
Advertisements
There is a second enterprise symptom worth checking. Citrix has documented Windows rearm failures during Machine Creation Services (MCS) image preparation after the November 10 security updates on Windows Server 2019, Server 2022 and Server 2025 master images.
- MCS startsImage preparation on the master image
- ReadsWindows licensing client machine ID
- After Nov 10 updateWMI provider rejects the query
- ResultOperating System Licensing Rearm failed
Symptoms include:
- “During image preparation, the rearming process for the copy of Windows installed on the master image failed.”
- The Citrix catalog warning
Operating System Licensing Rearm failedorImagePreparationOSRearmFailed. - An image-preparation log showing
System.Management.ManagementException: Invalid parameterwhile reading the Windows licensing client machine ID.
Citrix says this is a Windows-side issue, not a Citrix VDA, hypervisor or cloud-platform defect. Its advisory explains that the Windows Software Licensing WMI provider rejects the query MCS uses to obtain the client machine ID before rearming Windows. Citrix links the change to the November security updates addressing CVE-2026-96300. Microsoft’s public KB confirms the 0x80041008 known issue but does not give this detailed MCS root-cause explanation.
Citrix MCS mitigation while the Windows fix is pending
Citrix advises administrators to contact Microsoft Support for the business workaround or continue using the master-image snapshot created before the November 2026 update, postponing catalog updates that use the affected image until the fix is installed.
After Microsoft makes the fix available, Citrix’s documented sequence is:
- InstallFix on the master image
- Shut downThe master image
- SnapshotTake a new snapshot
- UpdateMachine catalog, then confirm no rearm warning
Citrix warns that machines created from an image that was not rearmed can share the same KMS client machine ID. A KMS host may then count them as a single machine, which can prevent the environment from reaching the KMS activation threshold. Do not roll out newly generated machines from a failed-rearm image without understanding this licensing impact.
Read the full Citrix MCS image-preparation advisory before changing a production catalog.
Is 0x80041008 the same as the KB5132061 99% install loop?
No. They are two separate November 2026 Windows update problems with different error codes and different repair paths.
0x80041008 appears when running specific slmgr.vbs licensing operations after the November security updates.
It affects command-line activation and enterprise licensing workflows.
KB5132061 may fail or repeatedly retry with 0x80070306, 0x800f0989 or 0x800f0993 on a limited number of PCs that installed the October preview KB5127936.
Microsoft says that repair is delivered automatically to affected internet-connected devices using Windows Update in Settings.
For the KB5132061 issue, use our separate KB5132061 install-error guide. It covers the 99% loop, the three update error codes and Microsoft’s automatic repair window. Do not apply the KB5132061 workaround steps to the separate 0x80041008 KMS problem.
Frequently asked questions
Will error 0x80041008 deactivate my already-activated Windows PC?
Microsoft says devices that are already activated remain activated. The known issue mainly affects certain activation and licensing commands. KMS-activated devices typically remain activated for up to 180 days after successful activation.
What does 0x80041008 Invalid parameter (SWbemObjectEx) mean?
It is a WMI invalid-parameter error. Microsoft has documented it when the Software Licensing Management Tool runs certain KMS and product-key operations after the November 2026 security updates.
Which slmgr.vbs commands are affected?
Microsoft specifically lists slmgr.vbs /skms-domain <domain> and slmgr.vbs /ipk <key>. The issue primarily affects organisations using command-line or automated Windows activation and licensing processes.
Does this affect Windows Server 2022 and Windows Server 2025?
Yes. Microsoft lists the November activation issue in the Windows Server 2022 KB5131090 and Windows Server 2025 KB5131080 update notes. It also appears in the Server 2019 KB5131085 and other affected Windows update notes listed above.
Is there a confirmed command to fix 0x80041008?
Microsoft’s public known-issue notes do not provide a universal repair command. For an immediate business mitigation, Microsoft directs affected organisations to Microsoft Support for business. Avoid destructive WMI or licensing-store resets that are not documented as the fix for this issue.
Should I uninstall the November 2026 security update?
Microsoft has not instructed users to uninstall the update as the general workaround for this activation issue. Do not remove a security update solely because an affected slmgr command fails. Ask Microsoft Support for business for the supported mitigation if deployment is blocked.
Why is Citrix MCS showing Operating System Licensing Rearm failed?
Citrix says MCS image preparation can fail to read the Windows licensing client machine ID through the Software Licensing WMI provider after the November updates. Follow Citrix’s advisory, preserve a known-good pre-update master-image snapshot if needed and wait for the Windows fix before regenerating the affected catalog.
Is 0x80041008 related to KB5132061 error 0x800f0993?
No. 0x80041008 is the activation and licensing command issue. KB5132061 installation failures use 0x80070306, 0x800f0989 or 0x800f0993 and have a separate Microsoft automatic repair process.
Official sources and advisories
- Microsoft: Windows 11 23H2 update KB5131087
- Microsoft: Windows 10 update KB5131096
- Microsoft: Windows Server 2019 and Windows 10 LTSC 2019 update KB5131085
- Microsoft: Windows Server 2022 update KB5131090
- Microsoft: Windows Server 2025 update KB5131080
- Microsoft Learn: Slmgr.vbs activation command reference
- Citrix: MCS image preparation fails to rearm Windows after November updates
- Microsoft Security Response Center: CVE-2026-96300
Editorial update: Checked November 13, 2026. Microsoft’s public notes currently describe the issue as known and say a resolution is being worked on. Recheck the Microsoft KB pages before changing production KMS or Citrix MCS workflows, because the documented status may change as the fix rolls out.
