Forum Discussion
Autoruns does not show services with long image paths
This issue looks like a string-handling limit within the Autoruns parsing engine itself rather than a change in Windows. When Autoruns scans the services registry hive, it reads the image path data. If a third-party app or argument pushes that string past a certain character limit, Autoruns seems to skip the entire entry silently instead of loading it.
While waiting for a tool update from the Sysinternals team, you can check for these long-path services using these built-in administrative steps:
1. Check via PowerShell
You can bypass the tool interface and view any service with an unusually long path by running an elevated PowerShell window as an Administrator. Run this command to list services with paths longer than 260 characters:
Get-CimInstance Win32_Service | Where-Object { $_.PathName.Length -gt 260 } | Select Name, DisplayName, PathName
2. Check the Registry Directly
You can manually verify that no hidden service is running under a long path by opening the Registry Editor (regedit) and navigating to the main services folder at:
HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services
From there, you can select the specific service name to inspect its ImagePath value directly in the right-hand panel.