Microsoft has integrated GitHub Copilot into Windows Performance Analyzer, a specialized diagnostic tool that helps engineers identify performance bottlenecks in Windows systems. The new feature, released as an early preview on July 30, allows developers to ask natural-language questions about Windows trace data, rather than manually navigating dense timelines and graphs. However, the integration comes with important limitations: it requires an active GitHub Copilot subscription and currently works only with GitHub Copilot, not other AI assistants.

What Problem Does This Solve for Developers?

Windows Performance Analyzer, or WPA, is a technical tool used by IT professionals and performance engineers to diagnose why computers slow down. When a machine experiences a sluggish boot, unexpected CPU spikes, storage delays, driver problems, or input lag, engineers collect trace files using Windows Performance Recorder and then open them in WPA to inspect detailed timelines, graphs, and process activity. The challenge is that interpreting this data requires specialized knowledge. A competent investigator needs to know which recording profile was used, which graph answers a particular question, and how to connect visible symptoms to underlying causes.

The new Copilot integration shortens this orientation work. Users can open a trace file in WPA, select a Copilot control in the upper-right corner, and ask questions in plain English. Copilot can then inspect the available trace data, identify relevant tables and signals, produce a summary, and guide follow-up analysis. Questions can be broad, such as "Why did this machine feel slow?" or narrow, such as "Which process added the most delay?" or "Was this workload CPU-bound or waiting on disk?".

How Does the AI Actually Work Within the Tool?

The Copilot integration does not automatically diagnose Windows problems on its own. Instead, it works from a finite trace file collected for a specific reproduction of a problem. The quality of the diagnosis depends entirely on what data was captured in the trace. If a trace does not include the events needed to establish disk input/output, ready-thread delays, deferred procedure call activity, stack walks, or a particular provider's events, no Copilot prompt can reconstruct what was never captured.

Microsoft explicitly warns that large-language-model output can vary between runs and may be incomplete or incorrect. Users are told to validate results against the underlying tables, graphs, time ranges, processes, threads, and call stacks before taking action. In performance work, this is not boilerplate caution. A confident but wrong explanation can send a developer after the application with the highest CPU use when the real delay was a blocked thread, a driver's deferred procedure calls, an antivirus filter, storage latency, or hardware waking from a low-power state.

Steps to Get Started With WPA Copilot Integration

• Verify Subscription Requirements: Ensure you have an active GitHub Copilot subscription, as the WPA MCP (Model Context Protocol) preview currently requires both GitHub Copilot and a paid subscription to function.
• Collect a Trace File: Use Windows Performance Recorder to capture a trace file after reproducing the performance problem you want to investigate, such as a slow boot or unexpected CPU spike.
• Open and Inspect in WPA: Load the trace file in Windows Performance Analyzer and use the Copilot control in the upper-right corner to ask natural-language questions about the data.
• Validate Results Against Raw Data: Cross-check any Copilot explanation against the underlying tables, graphs, and call stacks in WPA to confirm accuracy before taking action based on the diagnosis.
• Configure MCP Server Settings: Use WPA settings to inspect the WPA MCP server's read-only tools, control whether it starts with WPA, and disable other configured MCP servers if needed to reduce startup time.

What Are the Practical Limitations?

The Copilot integration is aimed at performance engineers and IT professionals who regularly collect and analyze Windows traces, not ordinary users looking for Copilot to speed up a sluggish laptop. Different performance scenarios require different Windows Performance Recorder profiles and different WPA views. High CPU usage, memory leaks, wait analysis, power issues, and disk activity are not a single data set with one universal answer. The preview lowers the expertise required to start an investigation, but it does not remove the need to understand what was captured and what the underlying data means.

The current integration also embeds GitHub Copilot CLI in WPA and loads configured MCP servers alongside it. Microsoft added settings to inspect the WPA MCP server's read-only tools, control whether it starts with WPA, and disable other configured MCP servers to reduce startup time and context noise. This is a sign of a developer-oriented preview rather than a polished Windows feature.

How Does This Fit Into Microsoft's Broader ETW Strategy?

The WPA Copilot preview is not Microsoft's only recent attempt to make Event Tracing for Windows (ETW) analysis conversational. On July 21, Microsoft released an early preview of its ETW MCP server, a headless companion intended for terminal-driven, scripted, batch, continuous integration, and integrated development environment-based investigation. The two tools use the same underlying TraceProcessor and ETW data layer, according to Microsoft. The difference is the interface. ETW MCP works without a WPA window and is designed to process, query, filter, aggregate, compare, and rank traces through an MCP-aware client. WPA MCP is for investigators who want the AI's explanation tethered to the familiar visual graphs and tables inside the WPA application.

A Windows team could use the headless ETW MCP to compare baseline and candidate traces across automated performance tests, then open the difficult case in WPA MCP to inspect the evidence visually. The former makes repetitive performance regression triage more automatable; the latter makes an individual trace less forbidding. ETW MCP examples include comparing a baseline trace against a trial run, querying hot symbols, identifying time windows with regressions, and running Critical Path Analysis to find what actually delayed an end-to-end scenario.

What Does the Subscription Requirement Mean for Organizations?

The current early preview supports GitHub Copilot only, and users need an active GitHub Copilot subscription. This is an important operational detail for organizations evaluating the tool. Windows Performance Analyzer itself has long been available through Microsoft's performance-tooling distribution, but the AI layer is tied to a separate licensed developer service. A team that collects traces through Windows Performance Recorder or already uses WPA will not gain the conversational layer merely by updating its diagnostic toolkit.

Microsoft has not committed to a date for support for other assistants, model providers, or MCP clients inside WPA. The ETW MCP server supports GitHub Copilot or another MCP-aware AI client, while the WPA MCP preview supports GitHub Copilot only. This distinction matters for teams considering long-term adoption and multi-vendor AI strategies.