visual studio code ошибка powershell код выхода 4294901760

The terminal process «C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe» terminated with exit code: 4294901760. #113440

Comments

ieremciuc commented Dec 26, 2020

I tried everything from microsoft github and stack overflow it is now worse help me!

The text was updated successfully, but these errors were encountered:

We are unable to convert the task to an issue at this time. Please try again.

The issue was successfully created but we are unable to update the comment at this time.

vscodebot bot commented Dec 26, 2020

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

meganrogge commented Dec 27, 2020

It looks like your report is missing some important information, See this wiki page for more info on how to report actionable terminal issues.
/label «needs more info» integrated-terminal

ieremciuc commented Dec 28, 2020

hsmello commented Jan 24, 2021

hey, did you manage to make it work?

if so, how did you do it?

if not, try these below in cmd as admin, maybe it will help. might take a while

Sfc /scannow
DISM.exe /Online /Cleanup-image /Scanhealth
Dism.exe /Online /Cleanup-Image /CheckHealth
DISM.exe /Online /Cleanup-image /Restorehealth
Dism.exe /Online /Cleanup-Image /startComponentCleanup

i have the same issue. i found the above in a website and it seems to have worked for more people, but not for me

Источник

The terminal process terminated with exit code: 4294901760 #100366

Comments

antonioborondo commented Jun 17, 2020

Steps to Reproduce:

Does this issue occur when all extensions are disabled?: Yes

Launch Visual Studio Code with the following command:

Shows the following message when the notification error appears:

The text was updated successfully, but these errors were encountered:

We are unable to convert the task to an issue at this time. Please try again.

The issue was successfully created but we are unable to update the comment at this time.

antonioborondo commented Jun 17, 2020

If you’re on Windows 10 1809 (build 17763) or below, the issue is related to the legacy «winpty» backend. Upgrading to Windows 1903 (build 18362) will move you onto the new «conpty» backend that is built by Microsoft and could fix your problem.

It might be related.

Tyriar commented Jun 17, 2020

@antonioborondo yep you would be on the old backend that had a bunch of issues that we couldn’t fix, it could also be anti-virus software blocking it so you could try excluding the paths called out in https://code.visualstudio.com/docs/supporting/troubleshoot-terminal-launch#_error-connectnamedpipe-failed-windows-error-232

Also, I’m really glad you found the troubleshooting page I just created 😄

Shoeb456 commented Aug 16, 2021

Источник

Terminal process exit code 4294901760 #114830

Comments

hsmello commented Jan 23, 2021

Terminal does not open
message:
The terminal process «C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe» terminated with exit code: 4294901760.

The text was updated successfully, but these errors were encountered:

We are unable to convert the task to an issue at this time. Please try again.

The issue was successfully created but we are unable to update the comment at this time.

vscodebot bot commented Jan 23, 2021

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

meganrogge commented Jan 25, 2021

It looks like your report is missing some important information, See this wiki page for more info on how to report actionable terminal issues.
/label «needs more info» integrated-terminal

hsmello commented Jan 25, 2021 •

when i open the terminal it stays open for a sec and this message appears:

after closing i get this the msg

VS Code version 1.52.1 and i am on a windows 64-bit OS

meganrogge commented Jan 26, 2021

Thanks for the info.

In the settings UI, what do you have the cwd set to?

hsmello commented Jan 26, 2021

meganrogge commented Jan 27, 2021 •

Can you pls paste the output of trace logging, as described below?

hsmello commented Jan 27, 2021

also a prit of a part of it that might be easier to read

meganrogge commented Jan 27, 2021 •

Thanks for that info. I think this is a duplicate of this issue. #100366 (comment)

The other thing you can try is downloading Powershell 7 and then reloading VS Code. It should pick up on that installation.

Источник

Troubleshoot Terminal launch failures

If you are new to using the Visual Studio Code Integrated Terminal, you can learn more in the Integrated Terminal user guide. There you can read how to configure the terminal, as well as review answers to common questions.

Below are specific troubleshooting steps, if the user guide hasn’t helped you diagnose the launch failure. The troubleshooting steps, such as checking your settings and enabling logging, apply to all platforms that support VS Code; macOS, Linux, and Windows.

Note: If you’re on Windows, review the common issues on Windows section first.

Troubleshooting steps

To troubleshoot Integrated Terminal launch failures in Visual Studio Code, follow these steps to diagnose issues:

Check your user settings. Review these terminal.integrated settings that could affect the launch:

You can review settings in the Settings editor (File > Preferences > Settings) and search for specific settings by the setting ID.

A quick way to check if you have changed settings that you might not be aware of, is to use the @modified filter in the Settings editor.

Most Integrated Terminal settings will need to be modified directly in your user settings.json JSON file. You can open settings.json via the Edit in settings.json link in the Settings editor or with the Preferences: Open Settings (JSON) command from the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ).

Test your shell directly. Try running your designated integrated terminal shell outside VS Code from an external terminal or command prompt. Some terminal launch failures may be due to your shell installation and are not specific to VS Code. The exit codes displayed come from the shell and you may be able to diagnose shell issues by searching on the internet for the specific shell and exit code.

Use the most recent version of VS Code. Each VS Code monthly release has many updates and fixes and may include integrated terminal improvements. You can check your VS Code version via Help > About (on macOS Code > About Visual Studio Code). To find the latest version of VS Code, go to the VS Code release notes. You may also want to check that you have installed the latest version of your shell.

Enable trace logging. You can enable trace logging and capture a log when launching the terminal. Logging often reveals what is wrong as all arguments used to create the terminal process/pty are recorded. Bad shell names, arguments, or environment variables can cause the terminal to not launch. Keep this log for later if your problem isn’t solved.

Additional troubleshooting steps

If none of these steps helped solve the issue, you can also try:

Exit codes

The exit codes displayed in the terminal launch failure notification are returned from the shell process and are not generated by VS Code. There are many available shells that can be used in the terminal and hundreds of possible exit codes. Try searching on the internet for your specific shell and exit code (for example, «PowerShell 4294901760») and you may find specific suggestions or known issues related to your terminal launch failure.

Common issues on Windows

Make sure compatibility mode is disabled

When upgrading to Windows 10, some apps may have compatibility mode turned on automatically. When this happens with VS Code, the terminal breaks as it does some low level things to enable the emulation it uses. You can check and disable compatibility mode by right-clicking on the VS Code executable and selecting properties, then uncheck the Run this program in compatibility mode option in the compatibility tab.

The terminal exited with code 1 on Windows 10 (with WSL as the default shell)

This can happen if Windows Subsystem for Linux (WSL) is not set up with a valid default Linux distribution.

Note: ‘docker-desktop-data’ is not a valid distribution.

The terminal not working when running the 32-bit Windows client on 64-bit Windows?

The easy fix for this issue is to use the 64-bit version. If you must use the 32-bit version, you need to use the sysnative path when configuring your shell path instead of System32. Adding this setting should fix the issue:

A native exception occurred

Typically this error occurs due to anti-virus software intercepting and blocking the winpty/conpty components from creating the terminal process. To work around this error, you can exclude the following file from your anti-virus scanning:

Reporting this issue to the Anti-virus team can also help stamp out the issue all together.

Источник

PowerShell won’t start in VSCode #103486

Comments

devedse commented Jul 28, 2020

For some reason I can’t use PowerShell inside vscode anymore. It just says «Loading the PowerShell extension is taking longer than expected». I’ve tried to reinstall the PowerShell extension and also VSCode. But none of these steps fixed it.

The issue happens whenever I open VSCode and try to do anything with a PowerShell file. (E.g. run it)

Anyway, when I first start VSCode this error shows up:

Here’s the files mentioned in C:\Users\devedse\.vscode\extensions\ms-vscode.powershell-2020.6.0\logs\1593015143-28af1fd9-3db7-4b8f-b7e9-83453c652a221593015141446\

StartEditorServices.log: (It’s empty)

I looked at similar issues too, but found no resolution:
PowerShell/vscode-powershell#1673

VS Code version: Code 1.47.2 (17299e4, 2020-07-15T18:22:06.216Z)
OS version: Windows_NT x64 10.0.18363

System Info

Extensions (12)

The text was updated successfully, but these errors were encountered:

We are unable to convert the task to an issue at this time. Please try again.

The issue was successfully created but we are unable to update the comment at this time.

Источник