Microsoft’s latest Insider drop pulls another convenience trick into the system tray:
Windows 11 Canary Build 28020.1673 adds a one‑click network speed test in the taskbar alongside a raft of smaller but meaningful improvements — from
camera pan and tilt controls to
RSAT support on Arm64, Emoji 16.0 entries, improvements to Widgets and File Explorer dark mode, and changes to the Quick Machine Recovery behavior. The catch: the “built‑in” speed test is a deliberately lightweight launcher that opens a browser and runs Bing’s web-hosted speed test (which in turn surfaces an Ookla‑powered measurement backend), not a native Windows measurement engine. That distinction shapes both the feature’s usefulness and its limits for everyday users and IT pros alike.
Background
Microsoft rolls out experimental features through the Windows Insider program’s Canary, Dev, Beta, and Release Preview rings to gather feedback and stage gradual rollouts. Build 28020.1673 was published to the Canary channel on February 27, 2026, and showcases a pattern we’ve seen increasingly: small, discoverable utilities and management conveniences tested in the taskbar and Settings, while heavy lifting (diagnostics, telemetry, and enterprise controls) remains behind admin policies or separate tooling.
This build is noteworthy because it highlights two concurrent trends in Windows development: 1) making routine diagnostic checks more discoverable to mainstream users, and 2) extending enterprise management parity (for example, RSAT on Arm64 and Quick Machine Recovery behavior adjustments) as Arm devices and hybrid work scenarios grow. The speed test is the most visible consumer-facing change; the rest are incremental but meaningful for specific user groups.
What’s new in Build 28020.1673 — quick overview
- Built‑in network speed test: A “Perform speed test” / “Test internet speed” control appears in the network icon right‑click menu and Wi‑Fi/Cellular quick settings. Selecting it opens your default browser and launches Bing’s speed test widget, reporting latency, download and upload speeds.
- Camera (PTZ) controls: New pan and tilt controls in Settings > Bluetooth & devices > Cameras for supported UVC/PTZ webcams.
- RSAT on Arm64: Remote Server Administration Tools are available as optional features on Arm64 Windows 11, making administration tools like AD management and Group Policy tools accessible on Arm devices.
- Quick Machine Recovery (QMR): QMR behavior adjusted so it auto‑enables on certain Windows Pro devices (non‑domain and enterprise‑managed), extending recovery access.
- Emoji 16.0: A curated set of new Emoji 16.0 glyphs is rolling out to the emoji panel.
- Widgets: Widget settings open as a full‑page experience rather than a dialog.
- File Explorer & Settings fixes: Dark mode consistency in Folder Options, reliability fixes for Settings > Bluetooth & Devices > Wheel, and Nearby Sharing improvements for larger files.
These changes are rolled out gradually using feature‑toggle systems, so you may see them appear on a subset of Insider devices before a broader ramp.
Deep dive: The taskbar network speed test — what it actually is
How the feature works (user flow)
- Right‑click the network/system‑tray icon or open the Wi‑Fi/Cellular quick settings.
- Choose Perform speed test (labeling may show as “Test internet speed”).
- Windows launches your default browser and navigates to the Bing speed test widget.
- The web UI runs the test and reports latency (ping), download, and upload speeds inside the browser.
It’s intentionally simple — a discoverable shortcut positioned where users already go for quick connectivity checks.
Why Microsoft designed it this way
- Rapid iteration: A web‑hosted test can be updated and tweaked without shipping OS patches.
- Leverage an existing backend: Bing’s speed test has historically been tied to Ookla’s Speedtest backend. Using an established measurement service saves Microsoft the cost and complexity of global test servers and measurement tuning.
- User discoverability: Most people first open the network flyout when troubleshooting connectivity, so adding a test there shortens the path to a quick sanity check.
- Minimal OS footprint: No new services or scheduled tasks are required; the button is a thin client that leans on web infrastructure.
What it is not: not a native diagnostic tool
- The test does not run inside Windows as a native measurement engine.
- Results are presented in the browser and aren’t persisted in Windows’ diagnostic history.
- There’s no built‑in Windows log or exportable forensic output tied to the OS first‑class diagnostics.
This distinction matters: convenience versus control. For quick checks the feature is handy; for repeatable, auditable network diagnostics you’ll still prefer native or third‑party tools.
Measurement accuracy and technical caveats
A browser‑hosted speed test that delegates measurement to an external backend has several technical implications that affect accuracy and interpretation.
- Browser stack variability: Different browsers, extensions, proxies, or HTTP caches can influence throughput measurements. A browser with heavy extensions or a content blocker may skew results.
- CDN and server selection: Ookla and similar services select test servers based on geographic and network topology considerations. The chosen server, its load, and proximity will influence results.
- Transport path differences: A test that runs over HTTP/HTTPS from a browser will take a different transport path than some native protocols, especially if local VPNs or packet filters alter traffic.
- Local caching and hardware acceleration: Browser caching behavior and offload features (e.g., TCP acceleration, NIC offloads) may change how the test behaves compared to a native binary test.
- Captive portals and blocked web access: If a network blocks Bing or redirects web queries (hotel or enterprise captive portals), the taskbar shortcut may fail to open or run the test, whereas a native diagnostic might still produce useful system‑level logs.
For everyday confirmations (“Am I getting the speed I pay for?”), browser tests are fine. For performance baselining, SLA verification, or forensic troubleshooting, use controlled native tools, measurement appliances, or coordinated server endpoints.
Privacy and telemetry considerations
Launching a web test surfaces several privacy and policy questions that are particularly relevant in enterprise environments.
- Third‑party server contact: The test contacts a web endpoint hosted by Bing/Ookla. That exchange can involve IP logging, geographic inference, and telemetry handled by those services.
- Default provider bias: There’s no in‑UI option to choose an alternate provider — the taskbar shortcut directs you to Bing’s test. Organizations that prefer a different vendor or in‑house test will need to instruct users accordingly or block access if required.
- Browser context: The test runs in the user’s browser profile, which may have different auth cookies or tracking parameters. That could lead to cross‑site requests that distinguish a user’s session.
- Enterprise policy control: Administrators should evaluate whether the shortcut contravenes corporate telemetry or data‑exfiltration policies, particularly in regulated industries. Group Policy, endpoint configuration tools, or network filtering can restrict access, but this requires explicit IT action.
For privacy‑sensitive deployments, recommend documenting the behavior and, if necessary, blocking access to the test endpoints or providing an approved internal speed‑test portal.
Why this matters to IT admins and power users
- RSAT on Arm64: The availability of Remote Server Administration Tools as optional features on Arm64 is a big step for IT teams standardizing on Arm PCs. Admins can install Group Policy Management, DNS, DHCP and other RSAT features directly on Arm devices without workarounds.
- Quick Machine Recovery (QMR) changes mean recovery behavior is being aligned across device families, but the automatic enablement on certain Windows Pro devices may need to be validated against organizational recovery policies.
- Sysmon and Entra ID changes: Broader rollout notes associated with parallel preview updates indicate improved Entra SID resolution and potential Sysmon support implications for endpoint monitoring and incident response.
- Deployability: Canary builds are unstable by design. Admins should not use Canary for production devices; the build’s enterprise‑facing improvements are signals of intent but will need validation in Beta/Release Preview before wide deployment.
IT teams must treat this build as a preview of direction rather than a mandate. Use lab testing to validate RSAT on Arm64, QMR impact on imaging workflows, and any network policy implications from the taskbar speed test.
Camera pan/tilt (PTZ) controls — practical notes
Windows 11’s inclusion of PTZ controls for supported UVC/PTZ webcams moves common physical adjustments into the Settings UI.
- The controls are placed under Settings > Bluetooth & devices > Cameras, in the Basic settings for each camera.
- Microsoft’s notes do not list which camera models are supported; support appears to be limited to UVC‑compliant PTZ webcams that expose pan/tilt controls to the OS.
- For teams using conference room cameras or prosumer PTZ devices, this adds convenience and eliminates the need for vendor software for basic adjustments.
Caveat: because Microsoft does not publish a compatibility matrix in this build, expect variation across vendors. Test specific cameras to confirm the controls appear and behave as expected before relying on the Settings UI for fleet management.
UX and accessibility refinements: Widgets, Emoji, and File Explorer
Small UX changes in this build improve discoverability and polish:
- Widgets settings full‑page: Moving Widget settings from a dialog to a full‑page experience reduces friction when customizing feeds and configuration.
- Emoji 16.0 entries: A curated set of emoji is appearing in the emoji panel, bringing Windows’ emoji support closer to modern mobile sets. This improves cross‑platform consistency for messaging and social apps.
- File Explorer dark mode consistency: Fixes to Folder Options dialog reduce jarring light UI elements in dark mode, improving accessibility and user comfort.
These changes are minor on their own but contribute to overall OS coherence that impacts daily use.
How to try the feature (for Insiders) — step‑by‑step
- Join the Windows Insider Program with your Microsoft account.
- On a test PC, go to Settings > Windows Update > Windows Insider Program.
- Choose the Canary channel (Build 28020.1673 targets this ring).
- Install updates through Windows Update and reboot when prompted.
- Right‑click the network icon or open Wi‑Fi/Cellular quick settings to look for Perform speed test.
- Click the option — your default browser will open and run the Bing‑hosted speed test.
Note: Canary builds require a clean install to exit to a lower channel later. Do not use Canary on production devices.
Recommendations for users and administrators
- For casual checks: Use the taskbar shortcut when you want a fast, single‑click check of latency and throughput.
- For reproducible diagnostics: Use dedicated measurement tools (native testers, Speedtest apps, iperf3 to a controlled server, or ISP/enterprise diagnostics) that allow consistent server selection and logging.
- For privacy‑sensitive environments: Evaluate and, if necessary, block the Bing test endpoints at the network perimeter or educate users to use approved internal tools.
- For Arm device fleets: Test RSAT functionality thoroughly; confirm that management workflows (Group Policy, AD tools) work as expected on Arm64 images.
- For camera deployments: Pilot PTZ controls for vendor‑specific cameras to confirm compatibility before standardizing on the Settings UI.
- For recovery strategy: Review Quick Machine Recovery auto‑enable behavior in imaging and recovery playbooks to avoid surprises during mass rollouts.
Potential risks and shortcomings
- Misleading “built‑in” label: Calling the feature “built‑in” may mislead non‑technical users into thinking the measurement is OS‑native and auditable; clear messaging is important to set correct expectations.
- Default provider lock‑in: Out‑of‑the‑box routing to Bing’s test (and, by extension, Ookla’s backend) gives Microsoft’s provider precedence. Users or organizations that prefer an alternate measurement service must take action.
- No in‑OS persistence: Results are not captured in Windows for trend analysis or automated monitoring. For repeated testing, organizations must use separate tools.
- Browser and policy dependencies: If browser policies block Bing or the speed test domain, the feature will fail silently — not ideal during troubleshooting scenarios where web access itself is impaired.
- Enterprise auditability: For compliance scenarios that require evidence of testing or log retention, a browser test will not meet audit requirements without additional logging.
These are all solvable, but they require either product evolution (e.g., an optional native mode) or organizational controls.
The strategic perspective: convenience vs. capability
Microsoft’s approach here is pragmatic: solve for the 80% use case with minimal OS bloat. A taskbar launcher to a maintained web tool is low effort, fast to iterate, and improves discoverability for basic problems. However, the trade‑off is a lack of depth: professionals and managed environments will still want native, configurable, scriptable, and auditable tools.
For Windows to address both audiences, future options could include:
- An opt‑in native diagnostic mode that uses OS network stacks and exports logs to Event Viewer or a TPM‑backed store for audits.
- A policy to let organizations choose or whitelist an alternate speed‑test provider or an internal server pool.
- In‑OS persistence of last‑run results with an API for management tools to query or export them.
Until then, the new taskbar test will live as a convenience shortcut — valuable for users who need a quick answer but insufficient for formal diagnostics.
Final verdict
Build 28020.1673 continues Microsoft’s methodical push: deliver incremental usability wins while iterating on enterprise parity and management tools. The
taskbar network speed test is a smart, low‑friction addition for everyday users and support staff who need a quick check without hunting down a website. Its design — a browser‑launched Bing widget backed by an established test provider — is pragmatic but limits the test’s validity for technical or compliance use cases.
The broader improvements —
RSAT on Arm64,
camera PTZ controls,
QMR adjustments, and small but meaningful UX fixes — show Microsoft is balancing consumer convenience with the realities of modern endpoint management. IT teams should treat this build as an indicator of direction: evaluate RSAT on Arm64, confirm recovery workflows, and create guidance on the new speed test for users.
If Microsoft wants this feature to be more than a convenience shortcut, the next steps are clear: add in‑OS measurement options, admin controls for provider selection, and built‑in logging for trend analysis. Until then, users get faster discoverability and admins get another item to validate — a reasonable exchange in the evolution of Windows diagnostic tooling.
Source: Windows Report
https://windowsreport.com/windows-1...73-adds-built-in-network-speed-test-and-more/