This Code Is Not Recognized Please Try Again Haute Cash

Troubleshoot Final launch failures

To get-go, we'd like to say we're pitiful that yous're here reading this document instead of having a expert time using the Integrated Terminal in Visual Studio Code. The VS Code team works hard to make the concluding experience as seamless equally possible just in some cases, at that place are bug with shell or terminal configurations that the VS Lawmaking editor can't work effectually.

After having worked with hundreds of developers to diagnose their last launch failures, the VS Lawmaking team has put together this topic with the advice and troubleshooting tips that take helped people in the past. We hope yous'll detect an answer here for your shell or last issue and tin get rapidly back to work.

Integrated Concluding user guide

If you are new to using the VS Lawmaking Integrated Concluding, you tin can acquire more in the Integrated Terminal user guide. There you lot can read how to configure the last, as well equally review answers to common questions.

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

Annotation: If yous're on Windows, you may desire to review the common issues on Windows department offset.

Troubleshooting steps

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

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

   • terminal.integrated.shell.{platform} - The path of the shell that the terminal uses.
   • terminal.integrated.shellArgs.{platform} - The command-line arguments when launching the shell process.
   • concluding.integrated.cwd - The electric current working directory (cwd) for the shell procedure.
   • final.integrated.env.{platform} - Environment variables that volition exist added to the shell process.
   • concluding.integrated.inheritEnv - Whether new shells should inherit their environment from VS Code.
   • terminal.integrated.automationShell.{platform} - Beat out path for automation-related terminal usage like tasks and debug.
   • concluding.integrated.splitCwd - Controls the current working directory a split up concluding starts with.
   • terminal.integrated.windowsEnableConpty - Whether to use ConPTY for Windows terminal process advice.

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

   

   A quick mode to check if y'all have changed settings that yous might not be aware of, is to utilise the @modified filter in the Settings editor.

   

   Most Integrated Terminal settings will need to exist 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 Control Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P)).

   

2. Test your trounce directly. Try running your designated integrated last crush outside VS Code from an external terminal or command prompt. Some terminal launch failures may be due to your trounce installation and are not specific to VS Code. The go out codes displayed come from the beat and you may exist able to diagnose shell issues by searching on the net for the specific shell and exit lawmaking.

3. Utilise the most contempo 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 Assist > Almost (on macOS Code > About Visual Studio Code). To discover the latest version of VS Lawmaking, go to the VS Lawmaking release notes. You may also desire to check that you take installed the latest version of your trounce.

4. Use the most contempo version of your shell. If your vanquish is installed carve up from your platform, effort installing the latest available version of the trounce. The same advice applies if you are on an older build of your operating system. For example, some older versions of Windows 10 did not work well with the VS Code last.

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

Boosted troubleshooting steps

If none of these steps helped solve the result, yous tin also endeavour:

• Inquire most it on Stack Overflow, frequently launch problems are related to environment setup and non a problem with VS Lawmaking.
• If the terminal is being launched from an extension, study the issue to the extension by opening the issue reporter (Help > Report Issue) and fix File On = "An Extension"
• If you believe information technology to be a bug with VS Code, report the upshot using the issue reporter (Assistance > Report Issue). The issue reporter will autofill relevant information, see Creating great terminal bug for what else to include in the written report.
• If yous're on Windows 10 1809 (build 17763) or beneath, the issue is related to the legacy "winpty" backend. Upgrading to Windows 1903 (build 18362) will move you lot onto the new "conpty" backend that is built by Microsoft and could fix your trouble.

Exit codes

The exit codes displayed in the last launch failure notification are returned from the beat process and are not generated past VS Code. At that place are many bachelor shells that tin can be used in the final and hundreds of possible go out codes.

• Try searching on the internet for your specific trounce and exit code (for instance, "PowerShell 4294901760") and y'all may detect specific suggestions or known issues related to your terminal launch failure.
• Endeavour searching in your shell'due south issue repository. For case, if you are having trouble with WSL, you might observe a workaround searching for your error code in the open or resolved bug at https://github.com/microsoft/WSL/issues.

Mutual problems on Windows

Brand sure compatibility mode is disabled

When upgrading to Windows ten, some apps may have compatibility style turned on automatically. When this happens with VS Code, the concluding breaks as it does some low level things to enable the emulation it uses. You lot can bank check and disable compatibility mode past right-clicking on the VS Code executable and selecting backdrop, and 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 non ready with a valid default Linux distribution.

Annotation: 'docker-desktop-data' is not a valid distribution.

• Open up PowerShell and enter wslconfig.exe /l to confirm WSL is installed correctly and list the currently available Linux distributions within your arrangement. Confirm a valid distribution has (default) side by side to it.
• To change the default distribution, enter wslconfig.exe /setdefault "distributionNameAsShownInList"

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

The like shooting fish in a barrel fix for this issue is to use the 64-bit version. If you lot must use the 32-bit version, yous need to use the sysnative path when configuring your shell path instead of System32. Adding this setting should fix the issue:

                      "final.integrated.beat.windows"            :                        "C:            \\            Windows            \\            Sysnative            \\            cmd.exe"                  

A native exception occurred

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

          {install_path}\resources\app\node_modules.asar.unpacked\node-pty\build\Release\winpty.dll {install_path}\resources\app\node_modules.asar.unpacked\node-pty\build\Release\winpty-agent.exe {install_path}\resources\app\node_modules.asar.unpacked\node-pty\build\Release\conpty.node {install_path}\resource\app\node_modules.asar.unpacked\node-pty\build\Release\conpty_console_list.node                  

Reporting this issue to the Anti-virus squad tin too help stamp out the outcome all together.

Terminal exits with code 3221225786 (or similar)

This can happen when you lot take legacy console manner enabled in conhost's backdrop. To modify this, open cmd.exe from the showtime menu, correct-click the championship bar, become to Properties and nether the Options tab, uncheck Use legacy console.

Side by side steps

• Integrated Terminal user guide - Larn more well-nigh general terminal utilize and configuration.

five/5/2022

crunkuncerew.blogspot.com

Source: https://code.visualstudio.com/docs/supporting/troubleshoot-terminal-launch

Share this post