debug terminal is not allowing any keyboard input

Hello,

Thank you for testing 2026.3.4 and for confirming that the debug terminal now opens.

We reproduced the keyboard problem in our lab on 2026.3.4.

When a job stops at Wait-Debugger, the debug terminal shows the [DBG] prompt, but most of the time it ignores what you type.

It happens in both the Integrated and the PowerShell 7 environments, and the other terminals are not affected.

So you are not missing anything, this is a defect in the debug terminal itself.

We are reporting it to our development team, and we will let you know when a fix is available.

Until then, the buttons above the debug terminal still work, because they do not need the keyboard.

• Continue lets the script run to the end.

• Step Into, Step Over, and Step Out move through the script.

• List Source Code shows the source code of the script.

You can hover over each button to see its name.

Reloading the page sometimes brings typing back, but not reliably.

To check variable values while the script is paused, you can attach to it from a PowerShell console on the PowerShell Universal server.

The job page shows the two numbers you need in the PID / Runspace field.

Enter-PSHostProcess -Id <PID>
Get-Runspace
Debug-Runspace -Id <Runspace>

You must run these commands as an administrator on the server, or as the account that runs the job.

The full steps are in our documentation, in the section about debugging from a PowerShell console: https://docs.devolutions.net/powershell-universal/development/debugging-scripts

Best regards,