The admin logging is the most useful change for business IT. The math-on-Braille support is the most important for people who rely on it. Details on each change follow.
Where this build fits
Like recent Experimental releases, build 26340.9882 sits on the Windows 11, version 26H2 code base and is delivered through an enablement package. Microsoft's release notes for earlier builds use the same wording, for example noting that updates are based on Windows 11, version 26H2 via an enablement package (Build 26340.9596).
This build comes one week after the previous Experimental flight. Microsoft's Windows Insider Blog listed Experimental: Build 26340.9843 in its October 30 announcement, and that release focused mainly on a larger Windows Search update.
If you've lost track of the channel names, the Experimental channel took over from the old Dev Channel. A Microsoft Q&A answer summarizing the channel notes says the Dev Channel has transitioned to the Experimental channel in the new Windows Insider Program rollout.
Microsoft describes every feature in this build as rolling out gradually. Installing 26340.9882 does not mean you get all of it right away. Microsoft says it relies on Controlled Feature Rollout, starting with a subset of Insiders and ramping up over time. If a colleague on the same build has a feature you don't, your install probably isn't broken. The feature just hasn't reached your device yet.
Summary: This is a 26H2-based Experimental flight with staged features. Matching build numbers don't mean matching feature sets.
Windows Hello: use whichever method works first
Microsoft says Windows Hello sign-in and unlock now behave more consistently and give clearer guidance. The practical change is simple: you no longer have to wait for face or fingerprint recognition to finish before typing your PIN.
Here is how Microsoft describes the new behavior:
- Use any method first. Face, fingerprint or PIN all work, and whichever succeeds first signs you in.
- Some cases still need the PIN. At certain times, such as after a restart, Windows asks for your PIN first. After that, biometrics work as usual.
Anyone who has watched the face-recognition animation spin while they already knew their PIN will welcome this. The PIN-after-restart rule should also be familiar, since Hello has long treated the PIN as the base credential. Microsoft gives "after a restart" only as an example and doesn't list every situation that triggers the PIN requirement.
Windows Hello event logging for IT admins
For enterprise admins, this is probably the most important change in the build. Microsoft is adding Windows Hello events that show how users actually sign in, without changing what users see.
| Event ID | Location | What it records |
|---|---|---|
| 4628 | Event Viewer > Windows Logs > Security | Which Windows Hello methods a user has set up and which one they used to sign in (PIN, face, fingerprint, or no Windows Hello) |
| 4629 | Event Viewer > Windows Logs > Security | Failed Windows Hello sign-in attempts |
| 5010, 7010 | Event Viewer > Applications and Services Logs > Microsoft > Windows > HelloForBusiness > Operational | Each Windows Hello sign-in and unlock, with the result (for troubleshooting) |
Microsoft says both Security log events use the existing Audit Logon policy, so no new audit category is needed. In general Windows terms, Audit Logon sits in the Logon/Logoff category of advanced audit policy. If your organization already audits logons, you shouldn't need to change anything to start receiving 4628 and 4629 on Insider devices that have the feature.
Some practical points:
- Hello adoption reporting. Admins currently have to piece together who really uses Hello and who still types a password. Event 4628 records the enrolled methods and the method actually used, so that data can go straight into a SIEM.
- Failed attempts. Event 4629 gives you something to alert on, such as repeated Hello failures on one device.
- Helpdesk troubleshooting. The HelloForBusiness Operational log gives support staff a record of each sign-in and unlock attempt and its outcome. That should help with "my face unlock keeps failing" tickets.
The release notes don't publish event field schemas, retention guidance or policy deployment steps. Test against real events before you build SIEM parsers, and expect the details to change while this is in preview.
Summary: Two new Security log events and two Operational log events give admins visibility into Hello usage. The Security events use the existing Audit Logon policy.
Live captions: choose your audio source
Live captions used to caption system audio, with the microphone available as an optional extra. In this build, Live captions settings let you pick system audio, your microphone, or both.
This is more useful than it may sound. You can caption a conversation with the person across the desk without also captioning a YouTube video in the background. Or you can caption only a Teams meeting or a video without picking up noise from the room. For deaf and hard-of-hearing users, deciding what gets captioned matters as much as how accurate the captions are.
Input: dismiss Sticky Keys and Filter Keys prompts for good
The Sticky Keys and Filter Keys prompts show up when you press Shift five times or hold the right Shift key too long. Gamers and fast typists trigger them by accident all the time. In this build, those dialogs let users who don't use the features choose not to be asked again, directly in the prompt.
Microsoft describes this as a change to the prompts only, not to the accessibility features. People who rely on Sticky Keys or Filter Keys should see no change in how those features work.
Narrator Math comes to refreshable Braille displays
Narrator's math support has been developing for several months. Microsoft's notes for Experimental build 26340.9354 introduced Narrator Math reading and said math reading is available as soon as you install this build, with no additional download or setup required.
Build 26340.9882 adds Braille output. When Narrator reads supported equations in Microsoft Word, PowerPoint, Edge or Google Chrome, Narrator Math now appears on a connected refreshable Braille display. Users can explore the equation by touch while Narrator reads it aloud.
The format options matter:
- You can set a math Braille format without changing your default Braille output table. Literary Braille and math Braille often use different codes, so this saves users from switching back and forth.
- Supported formats: Nemeth (default), UEB, CMU, Vietnamese, Swedish, LaTeX and ASCIIMath.
- Other settings: Narrator Math settings also cover reading language, speech behavior and navigation preferences.
Microsoft frames this around STEM learning, and that's reasonable. Equations have long been hard for screen-reader users. Microsoft limits the claim to "supported equations" in the four named apps and doesn't publish a compatibility list for particular displays or equation types. Schools and accessibility teams should test with their own hardware and course materials before relying on it.
Summary: Equations in Word, PowerPoint, Edge and Chrome can now appear on Braille displays in seven math formats, separate from your main Braille table.
Settings: Microsoft account benefits
Settings now makes it easier to see the benefits and services that come with your Microsoft account, including a welcome page for the feature. Microsoft doesn't say which benefits appear or which account types qualify.
This follows a pattern. Microsoft's notes for the previous Experimental build said Insiders with eligible Microsoft 365 subscriptions could upgrade through a dialog in Settings > Accounts. Tech blogger Erik Moreau's write-up of that build quoted the notes: users could do so through an integrated dialog in Settings > Accounts, rather than being redirected to a browser.
Some users will find this convenient. Others will see the Settings app becoming a place to sell Microsoft services. Both views are fair, and Insider feedback will probably decide how prominent the page ends up being.
Known issue: Task Manager CPU speed stops updating
Microsoft is investigating Insider reports that the CPU speed shown in Task Manager no longer updates after recent flights. The notes don't say which hardware is affected or offer a workaround. This build doesn't fix it either; it's listed as still under investigation.
If you're diagnosing performance on an Insider machine, don't rely on Task Manager's clock-speed reading for now. Check it against another monitoring tool.
Should you install it?
The usual Experimental-channel advice applies. Microsoft says features in these builds may change, be removed, or never ship. In its standard reminder, it notes they might change over time, be removed, or replaced and never get released beyond Windows Insiders. Keep this build off production machines.
Who should try it:
- IT admins who want to test the new Hello events in a lab before planning SIEM and audit work.
- Accessibility users and educators with refreshable Braille displays who want to test Narrator Math with real course material.
- Anyone who keeps triggering Sticky Keys by accident.
If a feature is missing after you install, assume the staged rollout hasn't reached you yet before you assume something went wrong. If you find bugs, especially with the Hello events or Braille math output, report them through Feedback Hub.