Tuesday, November 17, 2026
banner

Microsoft’s November 2026 Windows security update is not a routine “approve and forget” release. It changes NTLM behavior, tightens validation of signed PowerShell scripts, and has produced installation failures on some devices. A successful rollout therefore needs three kinds of evidence: the update is installed, authentication still works as intended, and administrative automation remains trustworthy.

Know the target build

For Windows 11 versions 24H2, 25H2, and 26H2, Microsoft released KB5132061 on November 10. The resulting OS builds are 26100.9974, 26200.9974, and 26300.9974 respectively. Do not treat an update approval, download, or pending reboot as completion. Inventory the running build after restart and keep a list of devices that did not reach the expected baseline.

Microsoft documented installation failures with error codes including 0x80070306, 0x800f0989, and 0x800f0993, followed by an automatic repair. Administrators should still identify affected endpoints and prove that the repaired installation completed. A dashboard showing “offered” or “downloaded” is not equivalent to a running patched build.

NTLM signing is entering a staged transition

The update begins the first phase of Microsoft’s response to CVE-2026-118737. Windows clients now offer NTLM message signing by default for non-anonymous connections. The goal is to ensure that authenticated NTLM sessions establish a cryptographic session key and negotiate real message signing, reducing exposure to relay attacks.

This is a hardening step, not the disappearance of NTLM. Use the accompanying auditing to find connections that do not use signing and to identify applications, appliances, scripts, or legacy services that still depend on weak behavior. Prioritize Internet-facing paths, administrative protocols, privileged accounts, and connections crossing trust boundaries.

  • Collect NTLM audit events centrally before moving to stricter enforcement.
  • Resolve each exception to an owner, application, server, and business purpose.
  • Prefer Kerberos or modern authentication where supported.
  • Require Extended Protection for Authentication and signing where the protocol permits it.
  • Do not create broad exclusions merely to silence authentication failures.

Test signed PowerShell scripts

November’s update also introduces stricter encoding validation for PowerShell script signing and signature verification. Scripts containing malformed UTF-8 may fail validation even if they previously ran successfully. This is intentional security hardening: a signature should cover an unambiguous representation of the script.

Build a representative test set before broad deployment. Include logon scripts, scheduled tasks, deployment tooling, monitoring agents, certificate-management jobs, and emergency administration scripts. If a signed script fails, preserve the original, verify its source and expected hash, save a corrected copy using valid UTF-8 with a byte-order mark when required, and sign it again with the approved code-signing process. Do not “fix” the problem by disabling execution policy or accepting unsigned replacements.

Use a controlled rollout

  1. Inventory. Record Windows edition, version, build, servicing channel, reboot state, and the responsible owner.
  2. Pilot. Include ordinary workstations, administrator devices, RDP clients, VPN users, and machines that run signed automation.
  3. Deploy. Use a deadline and restart policy appropriate to the risk, not an indefinite “available” state.
  4. Verify. Query the running build after restart and compare it with the intended baseline.
  5. Test controls. Exercise representative NTLM-dependent connections, RDP paths, and signed PowerShell workflows.
  6. Close exceptions. Assign every failed device or incompatible workflow to an owner and remediation date.

Do not miss the lifecycle issue

Windows 11 version 23H2 Enterprise and Education received their final security update in November 2026. Any remaining systems need a migration owner, target release, compatibility plan, and deadline. A device that installs its final cumulative update is not protected indefinitely; it has reached the end of its servicing runway.

Practical checklist

  • Confirm KB5132061 and the correct running OS build after restart.
  • Find installation failures and verify the automatic repair outcome.
  • Centralize and review NTLM signing audit evidence.
  • Test signed PowerShell scripts and re-sign corrected files through the approved process.
  • Validate RDP and other authentication-dependent workflows in the pilot group.
  • Create a migration plan for Windows 11 23H2 Enterprise and Education.

Microsoft’s KB5132061 release notes, its NTLM signing guidance, and the PowerShell encoding guidance should remain the authoritative references during deployment.

banner
Choose your TOTP token

Newsletter

Subscribe our newsletter for latest crypto blog posts. Let's stay updated!

banner

Leave a Comment

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept