Skip to main content

Windows 11 KB5132057 Is the Last Optional Update of 2026, and the SQL Server Connection Leak Is Still Not Fixed

Microsoft's KB5132057 preview adds a new Windows Search, web sign-in for hybrid joined PCs and an Android passkey fix. The SQL Server linked server leak stays open, and there will be no December preview.

KBY News Desk8 min read
An adult using a laptop indoors, browsing Google at a wooden table with coffee.

Microsoft released KB5132057 on Thursday 19 November, the last scheduled optional update of 2026 for Windows 11 versions 25H2 and 26H2. It brings a rebuilt Windows Search, a brighter Windows Hello face sign-in for dim rooms, web sign-in for Microsoft Entra hybrid joined PCs and a set of fixes, including the one for the misleading Android passkey error. It does not fix the SQL Server linked server connection leak that Microsoft lists as a known issue, and Microsoft’s own page says there will be no non-security preview in December. This is a preview, so nothing installs unless someone asks for it, but the gap it opens in the calendar is the part IT teams should plan around.

#What arrives now and what arrives later

Microsoft’s support page for the update (builds 26300.10075 and 26200.10075) splits the contents into two groups. A “gradual rollout” delivers features in phases, so two PCs on the same update can behave differently for a while. A “normal rollout” is the broad release to every eligible device at the same time. Most of the new features sit in the first group. Most of the bug fixes sit in the second.

The headline feature is the new Windows Search. Results appear in a single simplified list, Microsoft says performance and memory use improve, and files can be previewed from inside search with details such as when they were last modified and who created them. Search also gets inline actions, so a user can turn on dark mode or Bluetooth, change brightness or mute the device without opening Settings. With an Android phone linked through Phone Link, they can call or text contacts from the same box. Microsoft says the new experience is initially available in English only.

The Register, which tested it, welcomed the speed-up and was less taken with the actions: “turn on dark mode” worked in its testing, but “switch on dark mode” did not. That is a fair warning for anyone expecting users to find the feature by guessing phrases, and a reason to expect a few “search does not do what I typed” tickets.

Smaller changes in the same group include an optional setting that lets Windows Hello facial recognition brighten the screen briefly (Settings, then Accounts, then Sign-in options, then Facial recognition), an opt-in modern Run dialog (Settings, then System, then Advanced), a red rather than yellow border during screen capture, and File Explorer search from This PC that now uses the index. A new pointer indicator and extra Magnifier and Narrator options cover accessibility.

#The fixes a help desk will notice

The normal-rollout list is where the practical value sits. Microsoft says the update fixes:

  • the “Something went wrong” message that Android phones showed during cross-device passkey sign-in;
  • Sage 50 Accounting closing unexpectedly when options were selected;
  • Miracast connections defaulting to a lower resolution on certain wireless display receivers;
  • a wrong “Someone else is using this PC” warning when restarting or shutting down with nobody else signed in;
  • File History restore failing to find backups when a drive is chosen as the backup location;
  • Windows Fax and Scan failing to connect to a fax server because of an authentication problem;
  • Windows IoT Enterprise LTSC devices failing to activate through Key Management Service or Token-Based Activation;
  • extra characters at the start of Japanese text typed into RemoteApp applications.

The passkey item deserves a note for the service desk. The Register reports that Microsoft’s guidance says the Android error “is not supposed to appear” when the sign-in has actually completed on the Windows PC, and “can be safely ignored”. It says the problem affected cross-device sign-ins that used Microsoft Authenticator or Google Password Manager, in Edge or Chrome and not only through Entra ID, and that iPhones were not affected. If users have reported failed passkey sign-ins that turned out to have worked, this is the explanation, and a one-line knowledge base entry will save time until the fix is deployed.

#Web sign-in comes to hybrid joined PCs

The change most likely to matter to a larger estate is easy to miss in the list. Microsoft says web sign-in is now supported on Entra hybrid joined devices as well as Entra joined ones. At the lock screen, a user can sign in without a password using a FIDO2 security key, a passkey on their phone or a Temporary Access Pass, and Windows then gets a Kerberos ticket, so on-premises file shares and internal sites keep working. For organisations that are part-way through a move to passwordless and still have hybrid PCs, that removes a reason to keep passwords around. Microsoft links its web sign-in documentation from the update page, and we would read that before switching anything on, because this is an authentication path and a Temporary Access Pass at the lock screen needs the same care as any other recovery route.

There are two further sign-in changes. The update removes the “Other user” icon from the PIN entry screen, and devices with display-based NFC readers get an on-screen marker showing where to tap a security key. Microsoft also says it fixes boot failures or TPM initialisation errors on Arm-based systems that use a TPM 2.0 Command Response Buffer interface. If you manage Arm laptops and have seen unexplained TPM errors at start-up, put those on the pilot list first.

#The leak that is still there

The one known issue on the page is the same one we covered in our November Update Watch. After Windows updates released on or after 13 October 2026 are installed on server devices, connections created by SQL Server linked server queries can stay open once the queries have finished. Microsoft says this affects linked servers that use OLE DB providers, and names Oracle and PostgreSQL connections among those known to be hit. Open connections to external databases build up, and Microsoft says that can slow or degrade a server after it has run for some time.

Microsoft’s workaround has not changed. Idle connections can be closed by hand, and restarting the SQL service restores stability for a while, but both can interrupt active queries or transactions and the problem can return. A mitigation for enterprise devices is available only by contacting Microsoft Support for business. Microsoft says it is working on a resolution “in an upcoming release”. The Register notes the same, and that the preview did not clear it. Our advice from the Update Watch stands: if you run SQL Server with linked servers to Oracle or PostgreSQL, treat those machines as a separate group and do not assume this optional update helps them. Our November Patch Tuesday story lists what else shipped for the month.

#No December preview, and what we would do about it

Microsoft’s page says there will be no December 2026 non-security preview update in the second half of the month, because of minimal operations over the Western holidays and the new year. It says normal servicing resumes in January and, in the text we read, prints the year as 2026. We take that to be a slip for 2027, since the sentence is about the months after this one, but it is Microsoft’s wording and worth checking against the January notes when they appear. The December security update is not cancelled. By our own count, Patch Tuesday falls on 8 December.

In our view this changes the question an admin should ask about KB5132057. Normally an optional update is something to pilot for a few weeks and then take with the next security release. With no preview in December, the next chance to test a non-security build is January, so a pilot group that takes KB5132057 now gets the longest possible look at the new Search and the sign-in changes before they reach everyone. We expect, but Microsoft has not said on this page, that these changes will arrive in the December security update or the January preview; read the December release notes before assuming either.

What we would do, in order: put a small ring of IT-owned PCs on the update this week, including at least one Arm device if you have any; tell the service desk about the passkey message and the English-only Search; check your own Entra hybrid plans against the web sign-in documentation; keep SQL Servers with OLE DB linked servers out of any rollout; and make sure no one in your organisation is relying on this preview to fix a problem before the holidays without having tested it. Microsoft also reminds readers on the same page that the Secure Boot certificates used by most Windows devices began to expire in June 2026, and that devices without the newer certificates keep starting and updating normally. That is background, not a reason to hurry this update, but we track the longer story on our Windows Update certificate rotation page.

Two housekeeping points from the page. Windows 11 24H2 and 25H2 must already have an update released on or after 10 June 2025 (such as KB5060842) before this one installs through Windows Update, WSUS or the Microsoft Update Catalog. And if you add dynamic updates to a Windows image, Microsoft says the boot.stl file must be on the installation media, or devices may fail to start from it with error 0xc0430001. Windows 11 version 26H1 has its own preview, KB5132265.

#If you run a handful of PCs without an IT team

Most small firms can leave this alone. A preview only installs if someone checks for optional updates and picks it. The new Search will reach your PCs through the normal update in due course, and the brighter face sign-in and the new Run dialog are both off until someone turns them on. The thing worth doing is the boring one: keep your PCs on automatic updates, make sure each has had a restart this week, and ask whoever looks after your IT whether any of your servers talk to an Oracle or PostgreSQL database through SQL Server. If the answer is no, the open known issue does not affect you.

Evidence trail

Sources and verification

Primary documentation and external technical references used in this article.

  1. 01Microsoft Support: November 19, 2026, KB5132057 (OS Builds 26300.10075 and 26200.10075) Previewsupport.microsoft.com
  2. 02The Register: Microsoft's last non-security preview of 2026 packs a punchtheregister.com
  3. 03The Register: Windows 11 passkey bug cries failure after successful sign-intheregister.com

About this page

Credited to

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Reader Interaction

Comments

Add a thoughtful note on Windows 11 KB5132057 Is the Last Optional Update of 2026, and the SQL Server Connection Leak Is Still Not Fixed. Comments are checked for spam and held for moderation before appearing.

Loading comments...

Get new fixes by email.

New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.