You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Get-PESecurity is a great tool, and it works well to scan a wide variety of EXEs and DLLs...I have one EXE that fails to scan (hasplms.exe sentinel security license manger) with the error at line 592:
"Cannot find type [PE.IMAGE_SECTION_HEADER, Win32, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null]: make sure the assembly containing this type is loaded."
Is there anything that can be done about that? I can send the EXE to someone for analysis if that's helpful.
Thanks in advance :)
-Dave
Edit: this is on a Server 2008R2 Standard 64bit machine with PowerShell 2.0 in case that makes any difference.
The text was updated successfully, but these errors were encountered:
>powershell.exe -file .\test.ps1
Unable to scan file Error: Cannot find type [PE.IMAGE_SECTION_HEADER, Win32, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null]: make sure the assembly containing this type is loaded.
its null
I get an exception thrown and end up in my catch with the $tmp set to $null ...but perhaps there's some facet of powershell exception handling I've missed. It wouldn't do me any good to remove it from this trycatch, as we're multiple levels of try deep while working on this line already.
Hi
Get-PESecurity is a great tool, and it works well to scan a wide variety of EXEs and DLLs...I have one EXE that fails to scan (hasplms.exe sentinel security license manger) with the error at line 592:
"Cannot find type [PE.IMAGE_SECTION_HEADER, Win32, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null]: make sure the assembly containing this type is loaded."
Is there anything that can be done about that? I can send the EXE to someone for analysis if that's helpful.
Thanks in advance :)
-Dave
Edit: this is on a Server 2008R2 Standard 64bit machine with PowerShell 2.0 in case that makes any difference.
The text was updated successfully, but these errors were encountered: