That headline feature arrived with a larger set of changes. On November 16, 2026, Microsoft released two Windows 11 Insider Preview builds, a day before Microsoft Ignite opened in San Francisco. Build 26320.10003 goes to the Beta channel and Build 26340.10013 to the Experimental channel, with both based on Windows 11, version 26H2. Below is what each channel gets, which features are in both, and the BitLocker warning admins should read before changing any policies.
FIDO2 passkey management: Experimental channel only
The security key improvement is only in Experimental Build 26340.10013. It is not in the Beta build. Besides deleting individual passkeys, Microsoft says admins can also configure enterprise settings such as minimum PIN length, always-required user verification, and enterprise attestation. The screenshot in Microsoft's release notes is captioned as showing security key management options for passkeys, PIN, and advanced settings.
Why it matters:
- Storage space: FIDO2 keys can only hold a limited number of discoverable credentials. Freeing one slot without wiping the rest makes it practical to keep using a key for years. (This is general background on FIDO2 hardware, not something Microsoft stated.)
- Revoking access: If you leave a service or rotate a credential, you can now remove just that passkey. As WinCentral put it, the old process often meant you had to wipe and reset the entire physical key—forcing you to re-register every single account from scratch.
- Enterprise controls: Minimum PIN length, user verification on every use, and enterprise attestation give admins tighter control over how keys are used on managed PCs.
What Microsoft hasn't said yet: The official notes don't list supported key models, don't confirm that every FIDO2 key supports the same management features, and don't give a step-by-step Settings path or the configuration route for the enterprise options. Until they do, treat specific menu instructions from third parties with caution.
It also helps to be clear about scope. This feature manages passkeys stored on the physical security key. It doesn't delete Windows Hello credentials, passkeys synced by a password manager, or passkeys saved in a browser profile. Geekrewind makes the same point: the new feature in the release notes covers only the passkeys on the FIDO2 security key.
Summary: You can now delete individual passkeys from a FIDO2 security key and admins get new PIN and verification controls, but only in the Experimental channel. Supported hardware and detailed setup steps haven't been documented yet.
Remote Lock: lock a lost PC without wiping it
The second major Experimental feature is for IT departments. IT administrators can remotely lock lost, stolen, or compromised Windows devices through Microsoft Intune. The feature signs out active sessions, hides sign-in options, and displays a Device Locked screen.
The important difference from a wipe is that nothing gets deleted. According to Microsoft, the device stays enrolled and managed, BitLocker stays on, and user data stays in place. Only an admin can lift the lock remotely, after which the user can carry on where they left off. Admins can show their own message and help desk contact details on the lock screen using the LockReason and RecoveryHint settings.
Until now, help desks dealing with a missing laptop often had to choose between doing nothing and wiping it. A remote wipe is a bad outcome if the laptop turns up under a car seat the next day. Remote Lock sits between those two options. Microsoft's notes don't cover licensing, Intune prerequisites, or the exact admin workflow, so check those before you add it to an incident runbook.
Summary: Remote Lock lets IT secure a missing device through Intune and bring it back without data loss. It's currently Experimental-only, and the operational details are still to come.
More Experimental changes: Pluton, the taskbar, Magnifier and account switching
- Pluton Cryptographic Provider (developer preview): We're introducing a preview of the Microsoft Pluton Cryptographic Provider, enabling developers on supported devices to use the Pluton security processor for hardware-protected cryptographic key storage and operations through standard Windows CNG APIs. Microsoft doesn't list which devices are supported.
- Taskbar list view: Hovering over a taskbar app still shows thumbnails by default. You can switch to a list of window titles under Settings > Personalization > Taskbar, which helps when you have a dozen windows that all look the same as thumbnails.
- Magnifier touch and touchpad gestures: Magnifier has to be running first (press Windows key + Plus (+)).
- Touchpad: swipe up or down with three fingers to zoom in or out, move one finger to pan, and tap with three fingers to switch between 100% and your previous zoom level.
- Touchscreen: drag with three fingers to pan. To zoom, tap once with three fingers, tap again and keep them down, then drag up or down. Double-tap with three fingers to switch between 100% and your previous zoom level.
- Both gesture sets are on by default. You can turn off either one under Settings > Accessibility > Magnifier with the "Control Magnifier with touchpad gestures" and "Control Magnifier with touch gestures" toggles. The Magnifier toolbar also gets a new help (?) button that links to support articles, a summary of new features, and Feedback Hub.
- Switching from a Microsoft account to a local account: Microsoft also adds a useful security safeguard when switching from a Microsoft account to a local account. Windows will now prompt users to back up their BitLocker recovery key with updated instructions. If you've ever had to recover a PC with no recovery key on file, you'll know why this matters.
- Spotlight fix: The Explore Background option in the right-click menu for Windows Spotlight desktop backgrounds works again.
BitLocker preboot PINs for standard users, with a warning
This change is in both builds, which some early coverage didn't make clear. Standard users on managed devices can now set a BitLocker preboot PIN themselves. Previously, users without admin rights couldn't add the TPM+PIN protector. Once the relevant policies apply to a device that doesn't have a PIN yet, Windows shows a notification, and selecting it opens the PIN setup window.
Microsoft lists these existing BitLocker policies, which you can set in Intune or another device management tool:
| Policy | Required value |
|---|---|
| AllowStandardUserEncryption | ON |
| AllowWarningForOtherDiskEncryption | OFF |
| RequireDeviceEncryption | ON |
| SystemDrivesRequireStartupAuthentication | ON |
Before you turn these on: Microsoft says to target the startup-authentication and device-encryption policies only at a test group of standard users who have this Insider feature enabled. Standard users who don't have the feature can't add the TPM+PIN protector, so device encryption will fail under this configuration. Users without the feature who are already encrypted with TPM only will show as noncompliant. If you apply these policies to your whole organization, expect a lot of help desk tickets.
A safe pilot, step by step
- Set up a small device group of standard-user machines enrolled in the Insider Beta or Experimental channel.
- Confirm those devices are on Build 26320.10003 or 26340.10013. In the Experimental channel, also check that the feature has actually reached them, because Microsoft rolls features out gradually.
- Assign the four policies above to that group only.
- Check that users get the PIN notification and can set a PIN.
- Watch compliance reports for unexpected encryption failures before expanding the pilot.
Summary: Self-service preboot PINs could take a lot of manual work off IT teams. For now, keep them to a pilot group, because applying the policies too widely will break encryption compliance.
Beta channel: faster File Explorer search, and Offline Maps removed
Beta Build 26320.10003 includes a change many people will notice: searches from This PC in File Explorer now use the Windows search indexer. Microsoft says this makes them much faster and consistent with searches from File Explorer Home. Progress indicators for slow locations such as network drives have also been improved, so it's clearer that a folder is still loading rather than stuck.
Both builds also remove Offline Maps. Microsoft points to its April 2025 announcement that the Windows UWP Map control and Windows Maps platform APIs are being deprecated, and says Offline Maps won't work once those are removed. Two Settings pages go away: Settings > Apps > Offline Maps and the Maps storage entry under Settings > Storage > Local Disk. Developers who still rely on the UWP Map control should treat this as a reminder to migrate.
Fixes and one known issue
Both builds fix:
- Remote Desktop Protocol connections failing on the client because of a certificate mismatch after recent flights.
- The mouse cursor becoming invisible in some situations.
- Unreliable voice typing settings.
Known issue in both builds: reports that the CPU speed shown in Task Manager stops updating are under investigation. If your CPU appears frozen at one clock speed, it's most likely the Task Manager bug rather than a hardware problem.
The big picture
These features are still previews. Microsoft notes that many Experimental features roll out gradually through Controlled Feature Rollout, so two testers on the same build may not see the same things. It also says Insider features can change, be removed, or never ship to everyone. Not everyone can easily switch channels right now either: Microsoft is temporarily blocking moves from Experimental or Beta into the Experimental (Future Platforms) channel.
Even so, the overall direction is clear. Passkey cleanup, a lock option that doesn't destroy data, user-set BitLocker PINs, and recovery-key reminders are practical fixes for problems help desks deal with every week. The FIDO2 change is the headline because it fixes an obvious gap: deleting one credential shouldn't mean wiping every other credential on the key. The bigger questions are whether Microsoft documents supported keys and admin controls before general release, and whether the BitLocker PIN policies become safe to apply widely.
Try the Experimental build if you have spare hardware and a FIDO2 key you don't mind experimenting with. If you're an admin, read the BitLocker warning above before you change any policies.
References
- Windows 11 Insider adds FIDO2 passkey deletion - Notebookcheck Notebookcheck · 2026-11-17T07:08:00+00:00
- Windows 11 Insider Experimental Preview Build 26340.10013 - Windows Insider Program learn.microsoft.com
- Windows 11 Insider Beta Preview Build 26320.10003 - Windows Insider Program | Microsoft Learn learn.microsoft.com