This could have happened because:
1. GetSusp was run from within a zip file
2. When run this way, the process execution tree would be explorer.exe --> winzip.exe --> getsusp.exe instead of explorer.exe --> getsusp.exe
3. Because of this condition, GetSusp attempted to scan itself since the scan results got reported as LOCKED, it got reported.
The issue won't occur if you extract and run GetSusp from a separate folder.
I do not use it from a zip file!
I use an extracted Getsusp remote or extracted getsusp.exe locally.
Example Script - a simple remote getsusp collection (it should not be the reason):
robocopy.exe c:\scripts\getsusp \\%1\c$\Windows\temp\ getsusp.exe
psexec.exe \\%1 C:\WINNT\Temp\getsusp.exe --silent --date=90
robocopy.exe \\%1\c$\Windows\temp\ c:\scripts\getsusp\ gsusp_*.zip