Windows activation: OOB updates fix SLMGR error 0x80041008

Checked 14 November 2026. After Windows updates released on 10 November, Microsoft documented an error in certain SLMGR activation tasks. Commands could stop with 0x80041008 – Invalid parameter, mainly in organizations that install activation keys or change KMS settings through slmgr.vbs or automation. On 13 November, Microsoft released version-specific out-of-band (OOB) updates to correct the issue.

Key takeaway

Do not install an arbitrary KB from this list. Identify the system edition and version first, then use only its matching Microsoft update: Windows 11 23H2 uses KB5136483; Windows Server 2025, KB5136489; Server 2022, KB5136487; Windows 10 ESU or LTSC 2021, KB5136493; Server 2019 or Windows 10 LTSC 2019, KB5136490. Before central deployment, check each KB’s servicing-stack, prerequisite and, where applicable, checkpoint requirements.

What happened, and who is affected?

Microsoft says certain activation and KMS-management tasks could return 0x80041008 after the 10 November security updates. Examples include installing a product key or changing a KMS domain setting. This concerns a specific administrative workflow; it does not mean Windows is deactivated on every device.

Already activated devices remained activated. Existing KMS configurations that needed no further SLMGR commands were not considered affected. SLMGR is a built-in command-line tool for managing activation, mainly used in managed environments and scripts rather than as a routine step on every personal PC.

Which KB matches each version?

This is a quick match, not a full deployment procedure. Microsoft lists prerequisites for each update. For example, Windows 11 23H2 and Server 2022 require a Windows update from 8 July 2025 or later and the latest SSU. Server 2025 has a minimum servicing-stack version; Catalog packages may also require checkpoint MSUs in a specified order. Offline images can have further conditions.

Choose the update safely

1. Identify the system: Record Windows version, edition, architecture and current build. “Windows Server” alone is not enough to select a KB.
2. Confirm the symptom: Check whether it occurs during an SLMGR task Microsoft describes, such as installing an activation key or changing KMS details. Do not change a working setup pre-emptively.
3. Read the matching KB: Check prerequisites, Servicing Stack Update (SSU), architecture, deployment channel, restart guidance and offline-media notes.
4. Roll out in stages: Test on a small representative group first. If using Catalog MSUs, install any checkpoint packages in the order specified by Microsoft.
5. Verify and record: Confirm the installed KB and build, then repeat only the documented administrative task that failed. Keep error logs and record rollout scope.

OOB does not automatically mean security update

“Out-of-band” describes a release outside the usual schedule. The cited KB pages classify these fixes as non-security cumulative OOB updates. The label alone does not mean a new security issue exists or set urgency for every system. Microsoft says OOB fixes may be included in later cumulative updates. Whether to deploy now or in the next regular window depends on the system version, observed error and maintenance plan.

Context for the November rollout

Include activation scripts in pilot checks after monthly updates, especially on server and client fleets that change product keys or KMS parameters through SLMGR. For another November package, see our separate article about KB5132061 and checkpoint packages. It covers a different update and does not replace the OOB KB pages above.

For production environments with centralized activation management, an administrator should assess the impact on the organization’s update process. A public KB example does not replace checking the fleet’s actual versions and installation media.

Sources and methodology

Checked 14 November 2026. KB mapping, builds, affected versions and installation notes were checked against Microsoft’s support pages. The OOB and SLMGR explanations use Microsoft Learn. Microsoft listed no known issues on the cited OOB pages at the time of review; check the current change log before production deployment.

• Microsoft: KB5136483 for Windows 11 23H2
• Microsoft: KB5136489 for Windows Server 2025
• Microsoft: KB5136487 for Windows Server 2022
• Microsoft: KB5136493 for Windows 10 ESU and LTSC 2021
• Microsoft: KB5136490 for Server 2019 and Windows 10 LTSC 2019
• Microsoft: November update issue details for Windows 10
• Microsoft Learn: OOB update guidance
• Microsoft Learn: SLMGR management options

Video check: We found no official Microsoft video covering this specific correction and KB selection that added practical detail beyond the version-specific support pages, so no video is embedded. Author: TechDesk PE Digital.Networks.