Leapwork Diagnosis Report - Frequently Asked Questions

Leapwork Diagnosis Report - Frequently Asked Questions

Introduction
In this article, you’ll find answers to frequently asked questions about the Leapwork Diagnosis Report, a comprehensive tool designed to analyze your Windows system and verify that it meets all the requirements for running Leapwork automation efficiently. The report performs over 30+ checks across system configuration, security, network, and environment settings, helping you quickly identify and resolve any issues that could affect performance.

What the script checks:

What report is generated.
The tool produces a self-contained HTML report with an interactive dashboard (collapsible sections), color-coded statuses ( Success/green, Warning/yellow, Error/red), detailed findings with explanations, and actionable items (download links, commands, and suggested fixes), plus timestamp and detected Leapwork version in a professional, shareable layout. The script is read-only: it does not modify files, registry, or settings, does not change network/security configuration, does not require admin rights for most checks, and creates only a temporary HTML file.

  1. How do I run the script?
    You can run it via PowerShell or as a standalone executable:

    # Navigate to the script directory  
cd "C:\Path\To\ReadinessScript"  

# Run the script  
.\LeapworkReadinessReport.ps1  

    # Standalone executable  
LeapworkReadinessReport.exe

    After generation, the report opens automatically in your default browser.

  2. Why do I need this script?

  1. Do I need administrator privileges?
    Not required for most checks. For clarity:

  1. How long does it take to run?
    Typical runtime is 30–60 seconds; network checks may add 10–30 seconds; comprehensive scans usually complete in under 2 minutes.

  2. Where is the report saved?
    It’s saved in your temp folder as:

%TEMP%\Leapwork_Readiness_Report_YYYYMMDD_HHMMSS.html

Example: 

C:\Users\YourName\AppData\Local\Temp\Leapwork_Readiness_Report_20241201_143022.html
  1. How should I handle Error/Warning results?

  1. Can I share the report?
    Yes. It’s a single, self-contained HTML file with professional formatting; sensitive data is masked.

  2. How often should I run the script?
    Before installing Leapwork; after system changes (Windows updates, software installs, configuration changes); during troubleshooting; for monthly/quarterly health checks; and before major deployments.

  3. Which Leapwork versions are supported?
    The script automatically detects your Leapwork version and adapts checks accordingly. Some requirements vary by version ( e.g., .NET 6 not needed after 2025.3); it’s designed to work with current and upcoming releases.

  4. What if the script doesn’t detect my Leapwork installation?
    It looks in the standard paths:

%ProgramFiles%\Leapwork\Controller\  

%ProgramFiles%\Leapwork\Studio\  

%ProgramFiles%\Leapwork\Agent\

If not detected, it still performs general checks, but version-specific optimizations may not apply, verify standard locations or a custom install path.

  1. Can I run this on multiple machines or at scale?
    Yes. It’s portable (no installation required), suitable for batch/enterprise deployment (e.g., Group Policy or deployment tools), and reports can be centralized for analysis.

  2. I encounter errors while running the script, what should I try first?
    Common fixes:

  1. How do I get support?

  1. Is my data secure?
    All checks run locally; no data is transmitted (except for the connectivity tests themselves). Credentials/keys are masked, the report is saved locally, and no persistent logging is performed.

  2. Can the Leapwork Readiness Script be used in Cloud (LAAS) environments?
    Yes. For Cloud (LAAS) environments, the readiness script can be executed on the Studio machine to validate connectivity with the Cloud Controller.

  3. Do I need to run the readiness script on Cloud Controller or Cloud Agent machines?
    No. Customers using Cloud Controllers do not need access to or execution on Cloud Controller or Cloud Agent machines. The validation can be performed directly from the Studio machine.

  4. Is the PowerShell readiness script still required in Leapwork 2026.1.0 and later?
    Not always. Starting from Leapwork version 2026.1.0, Diagnostics can be run directly from Studio by selecting the Controller and generating the required report without manually executing the PowerShell script.

  5. What should customers on older (N-1) versions do for LAAS diagnostics?
    No. There is no dependency on specific Leapwork versions for this scenario. For LAAS environments, running Diagnostics on the LAAS Controller or Cloud Agent machines is not required. Diagnostics only need to be executed on the Studio machine to validate connectivity with the Cloud Controller.

The Diagnostics tool was primarily designed to validate connectivity between Leapwork components for on-premises environments.

  1. What is the purpose of the Leapwork Diagnostics / Readiness Report?
    The Diagnostics / Readiness Report helps validate the Leapwork environment by checking connectivity, configuration, system readiness, and related dependencies to assist with troubleshooting and baseline validation.

For any clarification, please contact our Priority Support.