Reply to thread

Message

<blockquote data-quote="ForgottenSeer 97327" data-source="post: 1042570">I am not a VoodooShield user, but there is a user manual available of V6: <a href="https://www.voodooshield.com/Download/VoodooShieldUserGuide.pdf" target="_blank">https://www.voodooshield.com/Download/VoodooShieldUserGuide.pdf</a>V6 has rudimentary command line protection, so you could check whether powerscript commands are listed here[SPOILER=&quot;Command lines&quot;][ATTACH=full]275825[/ATTACH][/SPOILER]You could also check whether by default Powershell folder is mentioned (in System32 and SysWOW64) here[SPOILER=&quot;Custom (blocked)&nbsp; folders when VS is ON-OFF&quot;][ATTACH=full]275826[/ATTACH][/SPOILER]As a last solution you could check whether powershell.exe is mentioned as vulnerable process here[SPOILER=&quot;Advanced settings&quot;][ATTACH=full]275827[/ATTACH][/SPOILER]The manual mentions what to do when a vulnerable process is not listed (add it and disable &quot;Automatically allow by parent&quot;), but since the manual is outdated I would wait until experienced VS users chime in or contact the developer when nobody responds, before altering advanced settings. A safer suggestion is to reset VS to default settings and check again (you might have accidentely whitelisted powershell yourself).</blockquote>

[QUOTE="ForgottenSeer 97327, post: 1042570"] I am not a VoodooShield user, but there is a user manual available of V6: [URL]https://www.voodooshield.com/Download/VoodooShieldUserGuide.pdf[/URL] V6 has rudimentary command line protection, so you could check whether powerscript commands are listed here [SPOILER="Command lines"] [ATTACH type="full" alt="1685541831764.png"]275825[/ATTACH] [/SPOILER] You could also check whether by default Powershell folder is mentioned (in System32 and SysWOW64) here [SPOILER="Custom (blocked) folders when VS is ON-OFF"] [ATTACH type="full" alt="1685541976260.png"]275826[/ATTACH] [/SPOILER] As a last solution you could check whether powershell.exe is mentioned as vulnerable process here [SPOILER="Advanced settings"] [ATTACH type="full" alt="1685542134348.png"]275827[/ATTACH] [/SPOILER] The manual mentions what to do when a vulnerable process is not listed (add it and disable "Automatically allow by parent"), but since the manual is outdated I would wait until experienced VS users chime in or contact the developer when nobody responds, before altering advanced settings. A safer suggestion is to reset VS to default settings and check again (you might have accidentely whitelisted powershell yourself). [/QUOTE]

Verification