Where this build fits in the Beta Channel
The Beta Channel recently moved to a new base. As Neowin reported earlier this month, Microsoft moved testing to the recently released version 26H2 from 25H2, raising build numbers to 26320 from 26220. That first 26H2 Beta flight was 26320.9876. Because it is delivered via an enablement package (eKB), the higher number does not mean the user environment changes significantly.
A small revision followed. Admin365.Blog reported that KB5134539 for the Windows 11 26H2 Beta moved the build from 26320.9876 to 26320.9877, and noted at the time that release notes were not published, with known issues and fixes both still empty.
Build 26320.10003 is the first flight since that switch to come with a full set of notes. Microsoft's reminders confirm it is based on Windows 11, version 26H2 via an enablement package. The usual Insider warnings apply:
- The desktop watermark in the lower-right corner is expected on pre-release builds.
- Features may change, be removed or never ship beyond the Insider Program.
- Some in-development features may not be fully translated yet. Microsoft asks Insiders to report localization problems through Feedback Hub.
Section summary: This is a refinement flight on the new 26H2 Beta base. Its practical changes are more substantial than the version-number change that came before it.
File Explorer: This PC search now uses the index
Searching from This PC used to be one of the slower parts of File Explorer. Microsoft says This PC search now uses the Windows search indexer, making it "much faster" and consistent with searching from File Explorer Home.
This should help people who search from This PC by habit and then wait while Explorer crawls the drives. The notes leave a few things unsaid:
- They don't say which locations or file types are covered.
- They don't say whether results now depend on your indexing scope.
- They don't describe a staged rollout.
Analysis (based on general knowledge of how Windows Search works, not stated in Microsoft's notes): Any search that uses the index can only find what the index covers. If This PC results look incomplete on your Insider machine, check which locations Windows Search is set to index before you report a bug.
The second Explorer change is about feedback, not speed. When you open a location that takes a while to load, such as a network drive, Explorer now shows clearer progress indication so you can tell it's still working. Microsoft doesn't claim network drives load faster. The change just makes it obvious that Explorer hasn't hung.
BitLocker: standard users can set their own preboot PIN
This is the most important change for enterprise admins. Until now, users without admin rights couldn't add the TPM+PIN protector. Organizations that wanted preboot PINs had to give users admin rights, use a scripted workaround or have IT set the PIN for them. In this build, standard users on managed devices can add the PIN themselves.
How it works
When the required policies apply to a device that doesn't have a PIN yet, Windows shows a notification asking the user to add one. Selecting it opens a window where the user sets the BitLocker preboot PIN. Microsoft says every user targeted by the policies gets this prompt if their device lacks a PIN, not just standard users.
Policy configuration
Microsoft says to set four existing BitLocker policies in Microsoft Intune or another device management solution:
| Policy | Value |
|---|---|
| AllowStandardUserEncryption | ON |
| AllowWarningForOtherDiskEncryption | OFF |
| RequireDeviceEncryption | ON |
| SystemDrivesRequireStartupAuthentication | ON |
Use a test group only
Microsoft is explicit that the policy requiring startup authentication and device encryption should go only to a standard-user test group that has this feature enabled through the Windows Insider Program. If it reaches other devices:
- Standard users without the feature can't add the required TPM+PIN protector, so device encryption fails.
- Standard users without the feature whose drives are already encrypted with TPM only will report as non-compliant.
That second point affects more than BitLocker. Microsoft's BitLocker documentation says Intune can use BitLocker status in compliance policies together with Conditional Access. A wrongly targeted policy could therefore turn into users losing access to cloud services. Put another way, if this policy reaches your production fleet, the first sign may be a pile of helpdesk tickets.
Background from Microsoft's BitLocker documentation
These points come from Microsoft's general BitLocker configuration guidance, not from the build notes:
- PIN length: The minimum-length policy can require at least 4 digits, and the maximum is 20. If that policy isn't configured, users can choose any PIN from 6 to 20 digits.
- Brute-force protection: The TPM's dictionary attack protection limits how quickly PINs can be guessed. Microsoft gives the example of a TPM 2.0 allowing 32 guesses at once and then one more every two hours.
- Tablets and slates: The touch keyboard isn't available in the preboot environment. Devices without a physical keyboard need another way to enter the PIN, such as an attached USB keyboard. Check this before you give a PIN prompt to someone with a tablet that has no keyboard.
- Changing the PIN later: A separate policy controls whether standard users can change their BitLocker PIN or password after it's set. Check how it's configured on your test devices.
A pilot checklist
- Create a small group of standard users on devices enrolled in the Beta Channel and running Build 26320.10003.
- Apply the four policies above to that group only.
- Check that the notification appears on devices without a PIN, and that selecting it opens the PIN window.
- Reboot and confirm the preboot PIN prompt appears.
- Check compliance reporting in your management console for the pilot devices.
- Make sure no device outside the pilot is in a group that receives the startup authentication policy.
Section summary: TPM+PIN without giving users admin rights is a real improvement for security and administration. For now it's an Insider-only feature, and Microsoft's own notes warn that targeting the wrong devices will break encryption.
Offline Maps removed from Settings
Microsoft is removing the Offline Maps feature and related settings pages. This follows the deprecation of the Windows UWP Map control and Windows Maps platform APIs announced in April 2025. Two Settings locations are going away:
- Offline Maps under Settings > Apps > Offline Maps
- Maps storage under Settings > Storage > Local Disk
Microsoft's reasoning is simple: once the Maps control and APIs are removed, offline maps won't work anyway.
The timeline matters here. Microsoft's deprecated-features list says the UWP Map control and Maps platform APIs were deprecated on April 8, 2025, and would keep working but receive no updates. The standalone Maps app was deprecated around the same time, with removal from the Microsoft Store planned by July 2025. So deprecation in 2025 didn't stop anything working. The loss of offline maps is tied to the upcoming removal of the controls and APIs, and the build notes don't give a date for that.
Who's affected:
- Consumers: Anyone who downloaded offline maps for travel should plan to use another mapping tool.
- Developers: Microsoft's API documentation says the UWP MapControl and Windows.Services.Maps APIs rely on Bing Maps and may not be available in future Windows versions. If your line-of-business or kiosk app still uses them, you'll need to migrate.
Fixes: Remote Desktop, mouse cursor and voice typing
- Remote Desktop: Microsoft fixed an issue where RDP connections could fail on the client because of a certificate mismatch introduced in recent flights. The notes don't say which certificate or configuration was involved. If you used a workaround for this on Insider machines, test connections again after updating.
- Invisible mouse cursor: Microsoft fixed an underlying issue that made the cursor disappear unexpectedly in several scenarios in recent flights. The scenarios aren't listed.
- Voice typing: Configuring voice typing settings is now more reliable. Microsoft doesn't say what was failing before.
Known issue: Task Manager CPU speed stops updating
Microsoft is investigating Insider reports that the CPU speed shown in Task Manager stops updating after recent flights. If you use that number for thermal or power testing on an Insider machine, use another monitoring tool until Microsoft fixes it. This appears to be a display problem, and the notes give no sign that the processor itself is affected.
Bottom line
Build 26320.10003 is a modest update with a few practical changes:
- For everyone: Faster, index-based search from This PC, clearer loading feedback for network drives, and the end of the cursor and RDP certificate bugs.
- For admins: A long-requested BitLocker option to test, with Microsoft's warning to keep it within your pilot group.
- For travelers and developers: Offline Maps is being removed from Settings, so plan your move off the deprecated Maps platform now.
Is TPM+PIN for standard users enough to get more organizations using preboot authentication? Possibly. The admin-rights requirement was one of the main obstacles, and Microsoft is now removing it.
References
- Windows 11 Insider Beta Preview Build 26320.10003 Microsoft Learn - Windows Insider release notes · 2026-11-16T22:05:37Z
- KB5134539 for Windows 11 26H2 Beta: Build 26320.9877 Explained - Admin365.Blog admin365.blog
- Microsoft brings Windows 11 26H2 to Beta Channel Insiders - Neowin neowin.net