Forum Discussion

DavidTapuchi's avatar
DavidTapuchi
Copper Contributor
Nov 05, 2026

Autoruns does not show services with long image paths

I was running Autoruns to confirm no unexpected services, and I noticed the Screenconnect instance I was connected through, is not in the list.

Creating a new service with a long path gives the same result. Considering that Screenconnect is commonly abused, seeing Screenconnect services is important.

I'm 99% sure I've seen Screenconnect in Autoruns before, so what changed now? Is it a change in Windows?

The following reproduces the behavior with a test service (thanks, Claude):
$long = 'x' * 3000

New-Service -Name 'ZZLongPathTest' -BinaryPathName ""C:\Windows\System32\notepad.exe" $long" -StartupType Automatic

.\autorunsc64.exe -accepteula -nobanner -a s -ct | sls ZZLongPathTest

1 Reply

  • syserrorlog's avatar
    syserrorlog
    Iron Contributor

    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.