Microsoft has shipped Windows 11 Insider Preview Build 28020.1362 (KB5073095) to the Canary Channel with a concentrated set of stability and usability fixes that target long-standing pain points in File Explorer, Settings, the taskbar, display/graphics code paths, and the sign‑in experience. The release is explicitly quality‑focused: it doesn’t bring sweeping new consumer features so much as a broad set of pragmatic bug fixes and performance improvements designed to reduce daily friction for testers and, eventually, mainstream users.
Canary Channel builds are Microsoft’s earliest public experiments with platform changes and refinements. They’re intentionally volatile: features can be added, removed, or altered rapidly based on early feedback. Build 28020.1362 is delivered as KB5073095 and is listed by Microsoft as an optional non‑security preview to Canary testers. That means the fixes here are targeted at edge cases and reliability regressions discovered across Insider telemetry and community reports; they are not the same as a monthly cumulative security update destined for stable Windows Update rings. This release’s chief goal is pragmatic: reduce frustrating crashes and visual regressions in the shell (Explorer, taskbar, Settings) while fixing a range of display and login nuisances that have produced high‑visibility bug reports from Insiders and IT admins. The cumulative touches on many subsystems, from thumbnail rendering to archive extraction, and includes fixes intended to make the Windows shell more predictable for heavy desktop users and for mixed hardware scenarios (for example, all‑in‑one PCs and high‑resolution monitors).
Source: Windows Report Windows 11 KB5073095 Fixes File Explorer, Taskbar, and Display Bugs
Background / Overview
Canary Channel builds are Microsoft’s earliest public experiments with platform changes and refinements. They’re intentionally volatile: features can be added, removed, or altered rapidly based on early feedback. Build 28020.1362 is delivered as KB5073095 and is listed by Microsoft as an optional non‑security preview to Canary testers. That means the fixes here are targeted at edge cases and reliability regressions discovered across Insider telemetry and community reports; they are not the same as a monthly cumulative security update destined for stable Windows Update rings. This release’s chief goal is pragmatic: reduce frustrating crashes and visual regressions in the shell (Explorer, taskbar, Settings) while fixing a range of display and login nuisances that have produced high‑visibility bug reports from Insiders and IT admins. The cumulative touches on many subsystems, from thumbnail rendering to archive extraction, and includes fixes intended to make the Windows shell more predictable for heavy desktop users and for mixed hardware scenarios (for example, all‑in‑one PCs and high‑resolution monitors). What’s fixed at a glance
- File Explorer: video thumbnail rendering, stray white toolbar, generic icons in context menu, custom folder views resetting, context‑menu‑related freezes, catastrophic error during very large archive extraction, Home becoming unresponsive.
- Settings: Network & Internet navigation hangs, search bar overlapping window buttons, truncated processor names in About.
- Taskbar: auto‑hide getting toggled off unexpectedly, Voice Access not addressing taskbar entries, icons shrinking despite available space, previews dismissing instead of bringing windows forward.
- Display & graphics: improved monitor mode query performance on high‑res displays, brightness slider fixes for AIO PCs, false “unsupported graphics card” warnings in some games, partial screen update issues, multiline text box rendering problems.
- Login & lock screen: faster taskbar loading after wake, improved first‑time sign‑in speed for new accounts, and a fix for a slideshow lock screen memory leak.
Deep dive: File Explorer fixes that matter
Thumbnails and EXIF metadata
A persistent annoyance for media users has been missing or inconsistent video thumbnails. Build 28020.1362 addresses an issue where certain EXIF metadata in video files caused thumbnails to fail to appear. That’s a targeted, practical fix for creators and power users who rely on thumbnails to navigate media folders quickly. Microsoft’s notes explicitly call out the EXIF case and community reports show this exact behavior was a frequent complaint.Old white toolbar / dark‑mode regressions
An “old white toolbar” appearing in File Explorer — and the related dark‑mode white‑flash regression seen in some earlier preview rollouts — have vexed Insiders. The build removes that stray white toolbar and, according to Microsoft, reduces visual regressions introduced by previous previews. Third‑party coverage of the white‑flash issue confirms that Microsoft has been tracking and addressing it across December previews; however, testers should be aware that dark‑mode visual regressions have been a moving target and may recur when other UI changes land.Context menu, app icons, and custom folder view persistence
Small UI glitches add up. This build fixes cases where the app icon next to “Open” in the context menu displayed a generic icon rather than the default app icon, and it ensures custom folder views (sorting, icon size, grouping) persist when folders are opened from external apps (for example, a browser’s Downloads link). The update also fixes an Explorer freeze that could happen after invoking the context menu — a reliability improvement that reduces unexpected explorer.exe hangs. Those are low‑level UX details but they directly reduce friction for daily users.Large archive extraction — catastrophic error 0x8000FFFF
One notable bug fixed here is the archive extraction failure for very large folders (Microsoft calls out ~1.5 GB+ examples) that returned a catastrophic error (0x8000FFFF). That error could disrupt workflows that rely on unzipping large archives and is the sort of regression that produces high‑severity support tickets. Fixing it reduces a clear operational risk, especially for users who exchange large compressed datasets or installers.Settings and taskbar: reliability where users notice it
The Settings app and the taskbar are the most frequently used system surfaces after the desktop — and small failures there are disproportionately irritating.Settings app reliability
Build 28020.1362 fixes a hang that occurred when navigating to Network & Internet pages in Settings, addresses a layout issue where the search bar overlapped the window minimize/maximize/close buttons, and ensures the CPU/processor name fully displays in System > About. These fixes are mainly polish, but they matter for users who need accurate system information or administer network settings regularly.Taskbar behavior and accessibility
Multiple taskbar issues were addressed:- Auto‑hide no longer resets itself randomly.
- Voice Access (Microsoft’s speech‑control accessibility tool) works correctly with taskbar items again.
- Taskbar icons no longer shrink when there is available space.
- Taskbar hover previews now consistently bring windows to the foreground instead of dismissing unexpectedly.
Display, graphics, and input: smoothing stutters and false warnings
Modern displays, high‑refresh/4K monitors, and gaming workloads expose subtle timing and enumeration issues. This build addresses a set of those problems:- Reduces micro‑stutter when apps query monitor supported modes on very high‑resolution displays by improving internal timing paths.
- Fixes brightness slider regressions on certain all‑in‑one (AIO) devices where the slider would revert unexpectedly.
- Removes false “Unsupported graphics card detected” messages that some games were showing despite compatible GPUs.
- Prevents background apps from causing partial screen updates and ensures multiline text boxes render text correctly.
Login, lock screen, and Narrator: less waiting, fewer leaks
Build 28020.1362 also tightens the first moments of user interaction:- Faster taskbar loading after waking from sleep reduces the jarring “desktop appears but taskbar lags” scenario.
- First‑time sign‑in for newly created accounts completes quicker, which helps fast provisioning and kiosk setups.
- Fixed a memory leak tied to slideshow lock screens; leaks over long up‑time can degrade system responsiveness.
- Narrator is less likely to pause abruptly during continuous reading in Word documents.
What’s still risky: known issues and community reports
No Canary build is risk‑free. Insiders and third‑party outlets have tracked a set of regressions that have either appeared alongside recent preview updates or that Microsoft has documented as known issues.- Dark‑mode white flash: while this build attempts to remove an old white toolbar and mitigate flashes, previous preview updates introduced a white‑flash regression when opening File Explorer in dark mode. Microsoft acknowledged that regression and has marked fixes/mitigations in recent updates; yet, community testing shows the behavior can reoccur under certain conditions. Test dark‑mode File Explorer workflows before broad deployment.
- Shell provisioning failures: Microsoft published guidance describing scenarios where, after provisioning with a 24H2 update, XAML components or shell packages might not register in time, producing symptoms such as explorer.exe crashes or no taskbar. Administrators upgrading device fleets should be aware of provisioning timing issues and validated rollouts in staged rings.
- Canary volatility: by definition Canary builds can surface regressions that didn’t exist before. Multiple independent community threads show that while some fixes land cleanly, other regressions (including taskbar or Start menu failures) have emerged in adjacent releases. For production devices, the Canary Channel is not appropriate; pilot testing is mandatory.
Recommendations for IT admins and power users
This build is a targeted quality release for testers. For organizations or power users considering an early evaluation, the following guidance balances risk with the practical desire to validate fixes.- Create a pilot ring (3–10 devices) that mirrors production hardware diversity: laptops, desktops, all‑in‑ones, and representative GPU models. Validate File Explorer heavy workflows (media browsing, large archive extraction, context menu flows) and taskbar interactions.
- Run a checklist of high‑risk tests:
- File Explorer: open Home, Gallery, create new tabs, toggle Details pane, open folders from other apps.
- Archives: extract large archives (>1.5 GB) to confirm catastrophic error fix.
- Display: exercise high‑resolution games, run monitor mode enumeration scenarios, and test brightness slider on AIOs.
- Sign‑in: first‑time account creation and resume from sleep flows.
- Accessibility: verify Voice Access and Narrator reading continuity.
- Validate drivers and firmware: update GPU drivers and display firmware first. Graphical and monitor enumeration fixes often interact with vendor drivers; mismatched drivers increase the chance of false “unsupported GPU” messages.
- Keep rollback and imaging playbooks ready: Canary to lower channel changes typically require clean installs to move back; plan recovery images and retention of critical user data.
- Pilot for at least 72 hours per device under normal user workloads: leaks and intermittent issues often only appear after sustained use. Monitor for explorer.exe restarts, memory growth, and taskbar visibility issues.
- File feedback with concrete repros: use Feedback Hub with diagnostic traces so Microsoft can correlate telemetry. Include steps to reproduce, hardware details, and screenshots or short recordings.
Why these fixes matter (and where they fit strategically)
Microsoft has shifted more engineering focus to incremental quality-of-life improvements in Windows 11, especially as the OS matures. The practical benefits of the fixes in KB5073095 are:- Reduced friction for daily productivity: File Explorer stability, reliable context menus, and persistent folder views all reduce wasted micro‑interactions and time spent working around shell oddities.
- Lower support costs: Fixes for catastrophic extraction errors, sign‑in delays, and taskbar auto‑hide bugs cut the classes of issues that generate routine helpdesk tickets.
- Better gaming and creative workflows: smoother monitor enumeration and corrected false GPU warnings reduce false negatives in game compatibility and avoid unnecessary troubleshooting.
- Accessibility improvements: Voice Access and Narrator fixes help keep Windows usable for people who depend on assistive technologies.
A realistic assessment: strengths and potential downsides
Strengths
- Focused reliability work: the patch addresses known, high‑impact UX regressions rather than experimental features. That’s a welcome emphasis on stability.
- Breadth across subsystems: the build isn’t narrowly targeted; it addresses shell, display, input, and sign‑in paths that together shape daily user experience.
- Measurable fixes: items like the archive extraction error and context‑menu freezes are concrete, testable repairs that will reduce support noise.
Potential risks and limitations
- Canary volatility: by design, early Canary builds can introduce regressions even as they fix others. This makes them unsuitable for production deployment without staged testing.
- Dark‑mode regressions and visual flicker: prior previews introduced white flashes in File Explorer when dark mode is active. Microsoft is fixing those, but the history shows visual regressions can reappear as other shell changes roll out. Exercise caution if dark‑mode consistency is critical for kiosk or presentation devices.
- Hardware/driver interactions: several fixes relate to display enumeration and GPU detection — areas that heavily depend on up‑to‑date OEM drivers. Older drivers may mask or reintroduce symptoms. Validate vendor driver compatibility before wide rollout.
Practical rollout checklist (quick reference)
- Backup critical data and ensure system images are up to date.
- Apply the build to a small pilot ring representing your fleet diversity.
- Validate the specific fixes you care about (see the 6‑step checklist above).
- Monitor telemetry for explorer.exe restarts, taskbar visibility, GPU warnings, and overall memory consumption.
- If you encounter new regressions, collect diagnostic traces and file Feedback Hub reports with repro steps; pause spread until the issue is understood.
Conclusion
KB5073095 (Build 28020.1362) is a pragmatic Canary release focused on shoring up the daily reliability and usability of Windows 11. It fixes a broad range of high‑visibility problems in File Explorer, the Settings app, the taskbar, display and graphics pathways, and the login experience — many of the very issues that generate the most complaints in community forums and helpdesks. The build’s greatest value is practical: it removes friction, reduces support overhead, and makes the shell more predictable for insiders and early adopters. That said, Canary remains Canary: expect volatility, perform methodical pilot testing, and validate vendor drivers before trusting fixes in production. For the Windows ecosystem, these fixes are important incremental steps toward a more stable, less surprising desktop — the kind of invisible work that improves daily life for millions of users when it finally reaches mainstream channels.Source: Windows Report Windows 11 KB5073095 Fixes File Explorer, Taskbar, and Display Bugs
