Change:
} }); <del> suite('pwsh', () => { </del> <ins> // These tests are only expected to work on Windows 10 build 18309 and above (getWindowsBuildNumber() < 18309 ? suite.skip : suite)('pwsh', () => { </ins> const expectedPs1 = process.platform === 'win32' ? `try { . "${repoRoot}outvsworkbenchcontribterminalbrowsermediashellIntegration.ps1" } catch {}` : `. "${repoRoot}/out/vs/workbench/contrib/terminal/browser/media/shellIntegration.ps1"`;

Discussion:
Type: <bBug</bHi, after recent VSCode update now when I open the terminal via workspace (clicking "Open in integrated terminal") - it shows some weird line like "←]633;P;IsWindows=←]633;A←]633;P;Cwd=C:x5cUsersx5csergex5cDesktopx5cProjectsx5cProjectsNamex5cProjectsNamex5cfrontendPS C:UserssergeDesktopProjectsProjectsNameProjectsNamefrontend←]633;" and then computer makes two sounds of the error. It have never happened before and everything was working fine - VSCode would open a terminal with the correct path without errors. I am pretty sure your wonderful team will fix this little bug. Thank you for making such an amazing product! VS Code version: Code 1.75.0 (, 2023-02-01T15:23:45.584Z) OS version: WindowsNT x64 6.3.9600 Modes: Sandboxed: No <details<summarySystem Info</summary </details<details<summaryExtensions (14)</summaryExtensionVersion ------ formatter-pug0.0.1 es7-react-js-snippets4.4.3 prettier-vscode9.10.4 auto-rename-tag0.1.10 code-beautifier2.3.3 vetur0.36.1 webgl-glsl-editor1.3.3 vscode-xml0.24.0 LiveServer5.7.9 markdown-preview-enhanced0.6.7 vscode-scss-formatter2.4.4 shader1.1.5 autoimport1.5.4 volar1.0.24 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
i have same error
Cannot repro on mac or windows
Same problem, please suggest some solution for it or give some information like is there a fault in this version or did i install something fishy.
Are you on Windows 7?
←]633;P;IsWindows=←]633;A←]633;P;Cwd=C:x5c Getting the same error after upgrade...? Help.

Windows 8.1 (yeah I know I need to upgrade,... We've got computers 7, 8, 10 & 11 here) ... OK after looking into this a little more I believe my issue was my need to upgrade this terminal - I just don't want the down time at the moment... Anyways ConPTY requires Windows 10 (build +) therefor fishing around in my terminal settings I set it to false. "terminal.integrated.windowsEnableConpty": false Hope this helps somebody, cheers.
For Windows 7 we don't support it anymore, for other versions or 8 and 10 (below build ) I see we're missing a check here to turn off shell integration when winpty is forced: The fix will behave essentially the same as setting so it's a good workaround in the meantime.
beep sound comes and still not working for windows 8.1, please helppp!
There was a work around for we had for this issue but I believe they have updated the code since then to address this issue. You may have a different problem...?
yeah for me terminal is still not working in vscode, i have windows 8.1 and i have infact installed latest version of vscode and the problem still exist.
exact problem is when i open terminal in vscode it just goes blank nothing starts just a black portion and a few beeping sound at start, the problems section is working perfectly but i have to use cmd for my terminal needs.
You know what's weird is I had taken the work around out of my file to see if the update had taken place and everything has been fine for a few days. Now after seeing your response and pulling up the terminal, I'm having the issue again. Maybe another update brought back the issue. Anyways no problem, made the change back to my settings and the problem is fixed. Your issue might be different idk. Have you tried adding, "terminal.integrated.windowsEnableConpty": false to your file? This thread seemed to be centered around an issue with forcing ConPTY on older systems. Try the work around out and if that doesn't fix it start a new thread since this one has been "closed".
Friendly ping! Looks like this issue requires some further steps to be verified. Please provide us with the steps necessary to verify this issue.
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of !

you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
Problem still exists on Windows 2012R2 Version: 1.76.0-insider (system setup) Commit: Date: 2023-02-24T21:55:13.530Z Electron: 19.1.10 Chromium: 102.0.5005.196 16.14.2 V8: 10.2.154.26-electron.0 OS: Windows_NT x64 6.3.9600 Sandboxed: Yes
I'm not sure why it wouldn't be fixed for you, but it looks like support for that ended October 9, 2018 If it's the same problem you can workaround the issue by setting
Removing bug as we don't need to verify