Code change:
Type: <bBug</bThe terminal in VSCode - insiders is unable to display special characters in terminals after latest update How it looks in VSCode: ! How it looks in VSCode - insiders ! The font settings are the exact same for both versions VS Code version: Code - Insiders 1.90.0-insider (, 2024-05-03T05:49:15.006Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (40)</summaryExtensionVersion ------ better-comments3.0.2 TabOut0.2.2 Bookmarks13.5.0 doxdocgen1.4.0 githistory0.6.20 gitlens14.9.1 copilot1.184.0 copilot-chat0.14.1 latex-workshop9.20.1 rainbow-csv3.11.0 git-graph1.30.0 autopep82024.0.0 debugpy2024.4.0 isort2023.10.1 pylint2023.10.1 python2024.4.1 vscode-pylance2024.4.1 jupyter2024.4.0 jupyter-keymap1.1.2 jupyter-renderers1.0.17 tensorboard2023.10. vscode-jupyter-cell-tags0.1.9 vscode-jupyter-powertoys0.1.1 vscode-jupyter-slideshow0.1.6 remote-wsl0.88.2 cpptools1.20.3 cpptools-extension-pack1.3.0 hexeditor1.10.0 vsliveshare1.0.5918 autodocstring0.6.1 advanced-new-file1.2.2 material-icon-theme5.1.0 r-debugger0.5.4 r2.8.2 markdown-preview-enhanced0.8.13 errorlens3.17.0 intellicode-api-usage-examples0.2.8 vscodeintellicode1.3.1 markdown-all-in-one3.6.2 material-theme3.17.2 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
can you share your Also are you using Windows PowerShell () or pwsh 6+? Could you get the version of that via ?
Same issue for us using bash 5.0.17(1) so might not be pwsh dependent. Terminal prompt now not showing special characters on latest insiders update 1.90.0 e.g. x1b[01x3b34m~/code/project1x1b[00m (main))
actually got a fix in for bash in
Where can i get the The powershell version is: 7.4.2
I have the same exact problem, and the following suggestion finally fixed it on my end:
I am not sure I understand what the comment is trying to say. I am supposed to replace my with the one from commit and 
I agree, the instructions could have been clearer. The commit selection does seem a bit random, but what I did was clicking 'Browse files' on the commit and found the from that repository version. Here's a link to get there directly: 
It was pushed to the official build. I'm having this issue and I dont rememeber ever joining any kind of insider program.
Related on Stack Overflow:
thank you so much! This was what fixed it for me after trying everything yesterday. Some more clarity or directions from the dev side would have been nice, but now its back to normal after all!
Thanks replacing the shellintegration.ps1 from this commit fixed it for me. The location of the file is:
In addition to the semi-permanent solution above, I have found that you can simply type (for PowerShell 7) or (for PowerShell 5) in the terminal, and it will launch a brand new, yet identical terminal in the current working directory - but without the gibberish.
FYI, I see this in the regular code branch Version: 1.90.0 (user setup) Commit: Date: 2024-06-04T19:33:54.889Z Electron: 29.4.0 ElectronBuildId: Chromium: 122.0.6261.156 20.9.0 V8: 12.2.281.27-electron.0 OS: Windows_NT x64 10.0. !
To verify: oh-my-posh a PowerShell terminal oh-my-posh, you should not see the escapes as shown above
Same issue here. oh-my-posh, powershell, issue only with vscode, windows term looks as intended. !
This should be fixed in v1.90.2 which was just released
Can confirm as fixed. Thanks for the work!
confirm as fixed and work well without needing to disable setting! !
Looks good again!
Looks good to me too!!
This morning, I updated my VS Code, activated the setting, but I am still experiencing the same issue (especially when I try to clear the terminal with CTRL+L). I am using Windows 10 Pro for Workstations x64, AMD Ryzen 5 5600X 6-Core Processor, and Nvidia 720 GPU. !
Still same issue
what shell/prompt is that?
It's the PowerShell from the Microsoft Store. Special characters appear when I press Ctrl + L to clear the terminal. I also have the same problem in Git Bash, but it happens when I execute a command. In both cases, I am using Oh My Posh. !
I was also having a related? problem with PowerShell integration since the 1.90 release. The recent 1.90.2 update has changed the outcome a little, but not fixed it. I get output like the below when I open a new pwsh terminal, and often the terminal stops responding after executing a command or two. I have this PowerShell profile. I thought any of PSFzf, zoxide, or the encoding settings could be the culprit, so I tried removing each one. Oddly, removing any combination of them doesn't fix the problem, but completely blanking out the file fixes it (second image below). It all worked fine in vscode prior to 1.90. ! !
you have the experimental suggest setting enabled, disabling that will fix it. What version of PowerShell is that you're using? Currently in Insiders we force suggest to be disabled on Windows PowerShell (5), but if you're experiencing it in a latter version maybe we need to disable it in older versions of Windows too.
Are you referring to a different setting? (I was wrong; see below.) (Not sure if it's relevant, but PowerShell suggestions do work in Windows Terminal.) ! !
OOPS, I did have an old version of that setting in my , and removing it did indeed fix the problem. Thank you.
Is there a separate issue tracking this behavior with ? I do not use OhMyPosh and am still getting the same behavior with VSCode . ! The workaround of invoking from within the VSCode terminal does work.

Related discussion:
text: function Global:__VSCode-Escape-Value([string]$value) { # NOTE: In PowerShell v6.1+, this can be written `$value -replace '…', { … }` instead of `[regex]::Replace`. # Replace any non-alphanumeric characters. <del> [regex]::Replace($value, "[$([char]0x1b)n;]", { param($match) </del> <ins> [regex]::Replace($value, "[$([char]0x00)-$([char]0x1f)n;]", { param($match) </ins> # Encode the (ascii) matches as `x<hex>` -Join ( [System.Text.Encoding]::UTF8.GetBytes($match.Value) | ForEach-Object { 'x{0:x2}' -f $_ }