After creating a Win32 package for device management, my PowerShell terminal sometimes enters a strange state where it tries to autocomplete or redraw on every keypress. Running `clear` temporarily restores normal behavior, but the problem eventually returns. The only reliable long-term workaround so far is closing the terminal window and starting a new session. Has anyone found a permanent fix or identified whether this is caused by PSReadLine or the terminal host?
3 Answers
This sounds like PSReadLine's inline prediction or redraw logic getting stuck rather 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. It’s also worth checking whether it happens only in Windows Terminal or also in the older console host; if it’s limited to one host, the issue may be rendering-related.
You could also remove and re-import the PSReadLine module to see whether a clean reload fixes the current session.
It may be a session-specific glitch, so opening a fresh PowerShell window is a reasonable temporary workaround. It’s annoying, but if the session isn’t needed for anything else, restarting it is usually quicker than fighting the broken autocomplete state.
Some people have trouble running the Intune packaging utility from PowerShell and find that it works more reliably from Command Prompt. If the issue only appears while launching the packaging tool from PowerShell, trying it from cmd may be a practical workaround.
Thanks, I’ll try disabling predictions first and then update PSReadLine if that confirms the cause.