Windows 11 Insider KB5065793: Speed Test, Copilot Get Started, and Cloud Storage APIs

Microsoft’s latest Insider checkpoint—packaged as KB5065793 and appearing in recent Dev and Beta preview builds—delivers a handful of practical interface changes and deeper platform plumbing that together reveal Microsoft’s current priorities: quicker diagnostic access, tighter Copilot integration, and broader cloud-storage hooks in File Explorer. The visible bits—most notably a one‑click network speed test accessible from the taskbar and a Microsoft 365 Copilot entry surfaced inside the Get Started app—are small but purposeful. Under the surface, updates to search and storage APIs and a modest accessibility tweak (a new Wait time before acting option in Voice Access) show Microsoft continuing to fold AI, cloud and accessibility into the core Windows 11 experience while rolling these changes out via the Insider program and controlled feature rollouts.

Background / Overview​

Windows 11 preview builds are delivered on parallel development tracks (Dev, Beta and Release Preview) and are often distributed as cumulative/enablement packages with KB identifiers for patching. The build identifiers tied to this checkpoint—reported in community flight trackers and visible in recent Insider updates—include Build 26220.xxxx for the version aligned to 25H2 and Build 26120.xxxx for the 24H2 servicing line. The KB label commonly associated with the most recent checkpoint in late‑September is KB5065793, which several preview participants and press outlets observed in builds reported around September 29–30, 2025.
These updates follow Microsoft’s long‑standing pattern: new UI surfaces and lightweight utilities are previewed to Insiders first, while core platform changes (APIs, cloud provider hooks) are introduced in parallel so ecosystem partners can adopt them. Many items are gated via controlled feature rollout, so availability will vary by device, region, subscription status and the Insider toggle setting in Settings > Windows Update.

---

What’s new, at a glance​

• A built‑in network speed test launcher placed in the network system tray menu and in Wi‑Fi quick settings for fast diagnostics.
• A Microsoft 365 Copilot page surfaced inside the Get Started app for commercial/managed devices with active Microsoft 365 subscriptions.
• Updated Windows Search and File Explorer search placeholder text on Copilot+ PCs to encourage descriptive, image‑aware queries.
• New or extended StorageProvider/Cloud Files APIs to let cloud storage vendors integrate more tightly with File Explorer Home.
• Voice access improvement adding a Wait time before acting setting to tune the delay between recognized speech and command execution.
• Numerous stability and quality fixes addressing crashes, display and taskbar inconsistencies in preview builds.

Each of these items targets a distinct use case: immediate troubleshooting (speed test), discoverability and adoption (Copilot placement), smarter local search (Copilot+ semantic search), developer enablement (storage APIs), and accessibility refinement (voice timing).

---

Built‑in network speed test: convenient launcher or subtle promotion?​

What changed​

A new option appears in two familiar places: the network/system tray icon (right‑click context menu) and the Wi‑Fi quick settings flyout (left‑click). Activating the control does not run a native kernel‑level measurement tool inside Windows; instead, it launches the system’s default browser and opens a web‑hosted speed test. The UI is intentionally lightweight: one click from the place most people go to check connectivity, and you’re taken straight to a web speed test widget that reports download, upload and latency when you start it.

Why this matters​

• For everyday users and support technicians, the new shortcut removes friction. When connectivity problems interrupt work, being able to run a quick speed check from the taskbar is faster than hunting for a web site or installing a third‑party tool.
• Because the test runs in the browser, Microsoft keeps the OS surface light and avoids adding a native test engine that would require server selection, update management, or telemetry controls inside the OS.

Practical limits and trade‑offs​

• The taskbar control is a launcher, not an embedded diagnostic engine. That means test methodology, server selection and retention of results are controlled by the web widget, not Windows itself.
• Routing users to a web test introduces variability (browser extensions, cached resources or proxy settings can affect results) and makes the measurement less reproducible than a native client.
• There’s a perception risk: because the web widget is hosted by Microsoft’s web properties, critics will frame this as product placement for Microsoft search services rather than a neutral utility. That concern is real for users who prefer vendor‑neutral tools or independent verification.

Bottom line​

The taskbar speed test is a solid usability win for quick triage, but users and IT teams who need reproducible, auditable measurements should continue to rely on dedicated test tools or enterprise monitoring systems. Treat the new shortcut as a convenience, not a replacement for formal network validation.

---

Microsoft 365 Copilot surfaced in Get Started: discoverability or intrusion?​

What changed​

Preview builds add a Microsoft 365 Copilot page to the Get Started experience on Windows. The page is targeted: it appears for commercial/managed devices that are governed by enterprise enrollment and where an active Microsoft 365 subscription exists. The idea is to help business users discover Copilot features, on‑ramp to the Microsoft 365 Copilot app, and understand how Copilot integrates with Office apps and OneDrive.

Why Microsoft is doing it​

Microsoft is aggressively integrating Copilot across Windows and its productivity apps. Putting a Copilot entry in Get Started is a classic product‑placement strategy to shorten the discovery path for users who might otherwise not realize their subscription includes AI features. For businesses, this can speed adoption and help IT teams highlight new capabilities to end users.

Governance and admin impact​

• On commercial devices the page respects subscription and management signals. Enterprises will have policy tools to control deployment and visibility.
• Admins who do not want Copilot promoted on managed endpoints should review Microsoft 365 and device management settings, including Microsoft 365 Apps Admin Center controls that influence app deployment and visibility.

UX and user reaction​

This placement will be welcomed by teams trying to increase Copilot adoption. Power users and privacy‑conscious employees may regard it as another merchandising surface. The change underscores a broader reality: Copilot is migrating from optional add‑on to a first‑class feature that Microsoft expects enterprises to enable and manage.

---

File Explorer, Windows Search and Copilot+ PCs: smarter local queries​

Semantic search and placeholder copy​

Windows Search continues to evolve on Copilot+ PCs (machines with onboard NPUs and the Copilot+ hardware profile). The search box and File Explorer search now show updated placeholder text that nudges users to describe images, files or scenarios (for example, “find the file with the chicken tostada recipe” or “show me photos of bridge at sunset”). That change reflects Microsoft’s shift toward semantic indexing and natural‑language queries for local files and images.

On‑hover actions and Ask Copilot​

File Explorer Home is getting on‑hover actions that accelerate common tasks. For Insiders on Copilot+ PCs you may see Ask Copilot about this file and similar context actions in the Home view. These actions launch Copilot flows that can summarize documents, analyze images, or extract key data.

What developers and users should know​

• Semantic search is currently gated to Copilot+ hardware profiles and supported file types. Expect staged rollouts by device capability.
• Search privacy controls remain available: you can restrict cloud content indexing or opt out of certain types of indexing via the Search permissions settings.
• The experience is designed to work fully offline on capable hardware, with local models handling semantic indexing—important for privacy‑sensitive scenarios.

Impact​

For knowledge workers this materially improves discoverability, especially when filenames are poor or images need natural-language descriptors. For IT and privacy teams, it requires a fresh look at search permissions, data access consent, and how semantic indexing aligns with data governance.

---

StorageProvider APIs: cloud storage integration gets friendlier​

The technical context​

Windows has supported cloud integration for a while—Cloud Files APIs, Cloud Filter (CFAPI) and the Windows.Storage.Provider namespace are established plumbing that enable OneDrive‑style placeholder files, sync roots and shell integration. The recent preview updates extend and modernize these integration points with new or clarified StorageProvider capabilities that make it easier for third‑party cloud storage vendors to surface content inside File Explorer Home and to participate in the Recommended / Shared UX.

What this enables​

• Cloud providers can register richer sync roots and present files in File Explorer Home with thumbnails, activity metadata and shared‑with information.
• Providers gain more predictable hooks to show recommended or shared content, improving parity with built‑in OneDrive experiences.
• For enterprises, this reduces friction when deploying alternative cloud storage solutions and helps preserve a more consistent user experience across consumer and third‑party clouds.

Security and operational considerations​

• Any cloud provider integration must respect system‑level security boundaries and the Sync Root registration model that governs placeholder hydration and access.
• Administrators should validate third‑party providers for compliance, data residency, and encryption practices before rolling out integrations that expose cloud content to broad user populations.
• Vendors that integrate must be mindful of file indexing, local cache size and potential performance impact on low‑resource devices.

Practical advice for developers​

• Review the existing Cloud Files API and Windows.Storage.Provider guidance for best practices on placeholder files and sync roots.
• Test integration across typical enterprise scenarios: multiple accounts, Entra ID (work/school) sign‑ins, offline access and aggressive indexing policies.
• Ensure robust telemetry and error reporting so administrators can diagnose cloud provider‑specific sync issues.

---

Accessibility: voice access gets a small but meaningful tweak​

Wait time before acting​

Voice Access, Microsoft’s speech control and dictation accessibility feature, gains a Wait time before acting option. This setting lets users configure how long the system waits after recognizing speech before executing a command—useful for people who speak with pauses or who need a little time to finish phrasing a command.

Why it matters​

• Small timing adjustments can dramatically improve speech recognition reliability for users with different speaking rhythms or in noisy environments.
• The setting aligns with Microsoft’s incremental approach to accessibility: add focused, configurable options that let users tune behavior to their needs.

Where to find it​

Voice Access settings (Settings > Accessibility > Speech > Voice Access) include the new delay control under the management options. Users can select a wait time that best suits their cadence, helping prevent premature command execution.

---

Fixes, stability and rollout mechanics​

The KB/preview package also bundles traditional fixes: crash mitigations, taskbar icon sync issues (battery icon mismatch), display and explorer stability improvements, and miscellaneous Click to Do/Click to Talk bug patches. Microsoft continues to use controlled feature rollouts—Insiders who turn on the “Get the latest updates as soon as available” toggle receive new UI experiments earlier, while others get features gradually.
From a deployment perspective, these changes illustrate Microsoft’s twofold model:

• Surface‑level UX changes (taskbar shortcuts, Get Started entries) are iterated quickly and tested via Insiders and press.
• Platform and API work (StorageProvider, search indexing enhancements) is rolled in parallel so partners and developers can prepare for adoption.

---

Critical analysis: strengths, risks, and unanswered questions​

Strengths​

• Practical convenience: The network speed test launcher is a quick win for non‑technical users and support desks. Small discoverability tweaks like this reduce friction and support faster troubleshooting.
• Productivity surface: Bringing Microsoft 365 Copilot into Get Started recognizes that discovery matters—many enterprise features fail because users don’t know they exist. This placement will smooth adoption where Copilot is enabled.
• Platform enablement: Extended StorageProvider APIs and search improvements show Microsoft preparing the OS for an era where local, cloud and AI experiences are tightly interwoven. Those APIs lower barriers for third‑party cloud providers and encourage richer File Explorer experiences.
• Accessibility nuance: The new Voice Access timing option reflects a pragmatic approach—accessibility improvements that actually reduce friction and are easy to configure.

Risks and caveats​

• Perception of promotion: Routing the taskbar speed test to a Microsoft‑hosted web widget reinforces concerns that Windows can be used to promote Microsoft services. Even if functionally convenient, users and regulators may interpret this as product placement.
• Measurement fidelity: Browser‑based speed tests are valid for quick checks but are sensitive to browser state and extensions. Enterprises requiring repeatable measurements should not treat the shortcut as authoritative.
• Fragmented availability: Copilot+ dependent features and hardware gating (NPU requirements) create inconsistent experiences across the Windows installed base, complicating support and training.
• Privacy and data access: Deeper Copilot integration in File Explorer and the semantic search model raise legitimate data governance questions. Admins must reassess index scope, consent, and encryption policies when enabling these features.
• Unclear enterprise opt‑out paths: While administrators have tools to manage software distribution, rapid changes to Get Started or automatic installations of Copilot‑adjacent apps in broader Microsoft programs can surprise IT teams if default opt‑outs aren’t obvious.

Unverifiable or partially verified claims​

Some community reports and early coverage describe exactly which Insider builds map to this KB label and the controlled rollout details. While Microsoft’s Insider channel release documentation confirms many of the feature categories (search improvements, file‑search semantics, File Explorer Home changes and Copilot experiences), a few specific UI strings and the KB ↔ build mapping seen in community trackers are currently best‑effort observations. Those specifics should be treated as provisional until confirmed in official release notes or enterprise update metadata.

---

Action checklist: what users, IT pros and developers should do now​

For IT administrators

• Review Windows Update and Insider settings on test devices; do not enable broad deployment to production without validation.
• Audit Microsoft 365 and device management policies to confirm how Copilot and Microsoft 365 Copilot app promotion are governed.
• Evaluate the Search permissions settings and plan index scope to align semantic indexing with privacy and compliance requirements.
• Test third‑party StorageProvider integrations in a lab and validate sync root behavior and placeholder hydration across OS updates.

For power users and technicians

• Try the taskbar speed test as a first‑pass triage tool; validate results with a second, independent measurement when accuracy matters.
• If Copilot shows in Get Started and you prefer not to use it, check the app list and uninstall or adjust settings to control visibility.
• If you rely on Voice Access, experiment with the new Wait time before acting setting to improve command recognition.

For developers and ISVs

• Explore the Cloud Files API and Windows.Storage.Provider documentation; plan to adopt the newer integration hooks to surface content in File Explorer Home.
• Test semantic file search behaviors and ensure any indexing or metadata your application exposes is compatible with Windows’ search model.
• Monitor controlled rollout signals and use the Insider channels for early testing.

---

Final verdict​

KB5065793 is emblematic of Microsoft’s current Windows strategy: combine small, high‑utility front‑end conveniences with behind‑the‑scenes platform extensions so partners and customers can adopt richer cloud and AI experiences. The network speed test shortcut is an immediate UX improvement for everyday troubleshooting, but it is intentionally lightweight and points to a web‑hosted test rather than a native engine. The Get Started Copilot placement and File Explorer/Copilot search upgrades underline Microsoft’s push to make Copilot a default part of the productivity stack—valuable for adopters but requiring careful governance in managed environments. Meanwhile, further investment in StorageProvider and cloud integration APIs shows Microsoft maturing the platform so third‑party cloud providers can integrate more closely with File Explorer Home.
For users and administrators, the practical approach is to treat these updates as preview features: evaluate on test machines, confirm privacy and compliance posture, and adopt at a pace that matches organizational risk tolerance. The preview crops up inside the Windows Insider ecosystem—where Microsoft collects feedback and refines decisions—so expect UI and behavior changes as these features move toward broader availability. The short term delivers convenience; the medium term raises policy and governance questions that enterprises will need to answer.

---

Source: Windows Report KB5065793 adds built-in network speed test & Microsoft 365 Copilot ad upfront in Windows 11 25H2