Nov 07 2016
A few months back, I experimented with windows forms to create dialog boxes for input - as opposed to using the 'Read-Host' command line input.
I then found that after using said scripts, when I unlocked my screen, the PowerShell ISE application had frozen, so I had to use Task Manager to 'kill' the application process.
I stopped my experimenting as it wasn't critical, but wondered if anyone else had experienced this scenario - where the ISE session is frozen following a lock/unlock action on the PC.
Hoping to understand what can be done to avoid the problem while continuing to use dialog boxes in PowerShell, please.