wsl_doctor

Diagnose and repair WSL2 boot, network, VHDX, and resource issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ProwlrBot/prowlrbot --skill wsl-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wsl_doctor
Source: https://github.com/ProwlrBot/prowlrbot/tree/main/src/prowlrbot/ext/skills/wsl_doctor
Command: npx skills add https://github.com/ProwlrBot/prowlrbot --skill wsl-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

WSL2 environments often fail to start or function correctly due to issues in the WSL service, VHDX health, networking, memory, or Hyper-V configuration. This skill provides a structured, multi-level diagnostic workflow to quickly identify the root cause and guide safe, effective repairs.

Core Features & Use Cases

  • Progressive diagnostic ladder: from a quick health check (Level 1) to deep diagnostics (Levels 2-10) and recovery steps.
  • End-to-end remediation guidance: covers WSL service state, VHDX integrity, networking/DNS, memory and performance tuning, systemd usage, GPU passthrough issues, and time synchronization.
  • Distro-specific and environment-aware support: handles scenarios where distros fail to boot, are registered incorrectly, or file access to Windows drives is impaired.

Quick Start

Initiate the diagnostic ladder with a quick health check to begin automatic diagnosis and repair of common WSL2 problems.

Frequently Asked Questions about wsl_doctor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix WSL2 boot failures and distro startup issues?

To troubleshoot WSL2 networking and DNS resolution problems, the diagnostic process checks your virtual network adapters, DNS configuration, and Hyper-V settings to identify and repair connectivity failures within the Windows Subsystem for Linux.

How do I troubleshoot WSL2 networking and DNS resolution problems?

To troubleshoot WSL2 networking and DNS resolution problems, the diagnostic process checks your virtual network adapters, DNS configuration, and Hyper-V settings to identify and repair connectivity failures within the Windows Subsystem for Linux.

What is the best way to repair VHDX health issues in Windows Subsystem for Linux?

The best way to repair VHDX health issues in Windows Subsystem for Linux is to use deep diagnostic steps that verify disk integrity and resolve file access impairments to Windows drives, ensuring stable virtual disk operations.

Does WSL2 troubleshooting require elevated privileges for Hyper-V and GPU passthrough recovery?

Yes, WSL2 troubleshooting requires elevated privileges for critical operations. Enforcing prerequisites ensures the diagnostic process can safely manage Hyper-V configurations, GPU passthrough scenarios, and resource contention repairs.

Why does my WSL2 environment experience memory and performance contention?

WSL2 environments experience memory and performance contention due to misconfigured resource allocation or systemd usage. The diagnostic workflow identifies these bottlenecks and provides tuning steps to optimize virtualization performance.