AIToday
Large Language ModelsAI Coding AssistantsPublickeyPublished: Aug 5, 2026, 01:01 JST3 min read

Microsoft releases Windows Performance Analyzer with AI tracing support

Microsoft releases Windows Performance Analyzer with AI tracing support

Key takeaway

  • Microsoft has released an early preview of Windows Performance Analyzer MCP, which embeds GitHub Copilot CLI into the Windows Performance Analyzer tool to help developers diagnose app slowness.

  • Instead of requiring deep knowledge of trace analysis, developers can now ask Copilot in natural language why their applications are slow—and Copilot will pinpoint bottlenecks related to CPU, disk, memory, network, or drivers, then generate a digestible report of findings.

3 Key Points

  1. What happened

    Microsoft announced an early preview of Windows Performance Analyzer MCP (Model Context Protocol), which integrates GitHub Copilot CLI into the Windows Performance Analyzer tool to help diagnose why Windows applications run slowly.

  2. Why it matters

    Normally, identifying performance bottlenecks—whether from CPU, file I/O, or network issues—requires Windows Performance Analyzer expertise and experience with Event Tracing for Windows logs. Copilot can now analyze trace data using natural language, letting developers ask questions directly rather than manually parsing complex system logs.

  3. What to watch

    The tool is in early preview; availability and release timeline for general use are not yet specified in the announcement.

In Depth

Read the full story

Microsoft announced an early preview of Windows Performance Analyzer MCP (Model Context Protocol), a new tool that integrates AI-powered trace analysis into the existing Windows Performance Analyzer workflow. The motivation is straightforward: when a Windows application runs slowly, developers need to identify whether the bottleneck lies in CPU processing, file I/O, or network operations. Traditionally, this diagnosis requires using the Windows Performance Analyzer tool to record and analyze Event Tracing for Windows logs—a process that demands both technical knowledge and hands-on experience.

The WPA MCP bridges that gap by embedding GitHub Copilot CLI directly into the Windows Performance Analyzer. Instead of manually parsing trace logs, developers can now type natural language prompts and ask Copilot questions about the trace data. Copilot then analyzes the trace, identifies relevant events and patterns, determines what is causing slowness, and generates a human-readable report. Microsoft provided a sample prompt that instructs Copilot to prioritize evidence of common performance problems—hangs, delayed input response, long wait times, CPU starvation, disk bottlenecks, memory pressure, paging, service contention, and problematic drivers—and to distinguish between system-wide issues and problems isolated to a single application or service. Using this guidance, Copilot forms hypotheses, extracts related data, and narrows down the root cause. The tool is currently available as an early preview, with no formal release date announced.

Context & Analysis

Windows developers have long faced a knowledge barrier when diagnosing application performance. The Windows Performance Analyzer tool itself is powerful but requires users to understand Event Tracing for Windows logs and have significant experience interpreting trace data. By embedding GitHub Copilot CLI directly into the analyzer, Microsoft is lowering that barrier: developers can now pose questions in plain English and let the AI do the pattern-matching and hypothesis-building across complex trace files.

This move reflects a broader trend of using large language models to simplify expert tools. Rather than forcing developers to learn specialized log analysis syntax or manually hunt through thousands of events, Copilot can read the trace, synthesize the data, and present findings in a clear report. The sample prompt Microsoft provided—asking Copilot to prioritize evidence of slowness such as CPU starvation, disk bottlenecks, and memory pressure—illustrates how the tool can guide analysis toward the most likely culprits.

FAQ

How do you use Windows Performance Analyzer MCP?
You write a natural language prompt to GitHub Copilot CLI within the Windows Performance Analyzer window. Copilot then analyzes the trace data, identifies relevant information, determines bottlenecks (such as CPU starvation, disk bottlenecks, memory pressure, or problematic drivers), and creates a report based on the insights it finds.
What problems can it help identify?
The tool can help distinguish hangs, delayed input response, long ready times, CPU starvation, disk bottlenecks, memory pressure, paging, service contention, and problematic drivers—and separate system-wide bottlenecks from issues isolated to a single app or service.

Get the latest Large Language Models news every morning

AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.

Free · takes 30 seconds · unsubscribe anytime

Ask AI

Ask AI anything about this article. Q&As are published on this page for other readers too.

Related Articles

Next articleAI agents need managers, not just users—companies lag in training

The AI news that matters, in one minute each morning.

Sign up free