Patchmap › Windows 11 24H2 › KB5084597
KB5084597 Hotpatch
This is a hotpatch: Windows is patched in memory, without a restart. The full update for the same month is KB5079473, which replaces the files on disk.
Hotpatch for Windows 11 24H2, Windows 11 25H2, March 2026 (released 2026-03-10). It includes 3 security fixes: most in Network (3), Remote Desktop (3), Server roles (3).
None of its 3 fixes are known to be exploited (Microsoft and CISA).
| Windows version | Build after installing |
|---|---|
| Windows 11 24H2 | 10.0.26100.7982 |
| Windows 11 25H2 | 10.0.26200.7982 |
Replaces: KB5077212. Replaced by: KB5079473. Restart needed: No.
Something broke after this update?
- Check the known problems for this update (shown above, with sources). If yours is listed, follow its workaround.
- Note exactly what fails and when it started, and check the event logs for the area (below).
- Test on one machine first. Change one thing at a time.
Hotpatch: This is a hotpatch: Windows was patched in memory, without a restart. If a problem started with it, try the full cumulative update for the same month instead (it replaces the files on disk and needs one restart). Devices managed with hotpatching (Intune or Windows Autopatch) may need to be excluded from hotpatch until the next baseline. The full update for the same month is KB5079473.
Before removing it: KB5084597 carries 3 security fixes.
- Removing an update also removes every security fix it carries (the count is shown here). Keep the time without it short.
- To remove: Settings → Windows Update → Update history → Uninstall updates, or your management tool. For updates that come combined with a servicing stack update, Microsoft's KB page explains removing the update with DISM /Remove-Package (wusa /uninstall doesn't work on the combined package).
- Pause updates while you work on a fix, or Windows will reinstall it.
- Report it: Feedback Hub, a Microsoft support case, and Patchmap (Report a problem), so others can find it.
By area:
Network3 fixes
Where to look
- Event Viewer → Windows Logs → System, filtered on the failing service.
What to check
- Remote printing and many admin tools use RPC: port 135 plus a dynamic port range must be open between client and server.
- Check whether the problem is only across the network (works locally, fails remotely).
Not Microsoft advice: check Microsoft's page for this update before acting.
Security fixes by area
Network3 fixes
Remote Desktop3 fixes
Server roles3 fixes
Links
Not Microsoft and not official advice: check Microsoft's own page before acting. Data from the Microsoft Security Update Guide and Windows release health, refreshed weekly.