Comments
-
I have encountered a similar issue to the main post and turning of command line scan did not help. Instead, I added exclusion to the specific ps1 ****** in the Antivirus Advanced features which then allowed the ****** to be invoked in vscode terminal profile.
