KB5067106 Fixes 0x800f0983 and 0x8000FFFF in Windows 11 Insider

Microsoft’s latest Insider checkpoint tightens a set of small but meaningful UX loose ends: the preview package reported as KB5067106 brings Build 26220.6972 to the Dev channel (25H2) and Build 26120.6972 to Beta (24H2), extending dark-mode coverage inside File Explorer, adding a supported toggle to disable the controversial Drag Tray, and folding mobile‑device management into the Settings app — all delivered as a staged, server‑gated rollout for Insiders.

Background​

Windows 11’s ongoing development in late‑stage preview builds has focused less on single blockbuster features and more on incremental polish, discoverability, and ergonomics. Microsoft continues to ship enablement‑style cumulative updates into the 26220/26120 flight families and then selectively expose experiences with Controlled Feature Rollout (CFR), meaning feature visibility varies by device, channel, and server flags.
Those preview packages are useful labs: they let Microsoft validate small UX changes (dark‑theme completeness, share flows, Settings agents) and reliability fixes (File Explorer extraction errors, display rendering regressions), while also surfacing regressions that still need attention. The current KB‑labeled package reported by community trackers is lightweight in scope but notable for bridging long‑standing dark‑mode gaps and adding a supported way to opt out of a drag‑and‑share UI many users found intrusive.

---

What’s in this update (practical summary)​

File Explorer: Folder Options and dialogs respect Dark mode​

One of the clearest user-facing wins is improved dark‑theme coverage in File Explorer. Common file‑operation surfaces — Folder Options, copy/move progress dialogs, delete confirmation and replace/skip prompts — now render in Dark mode instead of switching to bright white dialogs. That reduces the visual “flash” that undercut the dark theme experience during frequent file operations.
Why it matters: this is perceptual quality work. Removing jarring luminance shifts improves ergonomics on OLED and high‑contrast displays and makes the UI feel finished rather than piecemeal.

Drag Tray: a supported toggle under Settings​

The top‑of‑screen Drag Tray — a small floating share target that appears when you drag files — now has a built‑in on/off control at Settings > System > Nearby sharing. That gives users a supported way to disable the tray without registry hacks or third‑party tools.
Key notes:

• The Drag Tray continues to evolve (multi‑file support, smarter target ranking) in the preview flights, but the important change here is control: Microsoft recognizes the UI’s polarizing nature and offers a toggle.
• If you don’t see the toggle immediately, the feature may be behind a server‑side flag and not yet visible on your device. Community workarounds exist (e.g., ViVeTool), but those remain unsupported and risky on production machines.

Settings: Mobile Devices page and account benefit shortcuts​

A new Mobile Devices page is now present in Settings (under Bluetooth & Devices), bringing phone pairing, on‑demand file access, and per‑device actions (for example, using a phone as a connected camera) into the main Settings flow. This reduces context switching compared with the older separate “manage mobile devices” dialog.
Microsoft also added a “View my benefits” quick link to the Start menu account flyout, and updated Game Pass wording and tile visuals to reflect recent branding/benefits clarifications. These are small navigational and marketing touches designed to make services and entitlements easier to find.

---

Fixes, reliability improvements, and known issues​

Notable fixes included in the package​

• File Explorer: a reliability fix for a catastrophic extraction error that could occur when extracting very large archives (~1.5 GB+ reported in community testing).
• Display/graphics: a patch that addressed a red‑tint regression impacting some videos and games.
• Windows Update: corrected update installation failures producing certain error codes that blocked installs in prior flights.

These practical fixes are likely to deliver visible improvements for users who experienced the regressions; they demonstrate the preview channel’s role in quickly iterating on reliability issues before wider rollout.

Known issues you should watch for​

• Regressions affecting Click to Do (Copilot) text actions: some text actions using on‑device models may not work correctly on this build, and Microsoft has acknowledged a fix is in progress. Insiders who rely on those features should be cautious.
• Channel/hardware gating causes feature visibility mismatch: two devices on the same build may see different behavior because CFR and hardware entitlements (Copilot+ machines) gate some features.
• Occasional regressions affecting Start menu clicks, Xbox controller Bluetooth stability, and taskbar behaviors have been reported across recent flights and are noted in the preview’s known‑issues lists. Treat these builds as preview quality, not production releases.

---

Rollout mechanics and verification caveats​

Controlled Feature Rollout (CFR) and staged exposure​

Microsoft’s model here is binary shipping plus server‑side flags. The update binary may include a variety of features, but Microsoft flips features on gradually to limit blast radius and monitor telemetry. The practical effect: installing the cumulative package does not guarantee immediate access to all listed features. To increase odds of seeing staged features, Insiders can enable “Get the latest updates as they are available” in Settings > Windows Update, but even that is not a guarantee.

KB/build mapping ambiguity​

Community trackers report this preview with KB numbers such as KB5067106 (and sometimes KB5067103 for closely related flights), but the KB-to-build mapping is not always consistent across regions and public indexes. If you need authoritative KB documentation for enterprise tracking, rely on the Windows Update details on your device or the official Flight Hub until Microsoft publishes a formal KB article in the Microsoft Support catalog. Treat community KB labels as helpful indicators, not definitive references.

---

What this means for power users and IT​

For enthusiasts and testers​

• The dark‑mode polish and the Drag Tray toggle are welcome quality‑of‑life wins; try them on a spare machine or VM to validate behavior.
• If you prefer a fixed experience, beware of CFR variability — two Insiders on the same build can see different UIs. Document what you see and file Feedback Hub reports to help Microsoft converge.

For content creators and multimedia users​

• The Drag Tray can be disruptive to precision workflows (video editing, layered Explorer workflows). Use the new Settings toggle to disable it if it interferes with your flow. If the toggle is not yet visible, avoid registry/ViVeTool workarounds on primary workstations.

For IT administrators and enterprises​

• Do not deploy Beta/Dev preview builds broadly to production fleets. Use targeted pilot rings and validate imaging and OOBE flows: Microsoft is tightening setup behaviors and reducing local‑account bypasses, which can affect onboarding and imaging scripts.
• Maintain rollback and recovery plans: Insiders have the standard Go Back option for 10 days, but beyond that you’ll need recovery images or reimage procedures. Validate the extraction fix against your archive workloads before relying on it for mass deployments.

---

Practical guidance: how to test safely (step‑by‑step)​

1. Prepare a non‑production device or VM that mirrors your common hardware/software baseline.
2. Enroll the test device in the Windows Insider Program (Settings > Windows Update > Windows Insider Program) and choose the Beta or Dev channel depending on the build family you want to test.
3. If you want the highest chance of seeing staged features, toggle On: Settings > Windows Update > Get the latest updates as they are available. Note the tradeoff: you’ll see more experimental behavior.
4. Check for updates and install the preview cumulative package reported for your channel (community trackers reference KB5067106 for the 26220/26120 family). Verify your device’s Windows Update details for the precise build number.
5. Validate the features that matter to you:
   • Dark mode: open File Explorer, run a copy/move operation, open Folder Options, and confirm the dialogs respect Dark mode.
   • Drag Tray: go to Settings > System > Nearby sharing and look for the Drag Tray toggle; test drag behavior with common apps.
   • Mobile devices: pair a phone and verify the Mobile Devices page lists the device and exposes camera/file access controls.
6. Test workloads that historically failed (large archive extraction, video playback) to confirm fixes and note any regressions.
7. If you encounter a blocking issue, use Settings > System > Recovery → Go back to return to the previous build within the rollback window, or recover from a system image if necessary.

---

Strengths and risks — critical analysis​

Notable strengths​

• Focused polish: extending dark mode into frequently used dialogs demonstrates attention to small details that improve perceived quality and reduce eye strain. This is the kind of iteration that benefits end users every day.
• User control: adding a supported toggle for the Drag Tray recognizes divergent workflows and reduces the need for hacky workarounds. That’s a clear win for user autonomy.
• Practical reliability fixes: addressing extraction crashes and graphics tint regressions solves tangible pain points many Insiders experienced.

Potential risks and tradeoffs​

• Inconsistent experience: CFR plus hardware/regional gating can produce an inconsistent user base where troubleshooting is harder and documentable expectations diverge across teams. This complicates support and testing.
• Regressions still present: preview flights continue to surface regressions that can affect core productivity flows; admins must treat these builds as experimental.
• Enterprise impact from OOBE and account posture: changes to setup flows and the push to Microsoft accounts during OOBE require IT to revalidate imaging, provisioning, and kiosk scenarios. Don’t assume existing deployment scripts will remain compatible.

---

Recommendations (concise)​

• Test on isolated hardware or VMs before wider evaluation; don’t install preview flights on mission‑critical machines.
• If the Drag Tray interrupts workflows, use Settings > System > Nearby sharing to turn it off once the toggle appears; avoid unsupported registry/ViVeTool changes on production systems.
• Validate the extraction fix and display patches against representative workloads (large archives, video playback) and check GPU driver updates from OEMs to ensure compatibility.
• For enterprise deployments, delay adoption until the features are broadly rolled out and the formal Microsoft KB and update catalog entries are published. Use pilot rings and preserve rollback/recovery tooling.

---

Conclusion​

KB5067106’s preview packages (Build 26220.6972 / 26120.6972) are emblematic of Microsoft’s current development posture: accumulate a set of small, high-signal UX improvements and reliability patches in an enablement-style cumulative, then expose them progressively via server gating. That approach yields a steady stream of usability wins — consistent Dark mode coverage in File Explorer, a first‑class toggle for the Drag Tray, and a tidy Mobile Devices page inside Settings — while preserving Microsoft’s ability to iterate quickly and revert problem features before broad release. Insiders and IT teams will benefit most by treating these flights as testable previews: validate on disposable hardware, watch for the CFR variability, and keep rollback procedures ready. The net of these changes is modest but practical — a worthwhile step toward a more consistent and controllable Windows 11 experience for users who care about polish and predictability.

---

Source: Windows Report KB5067106 Update Brings Consistent Dark Mode to Windows 11's File Explorer

Microsoft has pushed a matched pair of Insider preview updates — KB5067106 appearing as Build 26220.6972 in the Dev Channel (25H2) and Build 26120.6972 in the Beta Channel (24H2) — that add a new Mobile Devices page to Settings, continue dark‑mode polishing in File Explorer, and introduce a toggle to disable the controversial Drag Tray, along with a small Start menu shortcut to view Microsoft account benefits.

Background / Overview​

Microsoft delivered KB5067106 to Windows Insiders as a checkpoint cumulative that maps to two servicing branches: Dev (25H2) and Beta (24H2). The same binary payload is exposed on both branches but appears under different build numbers (26220.xxxx for Dev, 26120.xxxx for Beta). Microsoft uses this approach to ship incremental UI improvements and fixes while controlling who sees new experiences via server-side gating (Controlled Feature Rollout). That means feature availability can vary between machines even when the reported build number is identical.
This update set is small in scope but noteworthy: it focuses on usability and continuity features rather than sweeping platform changes. The most visible items are:

• A dedicated Mobile Devices settings page (Settings > Bluetooth & devices > Mobile devices) to add, view, and manage phones connected to a PC.
• Continued dark mode improvements in File Explorer (notably the Folder Options dialog and related copy/move dialogs).
• A Drag Tray on/off toggle under Settings > System > Nearby sharing.
• A Start menu account flyout shortcut labeled “View my benefits” that opens the Microsoft account benefits page.

Community posts and forum threads confirm the changes and provide hands‑on context, reinforcing Microsoft’s published notes.

---

What’s new in KB5067106 (deep dive)​

Mobile Devices in Settings: what changed and why it matters​

Microsoft has added a Mobile Devices page beneath Settings > Bluetooth & devices. That page consolidates phone‑related controls into a single, discoverable surface where you can:

• See a list of paired mobile devices.
• Add a new mobile device to the PC.
• Manage device‑specific features such as “Use as a connected camera” and Show mobile device in File Explorer to access phone storage directly.

Why it matters

• Reduced friction: moving phone management into the main Settings flow removes the need for separate “Manage mobile devices” dialogs and reduces context switching.
• First‑class phone workflows: creators and hybrid workers who use their phone as a webcam or need on‑demand access to mobile files will find the process less fragmented.
• Easier troubleshooting: a unified settings entry point makes it simpler for users and admins to verify pairing and expected capabilities.

Rollout caveat

• The Mobile Devices page is being rolled out gradually — enabling the Insider toggle (Get the latest updates as they are available) improves the chance you’ll see it early, but server gating and hardware entitlements still control visibility.

Verification and limitations

• Microsoft’s blog confirms the settings page and the user‑facing surface. Community reports corroborate the File Explorer integration and camera use scenarios. Some third‑party guides and forum archives claim additional prerequisites (Phone Link versions, Bluetooth LE support, Android/iOS nuances), but those specific version numbers and device limitations are not fully enumerated in the official release notes; treat such specifics as helpful pointers, not definitive requirements, until Microsoft publishes formal KB or support articles. This is a caution: some claims circulating in community posts could not be independently verified against a single authoritative Microsoft support article at the time of writing.

File Explorer dark‑mode polish​

This build continues Microsoft’s long‑running effort to remove jarring light UI flashes when users run Windows in Dark mode. The update brings consistent dark rendering to the Folder Options dialog and refines copy/move progress and replace/skip prompts so they better respect the system theme. Those changes reduce luminance shifts during common file operations, improving ergonomics and perceived polish.
Practical impact:

• Users who keep Dark mode enabled will see fewer white dialogs during file operations; however some legacy or deeply embedded dialog surfaces may still be light and Microsoft will expand coverage with future flights.

Drag Tray toggle: finally controllable​

The Drag Tray — a top‑of‑screen sharing tray that appears when you drag files and offers quick share targets — has been polarizing since its early Insider appearances. KB5067106 adds an official on/off switch in Settings > System > Nearby sharing to let users disable the Drag Tray without registry tweaks or third‑party tools.
Why this is important

• Power users and creators: those doing precise drag‑and‑drop workflows (video editors, multi‑window explorers) often found the tray intrusive; a supported toggle reduces friction.
• Stability and policy: enterprises will prefer an official toggle over undocumented hacks.

Caveats and community note

• The toggle may be gated by controlled rollout; if it’s not visible yet, the feature may be server‑side blocked on some devices. Community workarounds and ViVeTool flags exist, but they are unsupported and can cause other unexpected behaviors — use them only on test devices.

Start menu account flyout: “View my benefits”​

The account flyout accessed from the profile icon in the Start menu now includes a shortcut labeled “View my benefits” that opens the Microsoft account benefits page. It’s a small UX change with outsized discoverability value: it lowers the barrier for users to discover entitlements from Microsoft 365, Xbox, and other subscription bundles tied to their Microsoft account.
Implications

• Improves visibility of bundled services and may increase clicks to the account portal.
• It’s a convenience feature; enterprises that restrict web access should account for any support tickets it might generate if the browser fails to open the destination.

---

Fixes and known issues in this build​

Microsoft lists a set of targeted fixes in these preview builds that aim to make day‑to‑day Windows use more reliable. Highlights include:

• Fixed a “Catastrophic Error (0x8000FFFF)” when extracting large archives (~1.5 GB+).
• Resolved an issue that could cause an unexpected red tint in videos and some games.
• Fixed stuck/partially updated onscreen content in some apps when other full‑screen apps updated in the background.
• Improved monitor mode queries performance to reduce momentary stutter on very high‑resolution displays.
• Fixed an update installation failure that could report error 0x800f0983.

Known issues called out by Microsoft include a regression affecting text actions that use the Phi Silica model in Click to Do and Recall — Microsoft is working on a fix — and a Start menu click-to-open issue for a subset of Insiders. Admins and testers should read the known issues list before upgrading.
Community‑reported fixes and reproductions appear in forums and thread archives, and community testers have validated many of the fixes and features on both Dev and Beta channel devices.

---

Risks, privacy, and enterprise considerations​

Controlled feature rollout: manage expectations​

Microsoft’s controlled rollout strategy reduces risk at scale but creates variability. A business that expects identical behavior across identically configured machines may be surprised if some devices receive the Mobile Devices UI while others do not. For enterprise deployments:

• Treat Dev/Beta channel builds as preview only and restrict them to lab or test systems.
• Wait for official KB articles and Update Catalog entries before approving enterprise deployments.
• Use imaging and update ring strategies to pin stable channels for production devices.

Privacy and telemetry considerations​

• The Start menu “View my benefits” shortcut opens an online account page; browser state, extensions, and corporate proxies affect what the user experiences and what telemetry is logged. Web‑hosted tools generate server logs on the host site and may create additional network telemetry visible to ISPs and enterprise monitors. Users in privacy‑sensitive contexts should be aware that clicking the shortcut launches web traffic beyond the local device. Community writing on this topic underscores that browser mediation and backend choices matter; the one‑click shortcut is a convenience, not a private, local diagnostic.

Security and management​

• Enterprises should validate whether new Settings entries or toggles affect Group Policy surfaces or MDM profiles. Historically, Microsoft adds administrative controls only after community feedback, so if your organization needs to enforce settings (for example, disabling Drag Tray), monitor the policy catalog and Windows CSP updates for new controls.

Accessibility and localization​

• New UI surfaces previewed in Insider builds can lag in accessibility support and localization. Narrator announcements, keyboard focus, and ARIA‑like cues should be validated by assistive technology teams before deploying to users with accessibility needs. Microsoft’s Insider notes warn that some accessibility features may not yet be fully compatible.

---

How to get the preview build (Insider guidance)​

• Open Settings > Windows Update > Windows Insider Program.
• Choose your channel: Dev for the 25H2 code path (Build 26220.6972) or Beta for the 24H2 preview (Build 26120.6972).
• To increase your chance of seeing toggle‑gated experiences (Mobile Devices page, Drag Tray controls), turn on “Get the latest updates as they are available” in the Insider Program page.
• Check for updates and install the preview cumulative (reported as KB5067106). Reboot when prompted.

Practical tips:

• Install on a spare device or VM if you want to test new settings and workflows.
• Back up or image before installing preview builds that may change shell behaviors or drivers.
• If you install on a device used for work, keep a recovery plan (image/restore point, or the ability to roll back to a stable channel).

---

Troubleshooting and power‑user notes​

• Drag Tray: If the new Settings toggle isn’t visible but you want to disable the feature, community workarounds (registry edits, ViVeTool) have been used — but they are unsupported and can break other behaviors. Prefer the official toggle when it becomes available for your device.
• If File Explorer exhibits copy dialog flicker in dark mode, Microsoft’s notes indicate the issue may be intermittent; try toggling dark mode off/on and update graphics drivers if rendering artifacts persist.
• For video/game red tint or stuck-screen content, apply this preview and verify GPU driver compatibility with the latest vendor releases; the build includes targeted fixes but drivers also matter.
• If the Start menu fails to open by mouse click, use WIN + X or the Windows key as a temporary workaround until a fix ships. Microsoft is tracking this issue.

---

How this fits Microsoft’s broader vision​

The additions in KB5067106 reflect two consistent strategies Microsoft has pursued:

• Cross‑device continuity: consolidating phone workflows into Settings and exposing deeper File Explorer integration reinforces Windows as the central productivity hub for multi‑device users.
• Polish over flash: incremental dark mode fixes and small UX toggles (like Drag Tray on/off) show a shift from feature bloat toward cleaning up high‑frequency experiences.

Those moves align with Microsoft’s public roadmap for Windows 11: measured, user‑centric refinements combined with controlled experiments surfaced through the Windows Insider Program. Observers and community members mirrored this interpretation in forum reports and analysis.

---

Strengths and notable improvements​

• Usability gains: centralizing mobile device management in Settings is a clear win for discoverability and reduces the number of UI flows users must navigate to manage phone‑PC features.
• Dark mode completeness: reducing bright flashes in File Explorer improves the day‑to‑day experience for users who prefer Dark mode and helps eliminate jarring visual context shifts.
• Respecting user choice: adding an official Drag Tray toggle acknowledges user feedback and gives power users a supported way to opt out.
• Practical fixes: the extraction error fix (0x8000FFFF), graphics and monitor query improvements, and update reliability fixes have meaningful operational value for users and IT teams.

---

Potential risks and unanswered questions​

• Staged availability complicates testing: controlled rollouts mean QA must test both with and without server‑gated features — adding overhead for ISVs and IT validation.
• Incomplete documentation at release: at the time of reporting, the full support KB article for KB5067106 in the Microsoft Update Catalog was not yet available; enterprises that require a formal KB with file lists and remediation steps should delay production deployment until Microsoft publishes the official support article. This is a cautionary note — some community summaries include specific prerequisites that we could not confirm against a single Microsoft support page at the time of this write‑up.
• Privacy and telemetry surface area: convenience links that open web pages or broker account benefits can increase telemetry and create support traps in locked‑down corporate environments; admins should prepare documentation for help desks.
• Accessibility gaps: new features can lag in full assistive technology support; organizations with accessibility requirements should validate functionality with the appropriate testing tools and users.

---

Bottom line and recommended next steps​

KB5067106 (Build 26220.6972 / 26120.6972) is a practical, incremental preview update aimed at improving phone‑PC continuity, dark‑mode consistency, and user choice around the Drag Tray experience. For Windows enthusiasts and testers it is worth installing on a spare machine or VM to validate workflows such as using a phone as a connected camera or browsing mobile storage from File Explorer. For enterprises and production users the sensible course is to:

• Wait for the official Microsoft KB/Update Catalog entry and review the support article.
• Test in a controlled lab with representative devices and policies — verify Phone Link scenarios, Nearby sharing, and the availability of the Drag Tray toggle.
• Update GPU and peripheral drivers to the latest vendor releases before deploying, as some fixes interact with graphics stacks.
• If you’re on the Insider program for testing, enable the “Get the latest updates as they are available” toggle to increase the likelihood of seeing toggle‑gated experiences sooner.

These incremental improvements are consistent with Microsoft’s ongoing effort to make Windows 11 feel more cohesive across devices, while still acknowledging that preview builds carry risk and variability. The Mobile Devices page and Drag Tray toggle are welcome usability updates, but organizations should validate them in context and await formal Microsoft KB documentation before rolling them into broad deployments.

---

Microsoft’s official Insider announcement lists the changes and known issues for Build 26220.6972 / 26120.6972; community reports and forum threads provide hands‑on validation and practical tips for Insiders who want to experiment with the new Mobile Devices page, dark‑mode fixes, and Drag Tray controls.

---

Source: Windows Report Windows 11 KB5067106 Brings Mobile Devices Setting in Version 25H2 & 24H2