feat(scanner/windows): update kb supersession#2518
Merged
Conversation
Add latest cumulative update KB entries for all actively maintained Windows versions: - Windows 10 Build 14393: Oct 2025 → Apr 2026 (7 entries) - Windows 10 22H2 Build 19045: Nov 2025 → Apr 2026 ESU (10 entries) - Windows 11 23H2 Build 22631: Nov 2025 → Apr 2026 (9 entries) - Windows 11 24H2 Build 26100: Nov 2025 → Apr 2026 (15 entries) - Windows 11 25H2 Build 26200: Nov 2025 → Apr 2026 (14 entries) - Windows 11 26H1 Build 28000: Feb → Apr 2026 (6 entries, newly enabled) - Windows Server 2016 Build 14393: Oct 2025 → Apr 2026 (7 entries) - Windows Server 2019 Build 17763: Nov 2025 → Apr 2026 (9 entries) - Windows Server 2022 Build 20348: Nov 2025 → Apr 2026 (9 entries) - Windows Server 2022, 23H2 Build 25398: Nov 2025 → Apr 2026 (8 entries) - Windows Server 2025 Build 26100: Oct 2025 → Apr 2026 (11 entries, incl. hotpatch) Also enables Windows 11 26H1 (Build 28000) in winBuilds map and updates test expectations accordingly. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates Windows KB supersedence data used by the Windows scanner to map kernel build/revision numbers to cumulative update KBs, and enables Windows 11 26H1 build detection.
Changes:
- Enable Windows 11 Version 26H1 (build 28000) in the Windows build-to-name map.
- Extend
windowsReleasesrollup tables with new KB/revision pairs through Apr 2026 across supported Windows client/server versions (including new 28000 entries). - Update unit test expectations for OS name detection and KB detection based on the new rollup data.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
scanner/windows.go |
Adds build 28000 to winBuilds and extends windowsReleases rollup data with new KB/revision entries (including new 28000 rollups). |
scanner/windows_test.go |
Updates expected OS name for “latest” Windows 11 and updates KB expectation lists to match new rollup tables. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Add dedicated Test_detectOSName case for Windows 11 26H1 (build 28000) and two DetectKBsFromKernelVersion cases (10.0.28000.1 and 10.0.28000.1836) to exercise the newly enabled 26H1 rollup data directly. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Windows scanner’s KB supersedence (rollup) data and enables Windows 11 26H1 (build 28000) so OS name/KBe detection stays current for actively maintained Windows client/server releases.
Changes:
- Enable Windows 11 Version 26H1 (build 28000) in the build-to-name mapping.
- Extend
windowsReleasesrollup data with new revision→KB entries across multiple Windows client/server builds through Apr 2026. - Update unit tests to cover 26H1 OS name detection and KB detection for build 28000, and refresh expected KB sets for updated rollups.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| scanner/windows.go | Enables build 28000 as Windows 11 26H1 and appends new revision→KB rollup entries across Windows releases. |
| scanner/windows_test.go | Adds explicit 26H1 OS name test cases, new 28000 KB detection cases, and updates expected KB lists to match the new rollup data. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
KB5068864 (November 2025 Patch Tuesday) corresponds to OS Build 14393.8594, not 14393.8628. Fix both Windows 10 and Windows Server 2016 entries. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…25 / Jan 2026 KBs KB5071543 (Dec 2025 B): 8697 → 8688 (OS Build 14393.8688) KB5074974 (Dec 2025 OOB): 8747 → 8692 (OS Build 14393.8692) KB5073722 (Jan 2026 B): 8806 → 8783 (OS Build 14393.8783) Applied to both Windows 10 (LTSB) and Windows Server 2016 sections. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If this Pull Request is work in progress, Add a prefix of “[WIP]” in the title.
What did you implement:
Add latest cumulative update KB entries for all actively maintained Windows versions:
Also enables Windows 11 26H1 (Build 28000) in winBuilds map and updates test expectations accordingly.
Type of change
How Has This Been Tested?
unit test
Checklist:
You don't have to satisfy all of the following.
make fmtmake testIs this ready for review?: YES
Reference