Plexus Access Solution

Windows 11 optional update KB5132057: sign-in changes and a SQL Server issue to know about

Microsoft released KB5132057, an optional preview update for Windows 11 versions 26H2 and 25H2, on 19 November 2026. It brings new features, a set of fixes and one known issue that affects servers.

Key takeaways

  • KB5132057 is an optional, non-security preview update, so it is not installed automatically on managed business PCs.
  • It extends web sign-in to Microsoft Entra hybrid joined devices and fixes several issues, including a Sage 50 Accounting crash and a TPM problem on Arm devices.
  • Microsoft lists a known issue: SQL Server linked server connections may stay open on servers with updates released from 13 October 2026 onward.
  • Test the update on a small pilot group before it becomes part of the regular security update.

What happened

On 19 November 2026 Microsoft published KB5132057 for Windows 11 versions 26H2 and 25H2 (OS builds 26300.10075 and 26200.10075). It is a preview release. That means it is optional and contains non-security changes that Microsoft plans to include in a later monthly update. Early coverage from other sites referred to slightly different build numbers (26300.10066 and 26200.10066) from 13 November, so the build you see on a device may depend on when it was installed. Use Microsoft's page as the reference.

The update is gradual: some features reach devices over time, and not every PC will show them straight away.

What is new

The listed changes include:

  • A redesigned Windows Search with inline actions and file previews, English first.
  • Windows Hello face recognition that can briefly raise screen brightness in dim rooms.
  • An optional modern Run dialog, turned on under Settings, System, Advanced.
  • File Explorer search from This PC now uses the Windows search indexer.
  • Accessibility additions such as a pointer indicator, Magnifier changes and Narrator math reading in eight more languages.
  • Web sign-in on Microsoft Entra hybrid joined devices, using FIDO2 security keys, phone passkeys or a Temporary Access Pass. A hybrid joined device is one that belongs to both an on-premises Active Directory and Microsoft Entra ID (formerly Azure AD).

Fixes included

Microsoft lists fixes for problems that can affect everyday work, such as Sage 50 Accounting closing unexpectedly, Miracast connecting at a lower resolution with some receivers, a false "Someone else is using this PC" warning, and an error with cross-device passkeys on Android. It also lists boot failures or initialization errors on Arm-based systems with a TPM 2.0 CRB interface. TPM is the security chip that stores keys for features such as BitLocker.

Known issue for servers

The release notes describe an issue where SQL Server linked server connections may remain open after queries finish. It affects server devices running Windows updates released on 13 October 2026 or later. Open connections can build up and slow performance over time. Closing idle connections or restarting the SQL service gives temporary relief, but either can interrupt work. Microsoft says a mitigation exists for affected enterprise devices through its business support, and the notes give no date for a fix. Deskmodder, a German Windows site, also reports this issue.

Why it matters

Optional previews are not urgent, but their contents usually become part of the next regular update. Reading them early lets you find problems before the whole company receives them. Businesses that run accounting software, hybrid sign-in or SQL Server will find at least one item here that touches their setup. The known issue is tied to updates already released in October, so servers may be affected whether or not they install this preview.

What businesses can do

  • Do not push the preview to every PC. Install it on a small pilot group first and check key applications, printing and sign-in.
  • If you use hybrid joined devices and want web sign-in, test it with a few accounts and decide which sign-in methods you will allow.
  • Check SQL Server machines that use linked servers. Watch for rising connection counts and slow queries, and note who to contact if you need Microsoft's mitigation.
  • Keep a record of build numbers per device, so you can tell which machines have which fixes.
  • Make sure backups are current before any update is rolled out.

Some details are still developing. Microsoft may update the notes, and third-party pages have shown conflicting dates and build numbers, so check the Microsoft page again before you deploy.

Sources

Planning updates for a mixed fleet of PCs and servers takes time that many small teams do not have. Plexus Access can help with servers and cloud setups, and you can ask for a free consultation.

Ready to talk about your project?

Tell us what you need. We offer a free consultation for your software and IT needs.