The announcement is real, but the feature isn't available yet, and Microsoft has left important details out. Here is what is confirmed so far.
What Microsoft announced at Ignite
Pavan Davuluri, Executive Vice President of Windows + Devices, described the feature in Microsoft's Ignite post on the Windows Experience Blog. The company says Copilot can run a read-only scan of the system to help find the root cause of errors or performance issues, then explain what's going on in clear terms.
Diagnostics is one of three related capabilities. Microsoft says three local capabilities are coming soon to Copilot+ PCs:
- Local context: Copilot can use information already on the PC, such as open files, running apps and the device's current state. Microsoft says with permission, Copilot can use that information to offer better help.
- Local actions: Copilot will be able to take action across Windows, from working with files to helping diagnose PC issues, while the user stays in control.
- Local models: Microsoft says Copilot will increasingly use AI models that run on the PC and will use the cloud when a task requires it.
Microsoft gives two example questions for diagnostics: why Bluetooth audio isn't working and why a network connection is slow. Its pitch to IT departments is that this kind of help could handle many of the most common reasons employees contact support.
In short: Microsoft has announced diagnostics as part of a broader local AI push for Copilot+ PCs. It is described as a read-only scan that explains what it finds.
The Bluetooth demo
Windows Central reported on Microsoft's demo video, which shows the feature step by step. In the demo, a user tells Copilot that audio isn't playing through their Bluetooth headphones and asks it to diagnose the issue. Copilot then asked for permission to access files and read system information. After that permission was granted, Copilot determined the cause of the issue.
The diagnosis was a familiar one. Copilot found that the headphones were connected but Windows 11 was likely sending audio to a different device. Copilot then explained how to fix the problem.
That's a modest example, and that makes it a good one. A wrong default output device is a very common cause of support calls. The headphones are paired, the volume is up, and the sound is still going to a monitor's speakers. If Copilot can reliably catch problems like this, it will save a lot of people a lot of frustration.
Windows Central also said that, as far as I can tell, the video Microsoft shared is the first time we've seen PC diagnostics running in Copilot. In the demo, Copilot opens from Windows 11's redesigned Search experience, which recently entered testing with Windows Insiders. That's the interface shown in the demo. Microsoft hasn't said diagnostics will require the new Search.
Until it ships, you can check this particular problem yourself. In Windows 11, open the speaker icon in Quick Settings or go to Settings > System > Sound. Then check which device is selected for output. This is general Windows guidance, not something taken from Microsoft's Copilot materials.
The rollout so far
Microsoft first described these capabilities in its October 7, 2026 post introducing Windows Hybrid Intelligence. In that post, local actions included organizing files, assessing device diagnostics, troubleshooting issues, coding, and carrying out workflows directly on the device. Microsoft said at the time that these features would begin rolling out on Copilot+ PCs "in the coming months." Footnotes in that post said availability may vary by device, market and silicon platform.
Copilot has done some read-only troubleshooting before. Over the summer, Windows-focused outlets reported on PC Insights, a Copilot feature that answers plain-language questions about a PC's state. One report described it as an opt-in, read-only feature with a gradual rollout limited to the United States as of July 2026. WindowsNews.ai reported that when you ask a question, Copilot requests one‑time access to the relevant Windows API, composes a response, and then stops. The same outlet raised a valid concern about overhead. It said the Copilot app can consume up to 1GB of RAM, potentially exacerbating performance issues.
Microsoft hasn't said whether the Ignite diagnostics feature replaces or builds on PC Insights. They look like related steps, but there's no confirmation that they are the same product. The difference that matters now is scope: the Ignite announcement is aimed at Copilot+ PCs, while PC Insights was reported as a U.S.-limited Copilot app feature.
In short: Copilot has been heading toward read-only troubleshooting since the summer. The Ignite demo is the first public look at root-cause diagnosis for Copilot+ PCs.
What Microsoft hasn't said yet
Here are the important gaps:
| Question | What's known |
|---|---|
| Release date | "Coming soon" at Ignite. In October, Microsoft said "in the coming months." No firm date. |
| Hardware | Copilot+ PCs. No support has been announced for other Windows 11 PCs. |
| Build / Insider channel | Not specified for diagnostics. |
| What the scan inspects | No full list published. The demo asked for access to files and system information. |
| Local vs. cloud processing | The scan is local. Copilot uses a mix of local and cloud models. Microsoft hasn't said whether diagnostic data ever leaves the PC. |
| Automatic repair | Not promised. The scan is read-only, and Copilot explains the fix. |
| Enterprise controls | Policy, retention and audit settings for this feature haven't been detailed. |
| Accuracy | Microsoft has published no ticket-reduction figures or failure rates. |
"Local" doesn't automatically mean "offline" or "private." Microsoft says the scan runs on the device. It also says Copilot sends tasks to the cloud when needed. Until Microsoft publishes documentation, nobody outside the company can say exactly where a given troubleshooting session's data goes.
What it means for IT departments
For IT teams, the case for this feature is easy to see: fewer tickets for wrong audio devices, Wi-Fi problems and similar issues. But Microsoft's "fewer support calls" claim is a goal at this point, not a measured result.
A few practical points for admins:
- Diagnosis isn't remediation. Copilot can explain what it thinks is wrong, but someone still has to decide whether to apply the fix. That matters most for driver, network and VPN changes on managed devices, where a well-meant "fix" can conflict with policy.
- Read-only is a deliberate boundary. Microsoft separately says Copilot will be able to take actions across Windows, such as working with files. The diagnostic scan is described as read-only. Don't assume that limit applies to every other local action.
- Check your Copilot+ PC inventory. If you're planning hardware refreshes, this feature will only reach devices that meet the Copilot+ PC requirements, at least at first.
- Wait for governance documentation. Ask for permission prompts, data flows and Intune or policy controls before turning this on across a fleet.
Note also that Microsoft announced this alongside a lot of agent-related security work at Ignite, including containment, identity and governance for AI that acts on a user's behalf. A troubleshooting assistant that reads system state fits that model: it gets access to look, not permission to make changes.
The bottom line
The Bluetooth demo shows that Copilot can catch a very common Windows problem and explain it clearly. Whether it works well in practice depends on details Microsoft hasn't published: how accurate the diagnoses are, what the scan collects, where the data goes and how it behaves when it can't find a cause. Until then, it's a feature to watch closely.
References
- Copilot could soon answer the eternal Windows question: ‘Why isn’t this working?’ Windows Central · 2026-11-17T19:33:02+00:00
- Microsoft Rolls Out Copilot PC Insights: Plain-English PC Diagnostics, with a Heavy Appetite - Windows News windowsnews.ai
- Building Windows for hybrid intelligence | Windows Experience Blog blogs.windows.com