Microsoft Releases Windows OOB Fix for Activation Errors

Microsoft released an optional non-security out-of-band update for limited enterprise licensing operations that can fail with error 0x80041008; no same-day macOS release was established in the official Apple surfaces reviewed.

Reader ratingRate this article

Loading reader rating…

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Oblique IT workbench with a blue monitor showing a glowing key, an amber warning changing to a green check, a desktop sequence, and a download arrow; a silver laptop with a green status dot sits behind it.
AI-generated editorial illustration of a Windows licensing and activation repair workflow; not an official interface or documentary image.

Microsoft released an optional non-security out-of-band update on November 13, 2026, for a limited number of enterprise devices whose Windows licensing or activation operations can fail with error 0x80041008.[1] The failure primarily affects organizations using slmgr.vbs or automation to configure KMS activation, install product keys, or manage Windows licensing.[1]

Devices that were already activated remain activated.[1][2] Existing KMS configurations that do not need additional slmgr.vbs commands are not affected.[2] This is a targeted cumulative quality fix, not a new monthly security release or feature update.[1][2]

Reporting cutoff: November 13, 2026, 7:09 p.m. EST (2026-11-14 00:09:50 UTC).

Home users: do not install this OOB update merely because it is new; Microsoft describes a limited enterprise licensing scenario and already activated devices remain activated.[1][2]

Business and IT teams: confirm error 0x80041008 in a licensing workflow before selecting the exact product package below.[1][2]

Classification and scope

  • Update class: optional, cumulative, non-security out-of-band quality update dated November 13, 2026.[1][2][3][4][5][6]
  • Trigger: certain SLMGR-based licensing and activation operations fail with invalid-parameter error 0x80041008.[1][2]
  • Affected workflows: KMS activation, product-key installation, or Windows licensing management performed with slmgr.vbs or automation.[1][2]

Exact KB, build and channel map

ProductKBOS buildChannel
Windows 11, version 23H2[2]KB5136483[2]22631.7714[2]Windows Update Optional updates and Microsoft Update Catalog[1][2]
Windows Server 2025[3]KB5136489[3]26100.33828[3]Microsoft Update Catalog[1][3]
Windows Server 2022[4]KB5136487[4]20348.5873[4]Microsoft Update Catalog[1][4]
Windows Server 2019; Windows 10 Enterprise LTSC 2019[5]KB5136490[5]17763.9488[5]Microsoft Update Catalog[1][5]
Windows 10 22H2 ESU; Windows 10 Enterprise LTSC 2021; Windows 10 IoT Enterprise LTSC 2021[6]KB5136493[6]19045.7850 / 19044.7850[6]Microsoft Update Catalog[1][6]

Deployment cautions

  1. Confirm that the failed operation uses SLMGR, KMS, product-key installation, or licensing automation and returns 0x80041008.[1][2]
  2. Select the package only from the product, KB, build, and channel row that matches the affected system.[2][3][4][5][6]
  3. Read the selected KB’s prerequisite cumulative-update and servicing-stack requirements before deployment.[2][3][4][5][6]
  4. For dynamic updates to existing installation media, include a boot.stl file matching the Windows version and architecture.[2][3][4][5][6]
  5. Do not omit boot.stl; Microsoft warns that omission can prevent startup from the media with error 0xc0430001.[2][3][4][5][6]
  6. Distinguish the known-issue states: KB5136483, KB5136490, and KB5136493 report no currently known update-specific issues, while KB5136489 and KB5136487 carry a WSUS synchronization-error-display issue from earlier updates.[2][3][4][5][6]
  7. Record the starting build and licensing state before deployment.[2][3][4][5][6]
  8. Deploy first to a representative test ring.[2][3][4][5][6]
  9. Verify the intended activation operation after installation and retain the organization’s normal rollback owner; this is practical editorial guidance, not a Microsoft guarantee.[2][3][4][5][6]

What users should do

  • If Windows is activated and you do not manage enterprise KMS or product-key automation, take no special action for this OOB release.[1][2]
  • Do not download a Catalog package for an unrelated activation concern.[1][2]
  • For Windows 11 23H2, use Settings → Windows Update → Advanced options → Optional updates or the Microsoft Update Catalog.[1][2]
  • For the listed Server and Windows 10 products, use the Microsoft Update Catalog.[1][3][4][5][6]

Apple check: tvOS only on November 13[7][8]

Apple’s security-release index and Developer Releases page list tvOS 27.2.1 on November 13, 2026.[7][8] In the same captured official surfaces, the latest listed production Mac releases are macOS Golden Gate 27.2.1, macOS Tahoe 26.7.3, and macOS Sequoia 15.8.3, all dated November 9.[7][8] No same-day macOS release was established in those official surfaces as of the reporting cutoff; that is a bounded source check, not a claim that Apple could not publish later.[7][8]

FAQ

Is this a security update?

No. Microsoft classifies these packages as optional non-security out-of-band updates; they are cumulative and include earlier improvements.[1][2][3][4][5][6]

Should every Windows user install it?

No. The documented problem is limited to certain enterprise licensing operations, and already activated devices remain activated.[1][2]

Which package can appear in Optional updates?

KB5136483 for Windows 11 23H2 can be offered through Windows Update’s Optional updates page.[1][2] The Server and listed Windows 10 packages are Catalog releases.[1][3][4][5][6]

Was there a same-day macOS release?

No November 13 macOS release appears in the captured Apple security and developer release surfaces; those pages list tvOS 27.2.1 on November 13 and the newest macOS rows on November 9.[7][8]

Official sources

  1. Microsoft Windows Message Center: OOB licensing and activation update
  2. Microsoft KB5136483: Windows 11 23H2
  3. Microsoft KB5136489: Windows Server 2025
  4. Microsoft KB5136487: Windows Server 2022
  5. Microsoft KB5136490: Windows Server 2019 and Windows 10 Enterprise LTSC 2019
  6. Microsoft KB5136493: Windows 10 ESU and LTSC 2021
  7. Apple security releases
  8. Apple Developer Software Releases

Browse Articles

Latest Articles