Patchmap › Windows Server 2025 › KB5075899
KB5075899
Security Update for Windows Server 2025, February 2026 (released 2026-02-10). It includes 29 security fixes: most in Kernel and drivers (13), Network (6), Server roles (5), Other (4).
5 of its 29 fixes are being exploited (Microsoft and CISA). Attackers are using these weaknesses: don't stay without KB5075899 for long.
| Windows version | Build after installing |
|---|---|
| Windows Server 2025 | 10.0.26100.32370 |
Replaces: KB5074109. Replaced by: KB5078736. Restart needed: Yes.
Software that relies on parts this update changed
Worth checking after installing, not a sign it will break.
- PaperCut NG/MF
- Active Directory user sync (LDAP, Kerberos): 1 fix
- Document rendering for printing (GDI): 1 fix
- YSoft SafeQ
- Active Directory sign-in and user sync (LDAP, Kerberos): 2 fixes
- Document rendering for printing (GDI): 1 fix
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.
Before removing it: KB5075899 carries 29 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:
Network6 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
Kernel and drivers13 fixes
Network6 fixes
Server roles5 fixes
Other4 fixes
Sign-in and identity2 fixes
Graphics and display2 fixes
Remote Desktop2 fixes
Printing and scanning1 fixes
Storage and file systems1 fixes
Desktop and apps1 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.