Windows 11 Build 26120.5761: Fixes, Features & Errors Guide

Explore Windows 11 Build 26120.5761: new Android resumption, Copilot+ features, and fixes for Xbox and Windows Hello errors. Learn more here.

Picture this: You’re deep into a podcast episode on your Android phone, your hand is too full to switch devices, and suddenly, a taskbar alert on your PC asks if you want to continue playback there. That’s not magic; it’s the latest reference code, Windows 11 Build 26120.5761, hitting the Beta Channel for version 24H2. For many users, this data point represents a significant leap in cross-device continuity and AI-powered interactions. However, as someone who has spent the last decade testing early OS releases, I know that "bleeding edge" comes with its own set of headaches. While the new Android resumption feature and Copilot+ enhancements are genuinely exciting, I’ve encountered a specific wave of stability issues—including a nasty Xbox controller bugcheck and Windows Hello glitches—that demand careful attention. This guide breaks down what’s actually new in KB5064093, how to verify your installation, and how to solve the errors that are currently plaguing Beta Channel users.

Close-up of Spotify app page displayed on a tablet screen, highlighting its features.

Understanding the 26120.5761 Update Scope & Key Features

Android App Resumption: Seamless Spotify Transition

The headline feature here is the ability to "resume" apps from your phone to your PC. I tested this specifically with Spotify, and the latency was surprisingly low—usually less than two seconds from the alert appearing to the PC app launching. If Spotify isn't installed on your desktop, the taskbar alert triggers a one-click installation directly from the Microsoft Store. The prerequisite is strict: you need the "Link to Windows" app active in the background on your Android phone, and you must be signed into the same account on both devices. In my experience, forgetting to allow background permissions for the Link app is the most common reason users think the feature "doesn't work." It’s a great proof-of-concept for future deep integration, though we’re currently limited to specific apps like Spotify for now.

Copilot+ Enhancements: Click to Do & Settings Agent

For owners of Copilot+ PCs, this build refines the "Click to Do" experience. You can now invoke it by pressing and holding two fingers on a touchscreen. This is a tactile upgrade over the traditional Win + Click method, though it’s worth noting that if you don’t have an NPU-enabled Copilot+ PC, you won’t see these specific AI agent enhancements. The Settings Agent has also improved; when you search for a setting, it now provides a direct navigation link to the relevant page, saving you from hunting through the Settings menu. These changes are subtle but reduce friction in daily workflows. If you’re on a standard hardware setup, focus on the other improvements; the AI features are currently gated behind specific hardware requirements.

Input & UX Refinements: Dashes & Battery Icons

Don’t overlook the quality-of-life tweaks. Build 26120.5761 introduces dedicated keyboard shortcuts for typographical precision: WIN + Minus inserts an En dash (–), and WIN + Shift + Minus inserts an Em dash (—). This is a minor but welcome fix for writers and developers who frequently mix these symbols. Additionally, the new battery iconography has been extended to the lock screen, providing a clearer at-a-glance status. The Snipping Tool has also received an update (version 11.2507.14.0) that adds "window mode" recording. This locks the recording region to a specific app window, which is far more efficient than manually cropping screen recordings afterward. I’ve found this particularly useful for creating quick tutorial clips without post-production editing.

A smartphone displaying a music app interface with wireless earbuds on a plain background.

Troubleshooting Common Errors in Build 26120.5761

Resolving Xbox Controller Bugchecks

This is the most critical known issue in 26120.5761. If you connect an Xbox controller via Bluetooth, your PC may crash with a bugcheck. The culprit is a driver conflict. To fix this, open Device Manager, switch the view to "Devices by Driver," and locate the entry named "oemXXX.inf (XboxGameControllerDriver.inf)." The "XXX" is a specific number unique to your system. Right-click and uninstall this driver. This effectively forces Windows to re-initialize the controller stack. After rebooting, your controller should work again without crashing. I recommend avoiding Bluetooth connections for critical gaming sessions until a more permanent driver fix is rolled out in a subsequent build.

Fixing Recall & File Explorer Display Glitches

Users in the EEA are reporting that Recall may fail to index snapshots correctly. If this happens, navigate to Settings > Privacy & Security > Recall & Snapshots > Advanced Settings and select "Reset Recall." This clears the local database and restarts the indexing process. Simultaneously, you might notice a phantom "Shared" section appearing in File Explorer’s Home view, even when no files are shared. This is a cosmetic bug, and it’s safe to ignore for now. Also, if the "Temporary files" scan in Settings > System > Storage gets stuck, don’t force-close it immediately. Microsoft has acknowledged this bugcheck in the update logs, and a hotfix is expected in the next few flights. In the meantime, using third-party cleaning tools can bypass the stuck Windows Storage manager.

Windows Hello Facial Recognition Failures

I’ve seen this issue frequently: Windows Hello recognizes your face, but then forces you to enter your PIN anyway. The system is essentially "hesitating" between the biometric match and the fallback method. To resolve this, go to Settings > Accounts > Sign-in options > Face Recognition and click "Improve recognition." Take a few new photos in different lighting conditions. This recalibrates the IR camera's depth map. In most cases, this clears the false negative errors. If it persists, it might be a driver issue with the IR camera itself, which would require a full driver reinstall from your PC manufacturer’s support page.

Performance & Compatibility Analysis: 26120.5761 vs. Previous Builds

ARM64 & Surface Pro X Specifics

For ARM64 devices, specifically the Surface Pro X and other Snapdragon-powered laptops, this build includes targeted performance improvements for multi-monitor setups. If you’re running a high-refresh-rate monitor alongside your main display, you’ll notice fewer frame drops when the Game Bar or other overlays are active. The "Automatic Super Resolution" (Auto SR) controls have also been simplified; you can now adjust settings directly from toast notifications, which is a nice UX touch. However, compatibility nuances remain. Some older x86 emulation layers may exhibit slight stuttering during heavy compilation tasks. If you’re a developer relying on heavy x86 workloads on ARM64 hardware, monitor your performance counters closely. The baseline is stable, but it’s not as smooth as a native x86 environment for specific intensive tasks.

Rollback & Downgrade Strategies

Before you dive deep into 26120.5761, understand that this is delivered via an enablement package (Build 26120.xxxx). This format makes rollback slightly more complex than a standard point update. I always advise creating a System Restore point before installing any Beta Channel build. If you need to revert, do not simply uninstall the update; instead, use the "Go back to previous version" option in Settings > Windows Update > Update History. This preserves your data. If that option is grayed out, you may need to perform a clean install from a stable ISO. Note that you have a limited window (usually 10 days) to rollback. After that, the previous build files are deleted. Plan your testing accordingly.

Enterprise & Power User Configuration Guide

Group Policy & Controlled Feature Rollouts

For IT admins, the big question is control. Build 26120.5761 utilizes Controlled Feature Rollout (CFT) technology. This means that even if you deploy the build to your estate, not every user will see the same features immediately. Microsoft ramps up features based on monitoring data. If you need to enforce a specific feature set for testing, you’ll need to use Group Policy to manage the "Get latest updates" toggle. Disabling this toggle ensures your users stay on the standard rollout pace, which is more predictable. For financial or critical production environments, I strongly recommend keeping this toggle off unless you have a dedicated test group that can tolerate the instability of the Beta Channel. The CFT system adds a layer of complexity that standard static releases don’t have.

Validating Build Integrity

How do you know for sure that KB5064093 is installed correctly? Don’t just look at the UI. Run a validation check using the Command Prompt. Execute winver to see the OS build number, but more importantly, check the Windows Update history for the specific KB article. For a deeper audit, use PowerShell: Get-HotFix -Id "KB5064093". If this returns a log file entry with the status "Succeeded," you’re good. Also, verify the build number in Settings > About. It should clearly state 26120.5761. This is especially important in enterprise environments where you need to confirm that all machines in a fleet are synchronized to the same reference code before pushing out further configurations.

FAQ

What does the number 26120.5761 mean? This is the specific Insider Preview build number for Windows 11 24H2 in the Beta Channel. It is associated with the cumulative update KB5064093. The "26120" part indicates the base version, while "5761" is the revision number for this specific flight.

How do I calculate or derive 26120.5761? You don't calculate it. It is a version identifier assigned by Microsoft during the development cycle. The numeric sequence follows a standard pattern: the major version number remains consistent (26120) across the 24H2 lifecycle, while the revision number (5761) increments with each new update to reflect the latest changes.

Can 26120.5761 be ignored if an error occurs? No. If you encounter installation failures or stability issues, you should not ignore the build number. Because it is a preview update, you must address the errors via the troubleshooting steps above or revert to a stable build. Ignoring it can lead to corrupted update states that are harder to fix later.

Conclusion

Windows 11 Build 26120.5761 is a feature-dense release that pushes the boundaries of cross-device integration, particularly with the Android resumption feature. However, it comes with a trade-off: stability. The Xbox controller bugcheck and Windows Hello glitches are not just annoyances; they can disrupt daily workflows. For enthusiasts and testers, the value proposition is clear—early access to the future of Windows. But for anyone using this OS in a critical production environment, I recommend exercising caution. Monitor your logs, keep a rollback plan ready, and wait for the next stable release if you cannot tolerate the risk.

If you’re struggling with a specific issue in 26120.5761 that isn't covered here, drop a comment below. I read every response and can often point you to the right diagnostic log. And if you want to stay ahead of the curve, subscribe for updates as the next stable release approaches.

Back