After creating a Win32 package for an Intune app, my PowerShell terminal sometimes enters a strange state where autocomplete or inline suggestions trigger on nearly every keypress. Running `clear` temporarily fixes it, but the behavior eventually returns. The only reliable long-term workaround so far is closing that terminal window and opening a new session. Has anyone found a permanent fix or identified what causes this?
3 Answers
This sounds more like PSReadLine's inline prediction or screen-redraw logic getting stuck than a problem with the terminal itself. Run `Get-PSReadLineOption`, then temporarily disable predictions with `Set-PSReadLineOption -PredictionSource None`. If that stops the behavior, update PSReadLine with `Update-Module PSReadLine`, since older versions had rendering bugs that could cause symptoms like this.
Removing and importing PSReadLine again may also help if the module loaded incorrectly in that session.
It may be worth checking whether this only happens in Windows Terminal or also in the older console host. If it is limited to one host, the issue is probably a rendering or input-handling glitch rather than the packaging utility itself.
I’ve run into similar behavior and usually just start a fresh PowerShell session when I need to finish packaging. It is not ideal, but opening a new window clears the broken state reliably.
Thanks, I’ll try disabling predictions first and then update PSReadLine if that confirms the cause.