KB5136489: Cumulative update for Windows Server, version 2025, November 2026. Fix addresses certain Windows licensing failures with error 0x80041008
Some organizations can now complete certain Windows licensing and activation operations that previously failed. The fix mainly helps systems that use commands or automated processes to manage KMS activation and product keys.
Does it affect you? Applies to: Devices running Windows Server 2025, with the update package listed for x64 systems.
What changes
Fix 1 change
Licensing and Activation
For: Organizations using licensing commands or automated processes
-
The update fixes certain Windows licensing and activation operations that could fail with error 0x80041008.1
Fixes failures with error 0x80041008 (Invalid parameter) in certain operations using
slmgr.vbs. The issue mainly affected organizations configuring Key Management Service (KMS) activation, installing product keys, or managing Windows licensing through commands or automated processes. Already activated devices and existing KMS configurations that needed no furtherslmgr.vbscommands were not affected.
Improvement 1 change
Servicing stack
-
The component that installs Windows updates gets quality improvements.2
Includes servicing stack update KB5131079, version 26100.33822.
Known issues
-
Windows Server Update Services (WSUS) does not display error details
Windows Server Update Services (WSUS) does not show synchronization error details in its reports after KB5070881 or later updates.3
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Monitor release health until a resolving update is available.
Technical details
Data sheet · Security · Downloads · Components Click to collapse or expand
Data sheet
- Released
- 2026-11-13
- Classification
- Updates
- Type
- Cumulative update
- Restart
- Required
- Replaces
-
KB5131080, KB5134137, KB5126646, KB5129235
+33 earlier
KB5122871, KB5120233, KB5099536, KB5094125, KB5087539, KB5091157, KB5082063, KB5078740, KB5075899, KB5078135, KB5077793, KB5073379, KB5072033, KB5072359, KB5068861, KB5070881, KB5070773, KB5066835, KB5068221, KB5065426, KB5063878, KB5064489, KB5062553, KB5060842, KB5058411, KB5055523, KB5053598, KB5051987, KB5050009, KB5048667, KB5046617, KB5044284, KB5043080
| Version | Build | Channel |
|---|---|---|
| 2025 | 26100.33828 | General availability |
Security
No vulnerabilities are listed for this update.
Downloads (Microsoft Update Catalog)
Updated components
1,498 files changed since the previous update for the same versions.
| Top changed components | Files |
|---|---|
| Graphics and display | 12 |
| Hyper-V and virtualization | 7 |
| Remote Desktop | 7 |
| Printing | 4 |
| Secure Boot | 4 |
| Bluetooth | 3 |
| Emoji and input | 3 |
| Kernel | 3 |
| Networking | 3 |
| Security and sign-in | 3 |
| Search | 2 |
| Settings | 2 |
Sources
Cited passages from Microsoft's official notes (3)
-
1.
Fixed: An issue where certain Windows licensing and activation operations using the Software Licensing Management Tool (SLMGR) might fail with error 0x80041008 (Invalid parameter).
support.microsoft.com -
2.
This update makes quality improvements to the servicing stack, which is the component that installs Windows updates.
support.microsoft.com -
3.
After installing KB5070881 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting.
support.microsoft.com
Checked automatically: 8 of 8 checks passed, 3 quoted passages · compared with Microsoft's page on Nov 15, 2026
- Quotes found in the official pages: passed
- Numbers found in the sources: passed
- Vulnerabilities from the dossier only: passed
- Links to allowed domains only: passed
- Every official change covered: passed
- Readable plain text: passed
- Changes confirmed by the file list: passed
- Sources agree: passed
A second AI read the text against the sources: correctness 5/5, clarity 4/5, completeness 4/5. How we work
Published by The Update Bureau. Written with AI from Microsoft's own documents, checked by rules and a second AI. How we work · Report a mistake