November 2026 Windows Security Update: KB5132061, Security Fixes, and Installation Guide

Microsoft has officially released its November 2026 Windows security update, bringing security improvements, Secure Boot certificate deployment enhancements, and several important bug fixes to supported Windows devices. Released on November 10, the update covers Windows 11, Windows 10, and multiple Windows Server versions.

For Windows 11 users, particularly those running versions 26H2, 25H2, and 24H2, the main update is KB5132061. Microsoft recommends installing the latest security updates promptly to help protect devices against emerging threats and maintain system reliability.

This month’s release also addresses a frustrating USB audio problem, expands the rollout of newer Secure Boot certificates, and includes additional improvements carried forward from previous updates. Administrators managing hotpatch-enabled environments should also pay attention to separate PowerShell security updates.

Here’s everything users and IT administrators need to know about the November 2026 Windows security release, including the main changes, supported versions, KB numbers, and installation instructions.

November 2026 Windows Update: What’s Included?

The November security release is part of Microsoft’s regular monthly servicing schedule. It delivers security improvements alongside reliability fixes and changes intended to improve the Windows experience.

For Windows 11, version 26H2, the November update builds on improvements previously delivered through KB5127648, released on October 13, 2026.

Microsoft has also incorporated other intervening improvements into the November cumulative release, meaning users receive a broader package of fixes rather than a security-only update.

The main highlights include:

• Security improvements designed to protect Windows devices against current threats.
• Expanded Secure Boot certificate deployment for eligible devices.
• A fix for USB Audio 1.0 devices experiencing startup failures and Device Manager error code 10.
• Additional reliability and compatibility improvements.
• Further security enhancements involving Windows authentication and PowerShell.

These changes make the November release relevant not only to individual Windows users but also to businesses responsible for maintaining large device environments. Microsoft Support+1

1. Secure Boot Certificate Deployment Expands

One of the most important developments in the November 2026 update involves Microsoft’s ongoing Secure Boot certificate transition.

Secure Boot is a Windows security feature that helps prevent unauthorized software from loading during the device startup process. It checks digital signatures during the boot sequence, helping protect systems against certain types of boot-level malware and unauthorized modifications.

However, older Secure Boot certificates are approaching expiration, with some beginning to expire in 2026. Microsoft is gradually transitioning eligible devices to newer certificates to maintain the security and reliability of the boot process.

The November update expands this deployment through additional high-confidence device targeting data.

In practical terms, this means Microsoft can identify more eligible devices for automatic delivery of updated Secure Boot certificates through Windows Update.

There is an important distinction for users: devices that have not yet received the newer certificates can continue starting normally and receiving standard Windows updates. The certificate rollout is ongoing, rather than an indication that every Windows computer must receive the new certificates immediately.

Microsoft expects certificate deployment to continue across supported PCs and non-managed business devices over the coming months.

For IT administrators, this development highlights the importance of monitoring Secure Boot readiness, particularly across devices with different hardware configurations and firmware environments. Microsoft Support+1

2. Microsoft Fixes USB Audio Error Code 10

Another significant improvement addresses a problem affecting certain USB Audio 1.0 devices.

Following a previous security update, some USB audio devices experienced startup failures and stopped functioning correctly. In affected cases, Windows Device Manager displayed the following message:

“This device cannot start (Code 10).”

Users could experience several symptoms, including:

• USB audio devices failing to initialize.
• No sound output from affected devices.
• Unresponsive volume controls.
• Audio settings becoming unavailable or behaving unexpectedly.

The issue was particularly frustrating for users who rely on external USB microphones, headsets, speakers, and other audio equipment.

Microsoft has addressed this problem through the November 2026 security update.

For affected Windows 11 users, installing KB5132061 should resolve the documented USB Audio 1.0 startup issue.

This fix is especially relevant to people who noticed audio problems after installing an earlier Windows security update. Rather than immediately replacing their audio hardware, users should first install the applicable cumulative update and check whether the device works correctly afterward. Microsoft Support+1

3. Additional Security Improvements Strengthen Windows Protection

Beyond the headline fixes, the November release includes additional security improvements.

One notable change concerns NTLM authentication. Microsoft is improving NTLM security by enabling clients to offer NTLM message signing by default for non-anonymous connections.

NTLM is an authentication protocol used in certain Windows environments, particularly where older applications and infrastructure still depend on it.

The change is intended to reduce exposure to NTLM relay attacks, in which attackers attempt to misuse authentication exchanges to gain unauthorized access to network resources.

The update also introduces auditing capabilities that can help administrators identify connections that do not use message signing.

For organizations still operating legacy Windows infrastructure, this is worth reviewing because authentication changes can affect compatibility and security policies.

Another important improvement involves PowerShell script signing and signature verification.

Microsoft is introducing stricter encoding validation. Consequently, scripts containing invalid UTF-8 encoding may fail signature verification even if previous Windows versions accepted them.

Administrators and developers who encounter this behavior should:

1. Identify the affected PowerShell scripts.
2. Review their existing file encoding.
3. Save affected scripts using valid UTF-8 encoding with a byte order mark (BOM).
4. Sign the scripts again.
5. Test them before deploying them across production systems.

These changes demonstrate that the November release addresses more than conventional operating system vulnerabilities. It also strengthens security controls used in enterprise authentication and administrative workflows. Microsoft Support+1

4. Other Improvements: Printing, Remote Desktop, and System Reliability

The November update also includes several fixes that may be particularly relevant to business users.

Printing improvements

Microsoft resolved an issue that could prevent users from adding printers published in Active Directory through Windows Settings.

Affected users might encounter error code 87, accompanied by the message “The parameter is incorrect.”

The problem was introduced by the October 2026 update. Microsoft notes that it generally does not affect existing printers or normal printing operations.

Remote Desktop improvements

The update also addresses a Remote Desktop Protocol (RDP) connection problem involving certificate mismatches.

The issue could prevent certain client connections following the October non-security preview update.

This correction is important for organizations that depend on Remote Desktop to access workstations, servers, and virtual environments.

Additional regional time-zone adjustments

Microsoft has also updated daylight saving time rules for Cuba to account for its extended 2026–2027 schedule.

Cuba remains on UTC-04:00 without the usual November 2026 and March 2027 transitions. The country is scheduled to return to UTC-05:00 in November 2027 before resuming its regular seasonal schedule in 2028.

Together, these changes show that the November release includes a combination of security, compatibility, and operational improvements. Microsoft Support

5. Windows Versions Receiving the November 2026 Security Update

Microsoft has published separate KB packages for different Windows versions and server editions.

Users should select the update corresponding to their operating system rather than attempting to install a package intended for another version.

The following is the update list provided in Microsoft’s November release announcement.

The KB identification numbers are particularly useful for IT teams managing updates through centralized deployment systems.

They also allow users to check whether the November package has been installed successfully.

6. Special PowerShell Security Updates for Hotpatch Devices

There is another important detail in Microsoft’s November security announcement that administrators should not overlook.

Devices enrolled in hotpatch updates have access to additional standalone security updates addressing vulnerabilities in Windows PowerShell.

These updates cover security issues involving:

• PowerShell web requests.
• PowerShell workflows.
• The Desired State Configuration (DSC) Archive Resource.

The standalone packages are offered after the November 2026 hotpatch update has been installed.

Microsoft also warns that a restart might be necessary if any of the updated files are currently in use.

The relevant packages are:

• Windows 11 versions 26H2, 25H2, and 24H2: KB5135385.
• Windows Server 2025: KB5135386.

Organizations using hotpatch-enabled systems should verify that these additional updates are installed where applicable.

This is particularly important because installing the main November hotpatch update does not mean administrators should automatically overlook separately offered security packages.

7. How to Install the November 2026 Windows Security Update

For most users, the easiest way to install the November update is through Windows Update.

Microsoft recommends installing security updates promptly rather than delaying them unnecessarily.

Follow these steps:

1. Open the Start menu.
2. Select Settings.
3. Navigate to Windows Update.
4. Select Check for updates.
5. Allow Windows to identify available updates.
6. Download and install the applicable November security update.
7. Restart the computer if Windows requests it.

After installation, users can verify the update by navigating to:

Settings → Windows Update → Update history → Quality Updates.

Look for the applicable KB number, such as KB5132061 for Windows 11 versions 26H2, 25H2, and 24H2.

What if Windows Update does not show the update?

If the update is not immediately available, users can consult the corresponding Microsoft support article or download the standalone package through the Microsoft Update Catalog.

However, administrators should pay attention to prerequisite servicing stack and checkpoint cumulative updates, particularly when deploying packages manually or updating Windows installation media.

For example, Microsoft’s KB5132061 instructions specify prerequisite update requirements that vary between Windows 11 versions.

Organizations should follow the installation sequence documented in the applicable KB article to avoid deployment problems. Microsoft Support

8. No December 2026 Non-Security Preview Update

Microsoft has also announced a change to its regular update schedule for December.

Because of reduced operations during the Western holiday period and the approaching New Year, there will be no December 2026 non-security preview update during the second half of the month.

However, this does not mean Windows security updates are being discontinued.

Microsoft has confirmed that normal monthly servicing for both security updates and non-security preview updates will resume in January 2027.

For businesses, this announcement is useful when planning maintenance windows, testing schedules, and monthly deployment cycles.

IT departments should continue monitoring Microsoft’s official release information rather than assuming that the absence of a December preview update means all servicing activity has stopped. Microsoft Support

What Windows Users and IT Administrators Should Do Next

The November 2026 Windows security update brings several important improvements, from broader Secure Boot certificate deployment to fixes for USB audio failures, authentication security, and Remote Desktop connectivity.

For individual users, the immediate priority is straightforward: check Windows Update and install the applicable security package.

For IT administrators, the release deserves a more detailed review, particularly in environments that rely on NTLM authentication, PowerShell automation, Remote Desktop, Active Directory printers, and hotpatch servicing.

A sensible deployment strategy should include:

• Checking which Windows versions are installed across managed devices.
• Identifying the correct November KB packages.
• Reviewing prerequisites before manual or enterprise deployment.
• Testing updates on representative devices before broad rollout.
• Verifying Secure Boot certificate readiness.
• Checking separately offered PowerShell security packages on hotpatch devices.

The coming weeks will be important as Microsoft continues expanding Secure Boot certificate deployment and organizations assess the operational impact of the latest security changes.

With the December non-security preview update skipped, January 2027 will be the next regular preview servicing milestone. Until then, keeping supported Windows devices current with the November security release should remain a priority.

Extra posts:

Windows August 2026 Security Update Is Here: What You Need to Know Before You Restart Windows Server 2022 November and December 2026 Security Updates Require Restarts Windows 11 Slow? 15 Fixes to Boost Performance (Expert Guide) Windows 11 26H2 Is Here: How to Get the 2026 Update and What Changes for Your PC Microsoft Teams to Introduce Guest Invitation Security Reporting in November 2026 Windows 11 Photos App Update 2026: Release Date, New Features, and Enterprise Policy Changes