Microsoft has quietly shipped a small but important Insider update — Windows 11 KB5065793 (Build 26220.6760 / 26120.6760) — that stitches up a raft of annoying user-facing bugs and developer headaches, from taskbar and system tray oddities to SMBv1 file-sharing problems and PIX GPU‑capture playback errors. The patch is rolling out gradually to Windows Insiders in the Dev and Beta channels, and while many fixes are straightforward quality-of-life improvements, a few changes carry security and compatibility implications that administrators and power users should weigh carefully.
Background / Overview
Windows Insider flights for the 25H2 enablement branch have used frequent incremental cumulative updates as Microsoft polishes features and kills regressions ahead of broader rollout. KB5065793 is one of those checkpoint cumulative updates: in the Dev Channel it arrives as Build 26220.6760, and in the Beta Channel as Build 26120.6760 for select 24H2 devices. The update’s public notes — surfaced through Microsoft’s Insider blog posts, preview release summaries and corroborating technology outlets — list a diverse set of fixes targeting the taskbar, Settings, File Explorer, search UI, networking, media playback and developer tooling.Two contextual points matter for readers:
- Many fixes are being gradually rolled out using Microsoft’s Controlled Feature Rollout (CFR) mechanism; that means not every Insider will see every fix immediately. Expect staggered availability.
- Some fixes address problems introduced by earlier September security updates and CUs; Microsoft has been issuing targeted preview updates to unblock impacted scenarios (notably SMBv1 over NetBIOS).
What’s fixed: taskbar, system tray and UI polish
Taskbar and system tray stability
The update addresses several taskbar and system tray glitches that insiders reported after the 25H2/24H2 flights. Key problem areas include:- Battery icon sync problems between the system tray, quick settings and Settings > Power & battery.
- Taskbar preview animation changes: Microsoft temporarily removed some hover-preview animations for reliability; the update reinstates or stabilizes the experience where appropriate.
- Fixes for taskbar-related crashes and inconsistent behavior that could leave app icons unresponsive or system tray indicators out of sync.
Click to Do and accidental WIN + P triggers
Reports indicated Click to Do — the Copilot-driven productivity surface — could be triggered unexpectedly by WIN + P on some devices. KB5065793 includes a fix that prevents Click to Do from launching incorrectly when projection hotkeys are used.Why it matters: accidental UI invocations break workflows and can cause user confusion. This is particularly important for users who rely on WIN + P for display projection in meeting and classroom settings.
Lock screen media controls and “Update and shutdown”
The update also corrects the behavior of lock-screen media controls so they appear reliably when media is playing, and resolves an issue where the “Update and shut down” action sometimes failed to apply updates as expected.Why it matters: reliable media controls improve remote/lock-screen workflows and the Update-and-shutdown fix prevents update-installation confusion that could otherwise lead to failed or delayed patching.
File Explorer, Settings, and Search fixes
Settings crashes and drive info
One recurring Insider report was that opening certain drive or storage pages in Settings could cause crashes. KB5065793 fixes Settings crashing when accessing drive information (for example, Storage > Manage disks & volumes or device drive details).Why it matters: Settings crashes block diagnostics and troubleshooting. Fixing these improves reliability for both casual users and IT troubleshooting.
File Explorer customization persistence
The update makes File Explorer customization (view, sort, folder options) more consistent across app instances — a longstanding annoyance where preferences didn’t always carry between Explorer windows or persisted incorrectly after restarts.Why it matters: consistent Explorer settings reduce friction for users who manage large file sets or depend on a stable workspace across restarts.
Search placeholder alignment and UI polish
Minor UI bugs such as search placeholder alignment and some visual spacing issues were corrected. These changes are small but contribute to a smoother user experience.Why it matters: accessibility and visual correctness matter — especially on new high-DPI displays and in localized languages where UI truncation and misalignment can be particularly disruptive.
Networking: SMBv1 over NetBIOS (NetBT) — what changed and why you should be cautious
What was broken
Earlier September security updates caused regressions that prevented some systems from connecting to legacy SMBv1 shares over NetBIOS over TCP/IP (NetBT). That breakage affected customers with older NAS appliances, legacy printers and industrial equipment that still rely on SMBv1.What KB5065793/related previews do
Microsoft has been addressing the SMBv1 connectivity regressions via multiple preview updates across Windows branches. KB5065793’s notes indicate it restores SMBv1 connectivity over NetBIOS in affected Insider builds, aligning with earlier fixes shipped for some branches (for example, a related preview addressed the issue for 23H2 devices).Why it matters: restoring SMBv1 over NetBT unblocks customers who must access legacy shares, but the SMBv1 protocol is inherently insecure and deprecated. Microsoft’s guidance remains to migrate away from SMBv1; fixing the regression is a compatibility stopgap, not an endorsement of SMBv1 as safe.
Security caveats and recommended actions:
- Do not re-enable SMBv1 across your network unless you absolutely must. SMBv1 has known vulnerabilities exploited in the wild.
- If you must connect to SMBv1 devices temporarily, isolate them on a separate VLAN, restrict firewall access, and tightly control which endpoints can access the legacy shares.
- Prioritize firmware/software updates from device vendors and plan a migration path to SMBv2/SMBv3 or alternative transfer methods.
Developer tooling: PIX GPU capture playback fixes
PIX capture playback reliability
Developers using PIX on Windows were seeing errors when playing back GPU captures in certain scenarios. KB5065793 includes fixes so PIX can more reliably play back GPU captures without failing on affected hardware/driver combinations.Why it matters: PIX is a critical diagnostics tool for Direct3D development and game performance analysis. Playback failures limit developers’ ability to reproduce and fix rendering bugs and performance regressions.
Notes for developers:
- Even with this fix, PIX playback can still be sensitive to GPU model and driver version differences; captures are most reliable when the playback environment closely matches the capture environment.
- If you still encounter issues, update GPU drivers, ensure PIX is the latest release, and follow PIX recommendations (disable DRM for captures, test with the D3D12 debug layer, etc.).
Media and HDCP playback fixes
HDCP-protected content playback
KB5065793 includes fixes for video playback problems affecting HDCP-protected streams in certain apps. Users had reported failure or glitches when playing DRM/HDCP content in apps that rely on protected path video playback.Why it matters: HDCP and DRM are critical for paid streaming services and protected media scenarios. Fixes restore expected playback on affected devices and spare users from customer-support headaches when paid content won’t play.
Operational notes:
- If you still see playback issues after the update, ensure you have the latest graphics drivers and check that the display chain supports HDCP end-to-end (monitor, cable, and GPU).
- Some DRM issues are device/firmware-specific; report failures through the Feedback Hub if playback still fails.
What’s been confirmed, what remains unclear
Verification and cross-reference summary:- Microsoft’s public Insider blog and official release posts document the overall Dev/Beta build rollouts and many of the broad fixes being tested across flights. Multiple Insider build posts around early-to-mid September show Microsoft actively addressing taskbar, Click to Do, and File Explorer issues in the Dev/Beta channels.
- Independent coverage and community reports corroborate the SMBv1 regression and the targeted preview fixes that Microsoft has been shipping to mitigate it.
- Developer documentation for PIX and Microsoft’s own PIX release notes and dev blog explain known PIX capture/playback limitations and note fixes rolled into subsequent PIX or OS updates.
- Some very specific items attributed to KB5065793 in third‑party summaries (for example, an explicit line like “temporary animation removal for previews” or granular itemization of every minor Settings alignment tweak) are not always listed in a single consolidated Microsoft KB support article at the time of publishing. Because the Insider channel uses staggered staged rollouts and incremental cumulative checkpoints, a complete itemization may only appear across multiple flights or internal release notes.
- If a claim cannot be found in Microsoft’s public Insider blog posts or Microsoft support pages, treat it as reported by Insiders and third‑party outlets, and verify on your own device (winver / Settings > Windows Update > Update history) before relying on it in a production environment.
Deployment guidance for Insiders, IT pros and regular users
How to check if you have KB5065793
- Open Start, type winver and press Enter.
- The About Windows dialog displays the OS Build and revision (e.g., Build 26220.6760 or 26120.6760).
- Alternatively, go to Settings > Windows Update > Update history and look for the KB entry.
How to get the update
- Insiders: With the Dev or Beta channel and the “get the latest updates as they become available” toggle enabled, KB5065793 will be offered automatically via Windows Update where Microsoft has staged the rollout.
- Non-Insiders: This is a preview channel update and will not necessarily be available on stable/public channels. Do not attempt to install Insider-only checkpoints on production systems.
If something goes wrong: quick rollback steps
- Settings > Windows Update > Update history > Uninstall updates. Find the KB and uninstall.
- If that option is unavailable, use System Restore (if enabled) or boot to Advanced Recovery to perform a rollback.
- For stubborn update failures, Microsoft Update Catalog offers standalone packages for some KBs — advanced users can download and install or remove via wusa.exe, but this is generally for experienced admins.
Reporting ongoing problems
- Use Feedback Hub (WIN + F) to submit reproducible steps, attach logs and indicate precise build numbers (very important for Insider triage).
- For enterprise environments, collect MSINFO32, Event Viewer entries, and crash dumps when escalating to Microsoft Support.
Risks, tradeoffs and security considerations
- Restoring SMBv1 connectivity: while convenient, this exposes a well-documented attack surface. Organizations must weigh the operational need against security risk and use network segmentation, firewall rules, or temporary exception policies rather than broad re-enablement.
- Insider builds are inherently less stable than production releases. Even small cumulative updates can introduce regressions on specific hardware or software stacks — particularly graphics drivers, virtualization features, or third‑party shell extensions.
- PIX capture/playback fixes depend on both OS-level changes and graphics driver compatibility. Developers should keep GPU drivers updated and be prepared for capture portability issues if driver versions differ between capture and playback machines.
Practical checklist — what to do next
- Home users:
- If you’re an Insider on Dev/Beta and seeing these problems, check Windows Update and install KB5065793 if available.
- If you depend on legacy SMBv1 devices, avoid broad re-enablement; instead, isolate and plan migration.
- IT admins:
- Audit environments for SMBv1 dependency and create a migration schedule; use temporary network-level controls if you must allow SMBv1 traffic.
- Test KB5065793 in a controlled pilot group before broad deployment — even preview fixes can surface new compatibility issues in enterprise environments.
- Developers:
- Update PIX to the latest version and verify capture/playback workflows after installing KB5065793. If problems persist, document driver versions and repro steps and file feedback via the PIX dev channels or Feedback Hub.
Conclusion
KB5065793 is a pragmatic quality-of-life update for Windows Insiders: it quashes a wide set of user-facing glitches, smooths out developer tools behavior, and addresses a high-profile SMBv1 connectivity regression that blocked some legacy workflows. For most Insiders the update will simply make daily use less buggy; for IT teams and developers the update reduces known friction points while also surfacing the ever-present tradeoff between compatibility and security — especially around SMBv1.Insiders and early adopters should install the update when available, verify the fixes that matter to them (notably SMB connectivity and PIX playback), and report any leftover issues through Feedback Hub. Administrators must treat SMBv1 fixes as temporary relief rather than a solution: plan migrations, apply network controls, and keep systems patched and drivers current. The Windows update pace remains rapid and iterative — expect more small cumulative updates as Microsoft continues to refine the 25H2/24H2 enablement experience.
Source: Windows Report Windows 11 KB5065793 Fixes Settings Crashes, SMBv1 Sharing, and Taskbar Issues
