Windows 11 Insider Build 26120.6772: Copilot AI, ESS Peripherals, OOBE Folder Name

Microsoft is rolling out Windows 11 Insider Preview Build 26120.6772 (KB5065797) to the Beta Channel, and this flight brings targeted AI-driven enhancements for Copilot+ PCs, a notable expansion of Windows Hello Enhanced Sign‑in Security to peripheral fingerprint readers, new OOBE options for naming your user folder, and a spate of usability and dark‑mode fixes across File Explorer and camera effects.

Background​

This release continues Microsoft’s pattern of delivering Beta Channel updates as an enablement package on top of Windows 11, version 24H2. Build 26120.xxxx-style updates are checkpoint cumulative updates that preview servicing and feature rollouts; many items are introduced via Controlled Feature Rollout, meaning features may appear only for a subset of Insiders initially and expand later. The build number and KB (Build 26120.6772 / KB5065797) identify the package being pushed to Beta-channel Insiders on October 6, 2025.
Two important program mechanics to keep in mind:

• The Beta Channel uses a toggle — Get the latest updates as soon as they’re available — that accelerates feature rollouts to consenting Insiders; features are often gated and gradually enabled across devices.
• Features shown in Insider builds may change, be removed, or never reach public release; many items in this build are still flagged as preview or controlled rollouts.

---

What’s new in Build 26120.6772​

Click to Do: Image Object Select and Unit Conversion (Copilot+ PCs)​

• Image Object select in Click to Do adds precise on-screen object selection. Hovering previews selectable areas, enabling copy/paste of isolated objects into other apps or to seed a Copilot conversation for further edits or context-aware tasks. This brings a quick visual editing flow to the system-level overlay rather than requiring a full image editor for simple extract-and-paste operations.
• Unit conversion recognizes number + unit combinations on screen (length, area, volume, weight, temperature, speed) and offers an inline conversion tooltip on hover and more options in the Click to Do context menu. Copilot integration surfaces extended conversions and follow-up actions.

These changes are explicitly targeted at Copilot+ PCs, where Click to Do and related on-device AI features are prioritized. The Click to Do experience is designed to analyze content locally and hand off only what the user elects to Copilot, preserving the choice to keep content local.
Practical implications:

• Users on supported Copilot+ hardware can expect faster image-focused workflows and in-place conversions without opening a separate app.
• Some Click to Do features remain region-limited; unit-conversion and Copilot-hand‑offs may be unavailable in certain jurisdictions during preview.

Windows Hello: ESS Expanded to Peripheral Fingerprint Sensors​

The build advertises that Windows Hello Enhanced Sign‑in Security (ESS) now supports peripheral fingerprint sensors. Historically, ESS required built‑in sensors that supported match‑on‑sensor (match‑on‑chip) capabilities and specific hardware/firmware support. The new messaging indicates that plug‑and‑play external fingerprint readers that meet ESS requirements can now enroll and participate in the stronger, VBS-backed biometric protection model.
Important caveats and verification:

• ESS requires specific hardware, drivers, and firmware to isolate biometric matching inside Virtualization‑Based Security (VBS) and to store templates securely; peripheral support depends on the sensor being ESS‑capable (match on sensor, embedded certificate, driver support).
• Peripheral support is being rolled out as part of a controlled preview; availability will vary by peripheral vendor, device driver, and OEM firmware.
• Even with the build enabling this capability, real‑world success will depend on vendors issuing appropriately certified sensors and drivers.

Security implications:

• When peripheral sensors truly support ESS (match‑on‑chip with proper certificates), the security model is strengthened because biometric matching and templates remain isolated from the main OS.
• If a peripheral lacks ESS support, it may still function when ESS is temporarily disabled or when a system provides toggles to allow external devices, but that reduces the protection surface.

Windows Setup (OOBE): Name your default user folder; local‑only account paths removed​

• You can now set a custom default profile folder name during OOBE by invoking Command Prompt (Shift + F10) on the Microsoft account sign‑in page, changing into the OOBE folder, and running: SetDefaultUserFolder.cmd <YourFolderName>. The name is limited to 16 characters and supports Unicode; special characters are stripped.
• Microsoft is also removing known mechanisms that allowed creating local accounts during OOBE. The rationale: some local‑account bypasses skipped critical setup screens and led to incompletely configured devices. Going forward, OOBE will require internet and a Microsoft account to proceed in the default path.

Impact and notes:

• The SetDefaultUserFolder option is a pragmatic nod to real user needs (shorter profile folder names, non-email‑based folder names) and is useful for administrators creating images or users who dislike the auto-generated folder names derived from email addresses.
• Removing local account bypasses affects installers, kiosk setups, and administrators who relied on offline OOBE workarounds. Enterprises and power users should plan for updated imaging scripts and deployment processes.

File Explorer: Dark Mode polish for core dialogs​

File Explorer receives targeted dark‑mode fixes to make common dialogs (copy/move/delete default and expanded states), progress bars, chart views, and confirm/error dialogs consistently respect dark mode. This is a focused cosmetic and usability improvement that removes jarring light panels during critical file operations.
User benefit:

• Improved visual consistency and reduced eye strain for users who run dark theme system‑wide.

Windows Studio Effects: Fix for external webcams​

This build fixes a class of failures where enabling Windows Studio Effects on some external webcams could cause the camera preview to fail. If you had previously disabled Studio Effects as a workaround, the release notes state you should be able to re‑enable it now.
Practical note:

• Studio Effects are still gated to supported hardware and may require updated drivers. External webcam support is an important improvement for docking scenarios and hybrid setups where an attached USB camera is preferred.

Miscellaneous fixes​

• Taskbar: fixes for “automatically hide the taskbar” peeking issues and focus bugs when activating app preview thumbnails.
• File Explorer EFS dialogs: responsiveness corrected for increased text scaling.
• Networking: corrected incorrect link speed reporting on certain adapters.
• Hyper‑V: fixed a problem starting VMs with TPM on ARM64 hardware.
• Protected content playback: fixes for playback problems in apps using Enhanced Video Renderer with HDCP enforcement.
• Xbox Controller Bluetooth bugcheck workaround guidance is included for affected Insiders.

---

Known issues to watch​

This flight lists several known issues Insiders should be aware of:

• Click to Do: a right‑edge swipe to launch Click to Do on the primary display may show the swipe visuals on the wrong display.
• Lock/login screens: a new issue where the touch keyboard may fail to launch on the login screen — the on‑screen keyboard from Accessibility can be used as a workaround.
• Taskbar hover/preview animations temporarily disabled because they interfered with window sharing from previews.
• Search: some queries may show unexpected text instead of expected results and images.
• Xbox Controllers via Bluetooth: some configurations can cause a bugcheck; a Device Manager uninstall of the specific XboxGameControllerDriver.inf is suggested as a temporary fix.

These caveats underscore the preview nature of the release: expect occasional user experience regressions, especially when multiple system subsystems (VBS/ESS, camera stacks, Copilot overlays) interact.

---

How to get this build and test the new features​

• Enroll in the Windows Insider Program and ensure your device is in the Beta Channel.
• To receive controlled‑rollout features quickly, turn On the toggle: Settings > Windows Update > Get the latest updates as soon as they’re available.
• Check Windows Update for the KB5065797 (Build 26120.6772) package and apply it.
• For OOBE folder naming (new installations): when on the Microsoft account sign‑in page in OOBE, press Shift + F10, run:
• cd oobe
• SetDefaultUserFolder.cmd <YourFolderName>
  Observe the 16‑character limit and Unicode-only support; special characters will be removed.

Safety checklist before installing on production machines:

• Back up important data and create a restore point or system image.
• If you rely on third‑party peripherals (fingerprint readers, webcams), confirm vendor driver availability and be prepared to roll back drivers if enrollment fails.
• For corporate or imaging scenarios, test OOBE changes and SetDefaultUserFolder interactions in an isolated lab first.

---

Technical verification and cross‑checks​

This coverage is based on Microsoft’s official Windows Insider blog announcement for Build 26120.6772 together with product documentation for Click to Do and Windows Hello Enhanced Sign‑in Security that describe hardware and driver requirements. Independent reporting from major Windows coverage outlets corroborates the feature focus for Copilot+ PCs, Click to Do capabilities, and the ongoing phased rollout approach. The combination of Microsoft’s product documentation and independent reporting confirms the following core points:

• The build number and KB are accurate for the Beta Channel release.
• Click to Do is being developed as a Copilot-integrated overlay to analyze content locally and offer image and text actions; the new image object selection and unit conversion are logical extensions of existing Click to Do capabilities.
• ESS peripheral support is now advertised as available in the build, but the security model remains conditional on sensor capabilities (match‑on‑chip, embedded certificates), drivers, and OEM firmware.

Cautionary note: Peripheral ESS support is both a platform change and a hardware ecosystem change. While the OS may now accept peripheral sensors under ESS, vendors still need to ship properly certified sensors and drivers — so end‑user experience will vary widely across devices and peripheral models.

---

Security, privacy, and usability analysis​

Security: ESS expansion is meaningful but conditional​

Expanding Enhanced Sign‑in Security to peripheral fingerprint readers is an important security milestone. ESS isolates biometric matching and templates inside VBS, reducing the attack surface for biometric theft. However, the security guarantee hinges on the peripheral meeting strict hardware and firmware expectations:

• Match‑on‑chip (match‑on‑sensor) is required so that raw biometric data does not leave the sensor.
• The device must include an embedded certificate and compatible driver to participate in the ESS trust model.
• System firmware and OEM configuration may be required to register secure devices with the secure kernel.

If a peripheral lacks those guarantees, users may need to disable ESS or rely on legacy drivers — which weakens the security posture. Administrators should vet peripheral vendors and demand ESS-capable sensors if they intend to adopt external fingerprints widely.

Privacy: Click to Do and Copilot hand‑offs remain opt‑in​

Click to Do’s design premise is local analysis with user choice to hand off content to Copilot. That model mitigates broad telemetry concerns, but features that capture screen content, convert units, or extract objects raise legitimate privacy questions if Copilot handoffs are not clearly surfaced. Organizations should ensure policy settings and user education clarify when content is shared beyond the local device.

Usability: OOBE changes are a double‑edged sword​

Requiring Microsoft account sign‑in during OOBE eliminates common local‑account bypasses that caused misconfigured devices, but it reduces flexibility for certain deployment or privacy‑conscious scenarios. The SetDefaultUserFolder.cmd offers a pragmatic mitigation for folder‑name control, but administrators will need to update their imaging and provisioning documentation.

---

Enterprise and deployment considerations​

• Imaging and provisioning: Automated deployments and syspreped images should be tested against the new OOBE behavior. Scripts or deployment tools that previously relied on local account creation during OOBE may need rework.
• Peripheral certification: Enterprises planning to provision external fingerprint sensors should request ESS compatibility documentation from vendors and verify match‑on‑chip support and driver signing.
• Testing matrix: Because Click to Do and other Copilot features are targeted to Copilot+ hardware, enterprises should map devices against Copilot+ hardware requirements before rolling out preview features to user groups.
• Policy controls: IT teams may want to validate available Group Policy / MDM controls for Click to Do, Copilot, and ESS toggles to ensure compliance with organizational privacy and security policies.

---

Troubleshooting tips and practical fixes​

• If Windows Studio Effects causes a camera preview failure: re-enable the setting in Advanced Camera options after updating to this build; ensure external webcam drivers are current.
• If Xbox Controller via Bluetooth is causing system bugchecks: uninstall the device driver entry named “oemXXX.inf (XboxGameControllerDriver.inf)” under Devices by Driver in Device Manager, then let Windows re-enumerate.
• For touch keyboard not appearing on login: use the on‑screen keyboard from the accessibility menu as an interim workaround; expect a fix in a subsequent flight.
• If Windows Hello enrollment fails for a peripheral: confirm the vendor driver is published and signed, and check for a registry/configuration key indicating ESS capability. If issues persist, submit feedback through Feedback Hub under Security and Privacy > Windows Hello Fingerprint.

---

Verdict and recommendations​

Build 26120.6772 is a focused Insider release that expands AI‑centric productivity tools while advancing biometric security for external devices. Key takeaways:

• For enthusiasts and testers on Copilot+ hardware: this build delivers meaningful workflow improvements (image object extraction, in‑place unit conversion) that make Click to Do noticeably more useful.
• For security‑minded users and admins: the ESS expansion to peripheral fingerprint readers is promising but must be treated as conditional — real security benefits require certified sensors and updated drivers.
• For IT and deployment teams: OOBE changes require updated provisioning documentation and testing; the SetDefaultUserFolder.cmd is useful but limited by character rules and is applied during initial setup only.

Recommended actions:

• Test this build in a lab environment or on non‑critical devices first.
• Validate peripheral drivers and vendor ESS support before adopting external fingerprint readers widely.
• If you rely on local account creation for deployments, update your workflows and test SetDefaultUserFolder in your imaging process.
• Use Feedback Hub to report any regressions that affect your hardware or workflows so Microsoft can iterate on these previews.

---

Build 26120.6772 continues Microsoft’s steady cadence of delivering incremental AI features and hardening sign‑in security in parallel. For Insiders, it’s an opportunity to evaluate more capable Click to Do interactions and to pilot ESS for external fingerprint readers — but the usual tradeoffs of preview software remain: careful testing, cautious rollouts, and readiness to revert if hardware or driver interoperability proves brittle.

---

Source: Microsoft - Windows Insiders Blog Announcing Windows 11 Insider Preview Build 26120.6772 (Beta Channel)