Microsoft’s latest Canary-channel drop for Windows 11 — Build 28020.1673 — continues the steady stream of small, focused refinements that have defined the post‑24H2 era: a taskbar‑accessible network speed test, further expansion of dark‑mode coverage in File Explorer and legacy dialogs, camera pan/tilt controls in Settings, Emoji 16 additions, and a handful of enterprise‑oriented updates such as RSAT for Arm64 and tweaks to Quick Machine Recovery. These aren’t headline redesigns, but together they tighten the daily experience and reduce the number of external tools users and administrators rely on for routine tasks.
Background
Microsoft’s development cadence for Windows 11 has matured into a rhythm of incremental improvements deployed through the Windows Insider channels — Canary for early trials, Dev and Beta for stabilization, and Release Preview for near‑retail parity. Build 28020.1673 lands in the Canary Channel as a focused quality‑of‑life release. Unlike a feature update that changes the OS major version, this sort of build typically enables staged features, nudges UI inconsistencies toward parity, and adds device or enterprise capabilities that administrators have requested.
The pattern is familiar: Microsoft will roll features out gradually using server‑side flags and controlled feature rollouts, gather telemetry and feedback, then broaden availability. That means not every Insider will see every change immediately; some items are gated behind feature toggles or device compatibility checks. This build is an exemplar of that model — practical, targeted adjustments aimed at smoothing day‑to‑day friction.
What’s new in Build 28020.1673 — high level
- A built‑in network speed test surfaced from the taskbar network flyout and Wi‑Fi Quick Settings.
- Continued dark mode polishing: more legacy dialogs and File Explorer surfaces now respect system dark theme.
- Pan/tilt (PTZ) camera controls added to Settings for compatible webcams that expose UVC/PTZ controls.
- Emoji 16.0 additions: a curated set of new emoji in the emoji panel.
- Widgets settings converted from a dialog to a full‑page experience for easier configuration.
- RSAT (Remote Server Administration Tools) support for Arm64 as optional features.
- Adjustments to Quick Machine Recovery behavior for managed Pro devices.
- Several reliability and quality fixes (nearer to the metal fixes for File Explorer, Nearby Sharing, and Settings reliability).
These changes are targeted: they remove small pain points and make the OS slightly more self‑sufficient for common tasks (like checking internet speed) and administrative management on newer platforms (Arm64).
Built‑in network speed test — convenience and limits
What changed
Build 28020.1673 places a
“Perform speed test” /
“Test internet speed” control in the taskbar’s network icon menu and in Wi‑Fi/Cellular quick settings. Selecting it opens your default browser and launches a web‑hosted speed test that reports latency, download, and upload numbers.
Why it matters
- Discoverability: Most users already drop into the taskbar network flyout when investigating connectivity problems. Putting a quick test there reduces friction compared with opening a browser and navigating to Speedtest or Fast.com manually.
- Onboarding & troubleshooting: New PC setups and basic network troubleshooting benefit from a one‑click sanity check without hunting down a site or a utility.
Important caveats
- Not a native measurement engine. The feature launches a browser‑hosted test (Bing’s speed‑test widget or an embedded third‑party engine). That means it is a convenience shortcut, not a local diagnostic that bypasses browser/HTTP/CDN behavior.
- Accuracy variables: Results can be impacted by the browser’s network stack, proxying, VPNs, corporate web filters, CDN routing, or background processes using bandwidth. If you need authoritative measurements for SLA verification, packet capture, or deep troubleshooting, the browser test is only a starting point.
- Privacy and enterprise controls: Because it calls out to an online service, organizations concerned about telemetry, egress filtering, or compliance will want to evaluate how the browser widget behaves in their networks and whether group policies should restrict it.
Practical use
- Right‑click the network icon in the system tray or open Wi‑Fi quick settings.
- Select “Perform speed test.”
- The default browser opens and runs the test; read latency, download, and upload metrics.
- For more precise diagnostics, run in‑OS tools (iperf3, PowerShell network tests) or router/ISP tools.
The takeaway: it’s a helpful, visible convenience for most users, but not a replacement for network diagnostics in technical or regulated environments.
Dark mode polish — fewer white flashes, more consistency
What’s improved
The long‑running complaint about Windows’ inconsistent dark theme continues to get attention. Build 28020.1673 extends dark styling into more legacy File Explorer dialogs, notably the Folder Options dialog and several file‑operation prompts and progress surfaces. That reduces the jarring “white flash” experience when performing common tasks under a system‑wide dark theme.
Why this matters
Dark theme consistency is a small UX detail with outsized impact. Repeated white flashes or bright modal dialogs ruin the perceived quality of an otherwise cohesive dark UI. Fixing these surfaces:
- Reduces eye strain in low‑light conditions.
- Improves visual continuity when moving between modern and legacy UI elements.
- Signals Microsoft’s continued effort to modernize long‑standing Win32 UI gaps.
Known issues and caution
- Some legacy components still rely on older UI frameworks; not everything will be dark immediately. Microsoft stages these changes and toggles rollout across builds and channels.
- A previous cumulative preview introduced a separate regression that created a white flash in File Explorer for some users; these kinds of regressions are why staged rollouts and Insiders are essential for catching issues before broad distribution.
For users in the Insider channels, this means fewer jarring moments when copying, moving, or deleting files — but testers should still expect some incomplete coverage.
Camera pan/tilt controls in Settings — small but practical
Many modern webcams (and external PTZ cameras) expose basic pan/tilt/zoom controls via standard interfaces. Build 28020.1673 surfaces
pan and tilt controls directly inside Settings under
Bluetooth & devices > Cameras in the Basic settings section for compatible devices.
Benefits:
- Eliminates the need for vendor‑specific utility UIs for simple adjustments.
- Useful for hybrid workers who want quick framing adjustments without opening a separate app.
Limitations:
- Hardware dependent — only cameras that expose PTZ functionality through standard protocols will show controls.
- Not a replacement for advanced camera control suites required in professional streaming or broadcast setups.
Emoji 16 and Widgets — small content updates
This build adds a curated subset of
Emoji 16.0 to the emoji panel, a modest refresh that keeps the input palette current and culturally relevant. Meanwhile,
Widget Settings have been redesigned to open as a full‑page experience rather than a cramped dialog, improving discoverability and usability for customization.
Why these matter:
- Emoji updates keep communication visually current.
- A full‑page Widgets settings view makes it easier to manage feeds and personalization without wrestling with small popup space.
RSAT for Arm64 and enterprise tweaks
A notable entprise‑focused change in this build is
RSAT (Remote Server Administration Tools) availability on Windows 11 Arm64. IT administrators can now add modules such as Active Directory, Group Policy Management, DNS Server Tools, and more as Optional Features on Arm64 devices.
This is significant because:
- Arm64 hardware is increasingly common (thin clients, lightweight managed devices, some Surface models).
- Admins can maintain parity across device architectures without remote tool workarounds.
Quick Machine Recovery (QMR) behavior adjustments — enabling QMR for managed Pro devices under certain conditions — also aim to deliver more consistent recovery options across device SKUs and management states.
Enterprise caveats:
- Staged rollout — RSAT visibility and installability may depend on matching build levels, optional feature packages, or server‑side availability.
- Admins should validate optional feature state via Configuration Manager, Intune, or Group Policy and test RSAT modules before wider deployment.
Quality fixes and reliability improvements
Build 28020.1673 includes a grab‑bag of reliability fixes that Microsoft typically bundles into Canary releases. Highlights include:
- Fixes that address File Explorer windows and tabs unexpectedly jumping to Desktop/Home.
- Improved Nearby Sharing reliability for larger files.
- Reliability tweaks in Settings (e.g., Bluetooth & devices wheel configuration).
These fixes are the kind that matter to power users and admins who chase the small, reproducible bugs that undermine workflows.
Rollout details and where to find it
This build is distributed via the Windows Insider program Canary Channel and will appear as an optional Canary preview (KB package). As with other Canary releases, features in the build may be toggled on server‑side and rolled out gradually; not every Insider will see every feature immediately.
Practical notes:
- Canary builds are early and may be unstable; they’re for testing, not production.
- Some features require matching component updates or further service‑side enablement.
- If you’re not an Insider, expect features to arrive in Dev/Beta/Release Preview before hitting mainstream updates.
Risks, limitations, and privacy considerations
No change is purely beneficial. Here are the trade‑offs and risks to be aware of:
- Browser dependency for speed test. Because the “built‑in” speed test launches a browser widget, it:
- Depends on the browser’s network path and web rendering.
- Can be subject to corporate proxies, VPN artifacts, or CDN routing oddities.
- Raises telemetry/egress considerations for enterprises that restrict external services.
- Staged rollouts hide complexity. The progressive enablement model means administrators can be surprised when a feature appears on some machines and not others. That requires updated internal documentation and communication with users and help desk staff.
- Canary instability. Canary channel builds may contain regressions. IT departments should avoid pushing Canary builds to user fleets; home power users and testers can help surface bugs but should be prepared to troubleshoot.
- Visibility vs control. Adding shortcuts to web tools inside the OS is convenient for mainstream users, but organizations balancing security and compliance with usability may prefer granular control via group policies or blocking the underlying web endpoints.
- Hardware dependency. Camera PTZ support, RSAT on Arm64, and other device features depend on hardware vendors and driver implementations. Expect variability across models and OEM releases.
Recommendations for users and administrators
For home users and testers:
- Try the taskbar speed test for quick checks, but use iperf3 or router diagnostics for robust verification.
- If you prefer strict privacy, evaluate browser behavior and consider blocking speed test endpoints at the network perimeter.
- Join the Windows Insider Feedback loop: report any visual regressions, PTZ incompatibilities, or Widget issues through Feedback Hub.
For system administrators:
- Do not deploy Canary builds to production devices; use Dev/Beta for earlier testing, and Release Preview for near‑retail validation.
- Validate RSAT Arm64 modules in a lab environment before enabling on endpoints — confirm optional feature packaging and dependencies.
- Audit network policies and URL filtering to ensure the baked‑in speed test does not conflict with compliance rules or create unexpected egress.
- Update help desk KBs to account for the new “Perform speed test” flow so first‑line support can direct users appropriately (and avoid misinterpreting browser-derived numbers as authoritative).
- Monitor staged rollouts: Microsoft frequently gates features, so track which machines receive which toggles and maintain an internal test matrix.
How to evaluate the build (step‑by‑step)
- Enroll a disposable test machine into the Windows Insider program (Canary channel) — use a VM or a spare device to avoid production impact.
- Update Windows to the latest Canary build and confirm the build revision in Settings > System > About.
- Verify the network icon behavior: right‑click the network icon or open Wi‑Fi quick settings and look for “Perform speed test.” Run the test and compare results with iperf3 or your router’s diagnostics to understand variance.
- Test File Explorer dark mode: enable system dark theme and perform copy/move/delete flows to see whether dialogs and progress surfaces respect dark styling.
- Attach a compatible PTZ webcam and check Settings > Bluetooth & devices > Cameras for new basic pan/tilt controls.
- If you have Arm64 admin test devices, validate RSAT optional features and confirm required modules show for installation.
- Use Feedback Hub to file reproducible reports for any regression you encounter.
Critical analysis — strengths and concerns
Strengths
- Microsoft is addressing pragmatic user pain points: discoverability of network diagnostics, dark mode consistency, and the ability to control camera orientation from Settings.
- Enterprise support for Arm64 RSAT reflects a forward‑looking posture that recognizes heterogeneous hardware in managed estates.
- The incremental approach allows Microsoft to iterate quickly and catch regressions with Insiders before broader distribution.
Concerns
- The “built‑in” label for the speed test risks misinterpretation. It’s a shortcut to a web tool; presenting it as a native diagnostic could lead users or support staff to overtrust browser‑delivered numbers.
- Staged rollouts and server toggles can complicate troubleshooting and help‑desk scripting when a feature appears only on some machines.
- Canary channel instability remains a natural downside; testers must be prepared for regressions and intermittent breakage.
- Privacy and compliance implications of directing users to cloud‑hosted tools from the OS must be assessed by enterprise security teams.
Final verdict
Build 28020.1673 is not a blockbuster; it’s a pragmatic step toward a more cohesive Windows 11. The additions are user‑facing and immediately useful: a visible, quick way to check internet speed; more consistent dark theme behavior; native PTZ controls; and administrative parity across Arm64 hardware. Microsoft’s approach — small, tactical improvements — may not generate headlines, but it elevates everyday workflows and reduces fragmentation.
However, organizations and power users should treat the build as a preview: evaluate the browser‑based speed test in the context of their network setup, test RSAT resource availability on Arm64 devices in a lab, and keep an eye on staged rollout behavior to avoid surprises. For enthusiasts and Insiders, the build is worth testing; for enterprises, the changes are promising but require measured validation and policy consideration before broad adoption.
Build 28020.1673 is another incremental course correction — modest, useful, and emblematic of an operating system that’s now evolving through countless small refinements rather than a handful of sweeping updates. That’s a sign of maturity, but it demands vigilance from administrators and a pragmatic outlook from users who expect the OS to balance convenience with control.
Source: Neowin
Windows 11 gets built-in network speed, improved dark mode, and more in build 28020.1673