
Steps to Reproduce:
@VitorLuizC can you paste in some of the problem characters? Also do you have any terminal-specific settings set in your settings.json?
My folder's name is "Pa莽oca", so the "莽" is the only special character, and no I didn't have any terminal-specific settings in my settings.json.

I've tried to open integrated terminal in another folder without special characters("Pacoca") and it worked.
Seems fine on stable and insiders on Linux:

Perhaps it's only happening on Windows?
I don't know if it matters but that folder is inside my OneDrive folder.

After a new test i've checked that doesn't matter.
Chinese folder or Japanese folder so does on Windows 10锛侊紒
Must be a windows thing, I'll try have a look at this for v1.3
Can confirm it effects on a new installation of v1.2.1 and on windows.
Folders causing this for me is when opened as "root" and containing swedish letters (氓盲枚). Also if folders above "root" contains special characters.
I had a look at this and it appears to be an upstream issue, moving to backlog.
Can confirm this is happening for me as well (just updated to 1.2.1 and currently on Windows 10). Behaviour is exactly as shown in VitorLuizC's image, except that I have no special characters in my path, and in fact the problem still occurs with no folders or files open and just the initial untitled document displayed.
I recently upgraded to Windows 10 from Windows 7 and the problem was not present while on Windows 7.
For me it happens for russian characters, I have "小械褉谐械泄" in path on Win 10
Confirm for polish letters in path on Windows 10.
+1 for Chinese
+1 for Russian on Windows 10. It doesn't matter are there any special characters in path for opened by VSCode folder. Having them in Windows username will be enough to get integrated-terminal crashing.
@Tyriar Chinese folder will show the following errors on Win10


Any news?
I've already opened an issue to this exact same problem 3 months ago. It was closed, because for Tyriar everything seemed to work fine. I've tried VScode on 3 different computers, with both powerShell and cmdprompt, with default settings, and it never worked. In fact, I've never seen a Windows computer that had integrated terminal working. I think I'm switching back to an IDE that can handle basic stuff.
@ugros many people are experiencing this issue as you can see from the linked issues. This issue is actually on the integrated terminal backlog (#9959) and is one of the major bugs I'll be looking at in September.
Keep in mind we're quite a small team with a lot of responsibilities, there is only so much we can do each release. Also I can't see your original issue? https://github.com/Microsoft/vscode/issues/created_by/ugros
@Tyriar I've been using different github account.
https://github.com/Microsoft/vscode/issues/7440
By the way, is there any workaround or any fix I can do with my computer, that would fix this issue in the meanwhile? My workflow suffers a lot by this issue.
Thanks a lot
Ah, I think the EPIPE thing was something else that stopped occurring in 1.2 or 1.3.
The only workarounds I can think of are to rename/relocate the open folder. I'll hopefully be checking this out sometime next week so it may come through in the Insiders build then.
The only workarounds I can think of are to rename/relocate the open folder.
What do you mean by this? Could you please evaluate? Thanks
I mean if you're working out of C:\Users\<special chars>\dev you can move your dev dir to C:\dev to get around this.
I was able to fix this for myself by changing the setting terminal.integrated.shell.windows from
"C:\\WINDOWS\\system32\\cmd.exe" (the default I assume, at least I hadn't changed it myself)
to
"C:\\Windows\\sysnative\\cmd.exe" (which the comment above the setting says is the 64bit version)
Hope that's helpful with fixing this issue. I'll also point out again that I experienced this issue without a project folder opened at all, i.e. with only an empty unsaved document opened, so the presence of special chars didn't seem to be the cause of the issue on my system.
@joseph-iussa double checked and setting to the 64-bit cmd doesn't fix this issue. Not sure what the problem was with opening the terminal with no open folder, doesn't reproduce on my machine.
Not only special chars, i think that are all unicode characters.
My user folder is 'Alfonso Andr茅s'.
Windows 10.
I encountered this problem today. I think I found the culprit. The vscode uses pty.js to open the terminal. https://github.com/Microsoft/vscode/blob/a6c845baf7fed4a186e3b744c5c14c0be53494fe/src/vs/workbench/parts/terminal/electron-browser/terminalProcess.js (line: 30)
And on the pty.js project I found the following open issue: https://github.com/chjj/pty.js/issues/173
@Dzienny yes it could be either pty.js or the dated winpty version it uses.
I've created a pull request with the fix here: chjj/pty.js#176
Fixed thanks to @the-ress's pull request! You can try this out in the Insiders build tomorrow or in stable v1.7.
I am facing this error on Linux Solus. No special character on file dir. When I try to compile code (alt+enter) F# Interactive console appears for a moment then I get this error message.
@srcnalt make sure you're on the latest version, if you still experience the issue please file a new one via Help > Report Issues :smiley:
I have the same issue: The terminal process command FsiAnyCpu.exe --fsi-server-input-codepage:65001 failed to launch (exit code: 3221225477)
My path to the folder is without any accents or special characters.
|Extension|Author|Version|
|---|---|---|
|Ionide-fsharp|Ionide|2.23.9|;
Exact same problem here with Ionide on windows 10. Have tried on windows 7 and it works.
Do not have any accents or special chars.
Sorry to bump, but I'm not sure if this is related.
When I run rollup -w I get the "The terminal process terminated with exit code" error, but the error code is 259, strangely. Running it in git bash outside of VSCode works fine, but the integrated terminal crashes without fail.
Most helpful comment
Chinese folder or Japanese folder so does on Windows 10锛侊紒