Overview 💥
In rare cases, Windows Server or Windows Workstation Inspectors may remain stuck in a Scheduled state and fail to execute. This behavior was identified in Liongard Agent version 5.0.4, where inspections may not transition from Scheduled to Running as expected.
This article outlines:
The recommended remediation (agent upgrade)
Validation steps
Advanced recovery options if the issue persists
Symptoms 🤒
You may observe one or more of the following:
Windows Inspectors remain indefinitely in Scheduled
No inspection execution despite successful scheduling
No explicit error shown in the Inspector UI
Agent appears online, but inspections do not run
‼️ This issue is specific to Agent v5.0.4 and does not impact later LTS versions.
Why This Happens 🤔
Agent version 5.0.4 contained a defect that could prevent Windows-based inspectors from transitioning out of the Scheduled state. The issue is resolved in later LTS agent releases, and upgrading the agent fully resolves the condition.
Primary Resolution (Recommended) 🧑🏫
Upgrade the Agent to the Latest LTS Version
Run the following PowerShell command on the affected system to silently upgrade the agent. This is best executed via your RMM platform or Intune.
if (Get-WmiObject Win32_Product | Where-Object { $_.Name -like "Liongard Agent*" }) { Invoke-WebRequest -Uri "https://agents.static.liongard.com/LiongardAgent-lts.msi" -OutFile "$env:TEMP\LiongardAgent-lts.msi"; Start-Process msiexec.exe -ArgumentList "/i `"$env:TEMP\LiongardAgent-lts.msi`" /quiet /norestart" -Wait }🧠 How This Fix Works
Step | Action |
1 | Detects an existing Liongard Agent installation |
2 | Downloads the latest LTS MSI |
3 | Performs a silent, in-place upgrade |
4 | Preserves environment mapping and agent identity |
Validation Steps 👨🔧
After upgrading:
Navigate to Admin → Agents
Confirm the agent is now on the latest LTS version
Verify inspectors transition from:
Scheduled → Running → Completed
✅ If inspections run successfully, no further action is required.
If the Issue Persists After Agent Upgrade 🧐
If inspectors remain stuck after upgrading to the latest LTS agent, proceed with a clean reinstall using the Liongard Agent Install Script, which handles edge cases not addressed by MSI upgrades.
Why Use the Script?
The script provides:
Capability | Benefit |
Optional uninstall before install | Removes corrupted services, folders, and registry keys |
MachineGuid collision detection | Prevents agent overwrite issues |
Environment validation | Ensures correct environment assignment |
Silent MSI execution | Avoids UI-based failures |
Transcript logging | Full execution trace |
MSI installer logging | Clear exit codes and errors |
FAQ's 🙋♂️
Q: Does this affect agents newer than 5.0.4?
No. The issue is isolated to v5.0.4 and resolved in later LTS releases.
Q: Can restarting the agent service fix this?
No. Service restarts do not resolve this condition.
Q: Is uninstalling required in all cases?
No. Most cases are resolved with an in-place LTS upgrade.
Q: Should I downgrade the agent instead?
No. Downgrading is not supported and may introduce inspection failures.
When to Contact Support 🦁
If issue persist after:
Upgrading the agent to the latest LTS
Attempting a reinstall using the Agent Install Script
Please submit a support ticket to our team and include the following information:
Windows OS version
Agent version before and after upgrade
Inspector type(s) affected
Screenshot of inspectors stuck in Scheduled
Relevant Windows Event Viewer errors (If available)
Summary 🤩
Agent v5.0.4 may cause Windows inspectors to remain stuck in Scheduled
Upgrading to the latest LTS agent resolves the issue
If the issue persists, perform a clean reinstall using the Agent Install Script
Logs are essential for further troubleshooting
Downgrades are not recommended or supported