About this article
This article is created using an automated generation workflow powered by generative AI. It is organized based on source information, but has not been verified on a physical device by the author.
Verification Status: unverified (Not verified on actual hardware)
In the Windows 11 Insider Preview released on October 7, 2026, multiple builds were provided for the Beta and Experimental channels, introducing a new WinUI 3-based Windows Search and a Battery Status widget that consolidates peripheral battery levels. Since the availability of each feature varies by channel and branch, it is important to understand the applicable build and usability changes for your environment.
- Overview of builds distributed on October 7, 2026 and target channels
- Functional changes in Windows Search brought by WinUI 3 renewal and inline actions
- Battery Status widget for centrally managing peripheral power status
- Impact and boundary conditions from a system administration and operations perspective
- How to check the version and build number
- Points to check and limitations before deployment
- Reference Information
Overview of builds distributed on October 7, 2026 and target channels
According to primary sources, this update simultaneously announces multiple build numbers for the Beta channel, Experimental channel, and specific branches.
The breakdown of the published build numbers is as follows:
Beta Channel: Build 26220.9606
Experimental Channel: Build 26340.9616
Beta Channel (26H1): Build 28020.3172
Experimental Channel (26H1): Build 28120.3181
Experimental Channel (Future Platforms): Build 29683.1000
Releases are divided not only into standard Beta/Experimental lines, but also into the 26H1 branch and builds for future platforms (Future Platforms). Testing of new UI components and system features is structured to be rolled out primarily in the Experimental channel first, and available new features vary depending on the participating channel and build number.
Functional changes in Windows Search brought by WinUI 3 renewal and inline actions
One of the major changes in this update is the revamp of the Windows Search interface. This new feature has started rolling out to the Experimental and Experimental (26H1) channels.
UI and processing efficiency improvements through the adoption of WinUI 3
Primary documentation explains that the new Windows Search has been rebuilt using WinUI 3 as its foundation. This results in faster and more efficient operation, alongside a streamlined design that makes search results easier to view and scan.
Direct operations using inline actions
In the conventional Windows Search, the typical workflow involved searching for a settings item and then navigating to the corresponding page in the Settings app to perform operations. This update introduces "inline actions" that allow tasks to be completed directly within the search results. Specific examples of actions listed in the primary documentation are as follows.
Toggling dark mode
Turning Bluetooth on and off
Adjusting screen brightness
Muting the device
Arranging windows (window snapping)
Since hardware controls and system layout changes can be performed directly from the search field, the intention is to reduce the number of user actions required.
Improved comprehension of typos and synonyms
Improvements have also been made to search query processing capabilities. According to the primary documentation, matching accuracy for input typos and synonyms has been improved, and adjustments are underway to make it easier to find desired settings and applications even with minor input variations.
Battery Status widget for centrally managing peripheral power status
For the Experimental channel, the "Battery Status widget" has been added to expand the widget board.
Consolidated display of remaining battery levels
A UI is provided that collectively displays the remaining battery levels not only of the laptop itself but also of connected peripherals in one place. It is designed so that the battery levels of peripherals—which previously required opening the Bluetooth device list in the Settings app or dedicated utilities individually—can be understood at a glance on the widget board.
Widget addition procedure
The UI configuration procedure for using the Battery Status widget is described in the primary documentation as follows.
Open the widget board
Select Add widgets
Select and place Battery Status
This widget helps ensure you do not miss the charging time for devices such as the mouse, keyboard, or headset while working.
Impact and boundary conditions from a system administration and operations perspective
When verifying new features in preview environments or managing enterprise devices, several boundary conditions and operational considerations must be taken into account.
Uneven feature availability across channels and branches
This new feature is not distributed uniformly to all builds.
Refreshed Windows Search: Experimental, Experimental (26H1)
Battery Status widget: Experimental
Beta channel builds (Build 26220.9606 and Build 28020.3172) do not explicitly list these prominent features as of this announcement. When performing validation, you must verify that the target device is registered to the appropriate preview channel.
Phased rollout and risk of behavioral spec changes
The primary documentation states We are beginning to roll out and We will continue fine tuning these improvements, meaning that even if the target build is installed, the features may not be enabled for all users immediately. Additionally, items controllable via inline actions and the search query recognition algorithms are subject to specification changes based on future feedback.
How to check the version and build number
You can check which build your environment corresponds to via the Windows Settings app or PowerShell.
Procedure for checking in the Settings app
[Before physical device verification]
Open Settings from the Start menu
System>Select "About"
Check the "OS Build" number in the "Windows specifications" section
Retrieving the build number using PowerShell
This is an example for quickly checking build information via a script or command line.
Example file save name:
check_os_build.ps1Prerequisites for execution: Windows PowerShell 5.1 or PowerShell 7.x (can be executed with standard user privileges)
: The current OS version, build number, and revision number are displayed in the console [Before device verification]
# check_os_build.ps1
# 実行中のWindowsビルド情報を取得するスクリプト
$os = Get-CimInstance -ClassName Win32_OperatingSystem
$buildInfo = [System.Environment]::OSVersion.Version
[PSCustomObject]@{
Caption = $os.Caption
Version = $os.Version
BuildNumber = $os.BuildNumber
BuildDetails = $buildInfo.ToString()
} | Format-List
By running this command and verifying whether the displayed BuildNumber and Version match the newly announced target build (such as the 26340 or 28120 series), you can determine whether the feature prerequisites are met.
Points to check and limitations before deployment
The items and limitations that must be verified in advance regarding this release are as follows.
Build and channel verification: Verify whether the target device belongs to the Experimental channel where the desired feature (WinUI 3 Search or Battery Status widget) resides.
Staged rollout of features: Even on target builds, the new UI may not appear immediately due to rollout controls such as A/B testing.
Peripheral compatibility status: The protocols and types of peripherals that can be displayed in the Battery Status widget may depend on the connected device driver and OS support status.
Restrictions on Business Environment Deployment: Because the Insider Preview Experimental channel includes early-testing features, it should not be used on mission-critical business devices, but rather limited to isolated evaluation and testing environments.
Reference Information
- Announcing new builds for 7 October 2026: https://blogs.windows.com/windows-insider/2026/10/07/announcing-new-builds-for-7-october-2026/
