Re: Not stopping at ANY breakpoints Win10 (1809) PowerShell v 5.1
Posted: Tue Jul 02, 2019 11:11 pm
Hi Frank.
The communication with the debugger is IP port based using local host and it is obviously working since the error messages come back and the script runs, if I read this correctly.
The debugger simply uses Set-PSBreakpoint to set breakpoints and the number of error messages should be equivalent to the number of break- or trace-points set.
For most other debugger operations it also uses the official cmdlets since there is no actual debugger API in PowerShell other than that.
First thing we need is the output of the $psversiontable from a console on an affected machine.
Secondly, open a powershell console and
use
Set-PSBreakpoint -Script "whicheverscriptyouhave.ps1" -line <valid_line>
Then try to run the script and see if it stops there in the console.
Then try to debug a script in the ISE.
All this will tell us if the PowerShell installation on your machines is valid and operating.
My intuition tells me this is a permission issue. Somewhere (and I don't know where) your right to debug or use Set-PSBreakpoint is curtailed.
I do not know if this is a machine wide thing or a per process or per user thing, but that is my guess.
I would assume you tried to run PowerShell Studio elevated and tried there, yes?
The communication with the debugger is IP port based using local host and it is obviously working since the error messages come back and the script runs, if I read this correctly.
The debugger simply uses Set-PSBreakpoint to set breakpoints and the number of error messages should be equivalent to the number of break- or trace-points set.
For most other debugger operations it also uses the official cmdlets since there is no actual debugger API in PowerShell other than that.
First thing we need is the output of the $psversiontable from a console on an affected machine.
Secondly, open a powershell console and
use
Set-PSBreakpoint -Script "whicheverscriptyouhave.ps1" -line <valid_line>
Then try to run the script and see if it stops there in the console.
Then try to debug a script in the ISE.
All this will tell us if the PowerShell installation on your machines is valid and operating.
My intuition tells me this is a permission issue. Somewhere (and I don't know where) your right to debug or use Set-PSBreakpoint is curtailed.
I do not know if this is a machine wide thing or a per process or per user thing, but that is my guess.
I would assume you tried to run PowerShell Studio elevated and tried there, yes?