windows device troubleshoot

    1

    Diagnose and fix Windows Device Manager error codes (10/43/48/52) using a six-layer system attribution model.

    $10

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    windows device troubleshoot

    Example session with this skill installed

    My Realtek network card is showing an exclamation mark in Device Manager with Error Code 48. I tried reinstalling the driver three times but it still won't start.

    • Read your context and instructions
    • Compiled the windows device troubleshoot

    I have analyzed the symptoms for your Realtek network adapter. Error Code 48 specifically indicates that the driver is being blocked by the system because it is not compatible with a security feature, likely Hypervisor-protected Code Integrity (HVCI) within Virtualization-Based Security (VBS).

    Diagnostic Report & Resolution

    Since reinstalling the driver failed, the issue is at the

    Policy Layer. A recent Windows update likely enabled VBS, which now enforces strict WHQL driver signing that your current driver version does not meet.

    Diagnostic CategoryValue / Status
    Device Manager Code48 (CM_PROB_SOFTWARE_BLOCKED)
    NTSTATUS Equivalent0xC000036B (STATUS_DRIVER_BLOCKED)
    Probable CauseVBS/HVCI Enforcement
    Verification RequiredGet-CimInstance -ClassName Win32_DeviceGuard

    Recommended Action: Disable VBS/HVCI Enforcement

    If you cannot find a newer WHQL-signed driver from the manufacturer, use this script to disable the blocking policy.

    @echo off
    :: Self-elevate to Administrator
    net session >nul 2>&1
    if errorlevel 1 (
        powershell -NoProfile -Command "Start-Process -FilePath '%~f0' -Verb RunAs"
        exit /b
    )
    
    echo Checking BitLocker status...
    manage-bde -status C: | findstr /C:"Fully Encrypted"
    echo NOTE: Ensure you have your BitLocker recovery key before proceeding.
    
    echo Exporting registry backup to %USERPROFILE%\Desktop\vbs_backup.reg
    reg export "HKLM\System\CurrentControlSet\Control\DeviceGuard" "%USERPROFILE%\Desktop\vbs_backup.reg" /y
    
    echo Disabling Virtualization Based Security...
    reg add "HKLM\System\CurrentControlSet\Control\DeviceGuard" /v "EnableVirtualizationBasedSecurity" /t REG_DWORD /d 0 /f
    reg add "HKLM\System\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity" /v "Enabled" /t REG_DWORD /d 0 /f
    
    echo System must reboot to apply changes.
    pause
    

    Next steps

    1. Run manage-bde -status to ensure you have recovery keys if BitLocker is active.
    2. Execute the block above as a .cmd file and reboot your PC.
    3. After reboot, check Get-PnpDevice -InstanceId <ID> to verify the status is now OK.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Diagnostic efforts for Windows device failures often fail because developers focus on updating drivers rather than identifying the root cause. This skill systematiclly resolves "Device cannot start" errors by analyzing the system state beyond the driver layer.

    What it does

    • Multi-layer diagnosis analyzes hardware, resources, conflicts, permissions, policies, and drivers to find the specific point of failure.
    • Error code mapping decodes device manager codes like 10, 43, 48, and 52 into actionable NTSTATUS insights.
    • VBS & Security profiling detects when Virtualization-Based Security or Windows Defender Application Control (WDAC) blocks legitimate drivers.
    • Automated fact collection gathers device manifests, driver details, network stack status, and VBS history in one pass.
    • Integrity verification checks registry ACLs and DriverStore permissions to resolve "Access Denied" errors.

    How it works

    1. Fact collection via diag-device.ps1 to pull the full system state and recent update history.
    2. Three-point triage to confirm if the device is physically started, map the error code, and attribute the failure to a specific system change.
    3. Change attribution to correlate the onset of the failure with Windows Updates or security policy shifts.
    4. Targeted remediation using provided .cmd or .ps1 scripts for VBS disabling, registry repair, or filter driver cleanup.

    Frameworks & tools

    The skill utilizes PowerShell 5.1+, Windows Management Instrumentation (WMI), and native Windows CLI tools like pnputil, manage-bde, and reg. It handles specific encoding requirements for CMD (GBK/ASCII) and PowerShell (UTF-8 BOM).

    Why this beats prompting it yourself

    Generic prompts usually result in a loop of "reinstall the driver" or "run sfc /scannow." This skill uses a six-layer diagnostic model that distinguishes between a corrupted INF file and a VBS-enforced driver block, saving hours of trial and error.

    Use cases

    • Resolve Code 48 "driver blocked" errors after a Windows security update.
    • Troubleshoot NICs or Wi-Fi adapters that show no response when plugged in.
    • Fix Bluetooth or USB controller failures where multiple driver versions have failed.
    • Perform a forensic audit of why a device worked yesterday but failed after a reboot.

    Known limitations

    Does not support Windows 7 or 8.1. It cannot fix physical hardware damage or issues requiring component replacement. Admin privileges are required for most diagnostic and repair steps.

    Requires PowerShell 5.1+ and Admin rights. No support for Windows 7/8.1, macOS, or Linux. Cannot repair physical hardware failure.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed today

    Requires

    Git

    Permissions

    Terminal / Shell
    Listedtoday

    What's inside

    Frequently Asked Questions

    This skill focuses on resolving persistent 'Device cannot start' error codes (10, 43, 48, 52) by analyzing deep system layers like registry ACLs, VBS security policies, and resource conflicts that standard driver updates often miss.

    The skill is designed for Windows 10 and 11 environments and requires a runtime capable of executing PowerShell 5.1+ and WMI commands with administrative privileges to perform deep-system diagnostics.

    You receive a comprehensive diagnostic toolkit including the six-layer attribution model, automated data collection scripts (diag-device.ps1), and targeted remediation scripts for registry and policy repairs.

    Yes, the skill is specifically engineered to detect when Virtualization-Based Security (VBS) or Windows Defender Application Control (WDAC) is silently blocking drivers, which is a common cause of Code 48 and 52 errors.

    While it can identify if a device is physically unresponsive, the skill is a software-level diagnostic tool and cannot repair physical hardware failure or internal component damage.

    New in Testing & Debugging