Microsoft on November 6 (local time) updated the delivery builds of "Windows 11 Insider Preview." The biggest change this time is that the foundation of the Beta Channel's standard release has switched to "Windows 11 version 26H2," with the build number raised to "26320." Because it is delivered via an enablement package (eKB), the higher number does not mean the user environment changes significantly.
The main builds currently being rolled out are as follows.
ChannelTarget versionBuild numberBeta26H226320.9876Beta26H128020.3445Experimental26H226340.9882Experimental26H128120.3454ExperimentalFuture Platforms29704.1000
Note: Based on the delivery status the company announced as of November 6.
In the Experimental (26H2) channel, where experimental features are tried first, efforts to improve the "Windows Hello" sign-in experience are being rolled out gradually. Previously, users could not enter a PIN until face or fingerprint authentication was complete, but going forward they will be able to type their PIN in parallel while biometric authentication is processing. The system completes sign-in or unlock with whichever authentication method succeeds first, and the company explains that this makes the overall procedure more consistent and easier to understand.
However, in some situations, such as immediately after a restart, PIN entry is still requested first. After that, biometric authentication can be used as usual.
In the Beta Channel (26H2), some of the new features being tested on the Experimental side are also being rolled out sequentially. These include a redesigned "Windows Search," a feature to check shared cloud storage usage for "Microsoft 365 Family" from the Settings app, a feature that temporarily brightens the screen during Windows Hello face authentication to improve recognition rates, and a change that allows the "~" (tilde) character to be handled in the File Explorer address bar. The first release of the new Windows Search will be English-only.
In the Experimental (Future Platforms) channel, new builds are scheduled to be delivered weekly over the coming weeks, interspersed between standard builds. These are synthetic cumulative updates for validating backend delivery and update services and do not include new features. No release notes or blog posts will be published, and the version will be confirmed via "Flight Hub."
This build migration is a reorganization of the development channels and does not involve feature additions for general users. However, with the delivery framework centered on 26H2 now in place, future preview validation will proceed with 26H2 at its core. It can be said that the stage has been reached where evaluation of candidate features for the next update, such as Windows Hello authentication improvements and the new search, will begin in earnest.
Separately, on November 8, the company also presented its views on delays in applying security updates in an official blog. According to diagnostic data from August 2026, fewer than half of the corporate Windows devices surveyed had finished applying security updates within two weeks of their release, and even after four weeks about one in four had not applied them. Noting that the use of AI has shortened the development of exploit code targeting vulnerabilities to the order of hours, the company listed reducing the time from release to application as a priority issue. Windows 11 also offers mechanisms such as "Windows Autopatch," which manages phased distribution, and hotpatching, which applies monthly updates without a restart.
Preview validation and update management for corporate devices are separate contexts, but both reflect the same challenge: how to deliver updates quickly and ensure they take hold. With the 26H2-based Beta Channel now fully operational, future developments will be watched closely on both the feature validation and quality management fronts.
