Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[resolved] got bad result from install script #5693

Closed
fourdim opened this issue Oct 8, 2021 · 0 comments
Closed

[resolved] got bad result from install script #5693

fourdim opened this issue Oct 8, 2021 · 0 comments

Comments

@fourdim
Copy link

fourdim commented Oct 8, 2021

  • VSCode Version: 1.61.0
  • Local OS Version: Windows 10
  • Remote OS Version: Linux (include centos ubuntu debian)
  • Remote Extension/Connection Type: SSH
  • Logs:
The terminal process "C:\Windows\System32\cmd.exe /c (type "C:\Users\***\AppData\Local\Temp\vscode-linux-multi-line-command-10.26.11.98-806610016.sh" | ssh -T -D 2530 "10.26.11.98" bash) & exit /b 0" terminated with exit code: 1.

Running script with connection command: ssh -T -D 2530 "10.26.11.98" bash
Terminal shell path: C:\Windows\System32\cmd.exe
"install" terminal command done
Install terminal quit with output: 
Resolver error: Error: Got bad result from install script
	at Function.Create (c:\Users\***\.vscode\extensions\ms-vscode-remote.remote-ssh-0.65.8\out\extension.js:1:397041)
	at Object.t.tryInstall (c:\Users\***\.vscode\extensions\ms-vscode-remote.remote-ssh-0.65.8\out\extension.js:1:489077)
	at processTicksAndRejections (internal/process/task_queues.js:93:5)
	at async c:\Users\***\.vscode\extensions\ms-vscode-remote.remote-ssh-0.65.8\out\extension.js:1:453110
	at async Object.t.withShowDetailsEvent (c:\Users\***\.vscode\extensions\ms-vscode-remote.remote-ssh-0.65.8\out\extension.js:1:456460)
	at async Object.t.resolve (c:\Users\***\.vscode\extensions\ms-vscode-remote.remote-ssh-0.65.8\out\extension.js:1:454189)
	at async c:\Users\***\.vscode\extensions\ms-vscode-remote.remote-ssh-0.65.8\out\extension.js:1:526942
  • Solution

This issue has been resolved, and I'm here to tell other users my solution.

After running the script mannually, I found that I cannot even open cmd.exe.

It appears that cmd.exe crashed and it results in this bug.

After searching, I found that I have an 'AutoRun' command set in the registry.

The registry values are:

HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\AutoRun
HKEY_CURRENT_USER\Software\Microsoft\Command Processor\AutoRun

Check both. By default, neither should exist. You may wish to fix the command strings in yours, or even delete them entirely.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant