-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EXE & PowerShell collectors issues #596
Comments
Just for information, He is not alone: I have same exact issue on a Windows Server 2012 R2. However, i do not controls the Server. (CTF-style environment) |
Will look into this |
Is this still an issue with the new sharphound v1.1.1? |
yes, the issue is still there
|
Issue still here, can't run SharpHound (exe or ps1) in old systems since a few versions. In my case SharpHound from 3.0.5 version was working fine on those old systems but I couldn't load the files in the lastest BloodHound (compatibility problems). I will be glad someone does it |
Ran into the same issue, it seems its because of .Net version installed on the victim machine - v4.6 should fix this: One idea is to try older versions of SharpHound which were written according to v4.0 or less. |
Downloaded and tested the latest PowerShell collector, it doesn't seem to work for some reason.
Tested again with the EXE collector and got this:
Test machines is Windows Server 2012 R2 & Microsoft Windows Server 2019 Datacenter, both fully updated.
The text was updated successfully, but these errors were encountered: