Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 274/275 feeds/APIs · 469/469 docs · 8/9 advisories · checked 15:16 UTC Customize Public modeDiscuss ChangeIntel on Discord

Recorded 15 Oct 2026 at 08:15 UTC. This is what ChangeIntel recorded, including the title, summary, facts and links. It is not a statement of the source's current position. See the latest record.

KB5121003

Windows 11, version 24H2: KB5121003 · 2026-08 B · OS build 26100.9168

What it said

KB
KB5121003
Windows versions and builds
Windows 11, version 24H2: 26100.9168 (2026-08 B); Windows 11, version 25H2: 26200.9168 (2026-08 B)
Applies to
Windows 11, version 24H2, Windows 11, version 25H2, Windows 11 Version 24H2 for ARM64-based Systems, Windows 11 Version 24H2 for x64-based Systems, Windows 11 Version 25H2 for ARM64-based Systems, Windows 11 Version 25H2 for x64-based Systems
Restart required
Yes
CVEs fixed
CVE-2026-68820, CVE-2026-62832, CVE-2026-62815, CVE-2026-62816, CVE-2026-62822, CVE-2026-62819, CVE-2026-62889, CVE-2026-62890, CVE-2026-66799, CVE-2026-49179, CVE-2026-62784, CVE-2026-62785, CVE-2026-62790, CVE-2026-62795, CVE-2026-62800, CVE-2026-62781, CVE-2026-62792, CVE-2026-42976, CVE-2026-54984, CVE-2026-59127, CVE-2026-61349, CVE-2026-61353, CVE-2026-61355, CVE-2026-61356, CVE-2026-61357, CVE-2026-61358, CVE-2026-61359, CVE-2026-61364, CVE-2026-61365, CVE-2026-61367, CVE-2026-61923, CVE-2026-61925, CVE-2026-61926, CVE-2026-61930, CVE-2026-61934, CVE-2026-61937, CVE-2026-62688, CVE-2026-62692, CVE-2026-62695, CVE-2026-62696, CVE-2026-62698, CVE-2026-62700, CVE-2026-62701, CVE-2026-62707, CVE-2026-62710, CVE-2026-62711, CVE-2026-62712, CVE-2026-62713, CVE-2026-62717, CVE-2026-62719, CVE-2026-62722, CVE-2026-62732, CVE-2026-62733, CVE-2026-62735, CVE-2026-62736, CVE-2026-62737, CVE-2026-62739, CVE-2026-62741, CVE-2026-62747, CVE-2026-62751, CVE-2026-62752, CVE-2026-62754, CVE-2026-62755, CVE-2026-62758, CVE-2026-62768, CVE-2026-62770, CVE-2026-62771, CVE-2026-62777, CVE-2026-62779, CVE-2026-62783, CVE-2026-62797, CVE-2026-62811, CVE-2026-62876, CVE-2026-62877, CVE-2026-62880, CVE-2026-62885, CVE-2026-62888, CVE-2026-62894, CVE-2026-65671, CVE-2026-65672, CVE-2026-65773, CVE-2026-65774, CVE-2026-65775, CVE-2026-65786, CVE-2026-65787, CVE-2026-65790, CVE-2026-65814, CVE-2026-66804, CVE-2026-70344, CVE-2026-70345, CVE-2026-70346, CVE-2026-70347, CVE-2026-54113, CVE-2026-59132, CVE-2026-59134, CVE-2026-61352, CVE-2026-61363, CVE-2026-50472, CVE-2026-59122, CVE-2026-59125, CVE-2026-59126, CVE-2026-61346, CVE-2026-61348, CVE-2026-61361, CVE-2026-61366, CVE-2026-61927, CVE-2026-61929, CVE-2026-61938, CVE-2026-61939, CVE-2026-62690, CVE-2026-62693, CVE-2026-62705, CVE-2026-62723, CVE-2026-62724, CVE-2026-62725, CVE-2026-62726, CVE-2026-62727, CVE-2026-62728, CVE-2026-62729, CVE-2026-62734, CVE-2026-62748, CVE-2026-62749, CVE-2026-62753, CVE-2026-62766, CVE-2026-62773, CVE-2026-62774, CVE-2026-62780, CVE-2026-62788, CVE-2026-62892, CVE-2026-62908, CVE-2026-65678, CVE-2026-65776, CVE-2026-65778, CVE-2026-65779, CVE-2026-65780, CVE-2026-65781, CVE-2026-65782, CVE-2026-65783, CVE-2026-65788, CVE-2026-70307, CVE-2026-62699, CVE-2026-62702, CVE-2026-62769, CVE-2026-62881, CVE-2026-62883, CVE-2026-65795, CVE-2026-65797, CVE-2026-65798, CVE-2026-65799, CVE-2026-70304, CVE-2026-70330, CVE-2026-59138, CVE-2026-61345, CVE-2026-61918, CVE-2026-61921, CVE-2026-61924, CVE-2026-62750, CVE-2026-62782, CVE-2026-65785, CVE-2026-65794, CVE-2026-62708, CVE-2026-59130, CVE-2026-59131, CVE-2026-59128, CVE-2026-59135, CVE-2026-59136, CVE-2026-59137, CVE-2026-61347, CVE-2026-61360, CVE-2026-61928, CVE-2026-61933, CVE-2026-61936, CVE-2026-62703, CVE-2026-62709, CVE-2026-62730, CVE-2026-62738, CVE-2026-62740, CVE-2026-62743, CVE-2026-62746, CVE-2026-62786, CVE-2026-62793, CVE-2026-62796, CVE-2026-62798, CVE-2026-62887, CVE-2026-65662, CVE-2026-65784, CVE-2026-70348, CVE-2026-62757, CVE-2026-65777, CVE-2026-61368, CVE-2026-61350, CVE-2026-56179
Known issues caused
None in the collected release health data
Known issues resolved
None in the collected release health data
Included security update
None identified in the collected release tables
CVEs listed directly for this KB
CVE-2026-68820, CVE-2026-62832, CVE-2026-62815, CVE-2026-62816, CVE-2026-62822, CVE-2026-62819, CVE-2026-62889, CVE-2026-62890, CVE-2026-66799, CVE-2026-49179, CVE-2026-62784, CVE-2026-62785, CVE-2026-62790, CVE-2026-62795, CVE-2026-62800, CVE-2026-62781, CVE-2026-62792, CVE-2026-42976, CVE-2026-54984, CVE-2026-59127, CVE-2026-61349, CVE-2026-61353, CVE-2026-61355, CVE-2026-61356, CVE-2026-61357, CVE-2026-61358, CVE-2026-61359, CVE-2026-61364, CVE-2026-61365, CVE-2026-61367, CVE-2026-61923, CVE-2026-61925, CVE-2026-61926, CVE-2026-61930, CVE-2026-61934, CVE-2026-61937, CVE-2026-62688, CVE-2026-62692, CVE-2026-62695, CVE-2026-62696, CVE-2026-62698, CVE-2026-62700, CVE-2026-62701, CVE-2026-62707, CVE-2026-62710, CVE-2026-62711, CVE-2026-62712, CVE-2026-62713, CVE-2026-62717, CVE-2026-62719, CVE-2026-62722, CVE-2026-62732, CVE-2026-62733, CVE-2026-62735, CVE-2026-62736, CVE-2026-62737, CVE-2026-62739, CVE-2026-62741, CVE-2026-62747, CVE-2026-62751, CVE-2026-62752, CVE-2026-62754, CVE-2026-62755, CVE-2026-62758, CVE-2026-62768, CVE-2026-62770, CVE-2026-62771, CVE-2026-62777, CVE-2026-62779, CVE-2026-62783, CVE-2026-62797, CVE-2026-62811, CVE-2026-62876, CVE-2026-62877, CVE-2026-62880, CVE-2026-62885, CVE-2026-62888, CVE-2026-62894, CVE-2026-65671, CVE-2026-65672, CVE-2026-65773, CVE-2026-65774, CVE-2026-65775, CVE-2026-65786, CVE-2026-65787, CVE-2026-65790, CVE-2026-65814, CVE-2026-66804, CVE-2026-70344, CVE-2026-70345, CVE-2026-70346, CVE-2026-70347, CVE-2026-54113, CVE-2026-59132, CVE-2026-59134, CVE-2026-61352, CVE-2026-61363, CVE-2026-50472, CVE-2026-59122, CVE-2026-59125, CVE-2026-59126, CVE-2026-61346, CVE-2026-61348, CVE-2026-61361, CVE-2026-61366, CVE-2026-61927, CVE-2026-61929, CVE-2026-61938, CVE-2026-61939, CVE-2026-62690, CVE-2026-62693, CVE-2026-62705, CVE-2026-62723, CVE-2026-62724, CVE-2026-62725, CVE-2026-62726, CVE-2026-62727, CVE-2026-62728, CVE-2026-62729, CVE-2026-62734, CVE-2026-62748, CVE-2026-62749, CVE-2026-62753, CVE-2026-62766, CVE-2026-62773, CVE-2026-62774, CVE-2026-62780, CVE-2026-62788, CVE-2026-62892, CVE-2026-62908, CVE-2026-65678, CVE-2026-65776, CVE-2026-65778, CVE-2026-65779, CVE-2026-65780, CVE-2026-65781, CVE-2026-65782, CVE-2026-65783, CVE-2026-65788, CVE-2026-70307, CVE-2026-62699, CVE-2026-62702, CVE-2026-62769, CVE-2026-62881, CVE-2026-62883, CVE-2026-65795, CVE-2026-65797, CVE-2026-65798, CVE-2026-65799, CVE-2026-70304, CVE-2026-70330, CVE-2026-59138, CVE-2026-61345, CVE-2026-61918, CVE-2026-61921, CVE-2026-61924, CVE-2026-62750, CVE-2026-62782, CVE-2026-65785, CVE-2026-65794, CVE-2026-62708, CVE-2026-59130, CVE-2026-59131, CVE-2026-59128, CVE-2026-59135, CVE-2026-59136, CVE-2026-59137, CVE-2026-61347, CVE-2026-61360, CVE-2026-61928, CVE-2026-61933, CVE-2026-61936, CVE-2026-62703, CVE-2026-62709, CVE-2026-62730, CVE-2026-62738, CVE-2026-62740, CVE-2026-62743, CVE-2026-62746, CVE-2026-62786, CVE-2026-62793, CVE-2026-62796, CVE-2026-62798, CVE-2026-62887, CVE-2026-65662, CVE-2026-65784, CVE-2026-70348, CVE-2026-62757, CVE-2026-65777, CVE-2026-61368, CVE-2026-61350, CVE-2026-56179
Missing security release
None identified in collected security coverage
Published
11 Aug 2026 00:00 UTC

Source evidence when recorded

Windows 11 releases
Complete at observationRead 15 Oct 2026 at 08:15 UTC
Microsoft security releases
Complete at observationRead 15 Oct 2026 at 08:15 UTC
Windows known issues
Complete at observationRead 15 Oct 2026 at 08:15 UTC

Coverage describes the sources at this observation. A complete read then does not establish their current position.

What changed

  1. Known issues: Microsoft Teams and Outlook might fail to launch on ARM-based devices: Resolved → None in the collected release health data
Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (3)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 15 Oct 2026 · 08:15:54 UTC Known issues causedMicrosoft Teams and Outlook might fail to launch on ARM-based devices: Resolved → None in the collected release health data
  2. 14 Oct 2026 · 11:22:42 UTC Missing security releaseUnknown: security evidence is incomplete or retained → None identified in collected security coverage
  3. 14 Oct 2026 · 11:22:42 UTC Source coverage: msrc-cvrfIncomplete → Current
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 11 Nov 15:16 UTC · 274 of 275 readable · 273 fully read · documentation 469/469 current