Change:
// Run Extension Host as fork of current process const args = ['--type=extensionHost', `--uriTransformerPath=${uriTransformerPath}`]; const useHostProxy = this._environmentService.args['use-host-proxy']; <del> if (useHostProxy) { args.push(`--useHostProxy`); } </del> <ins> args.push(`--useHostProxy=${useHostProxy ? 'true' : 'false'}`); </ins> this._extensionHostProcess = cp.fork(FileAccess.asFileUri('bootstrap-fork', require).fsPath, args, opts); const pid = this._extensionHostProcess.pid; this._log(`<${pid}> Launched Extension Host Process.`);

Discussion:
Issue Type: <bBug</bAttempting to build my dev container behind a proxy failed with the latest update to 1.64. This appears to be agnostic to the container used to build and is a widespread issue across the team. 63 worked appropriately. I've attached the output log. VS Code version: Code 1.64.0 (, 2022-02-03T04:22:20.678Z) OS version: WindowsNT x64 10.0.

Restricted Mode: No Connection to 'dev-container+7b22686f737450617468223a22633a5c5c55736572735c5c786a34735c5c446f63756d656e74735c5c726574656e74696f6e2d6d6f64656c696e672d656e7669726f6e6d656e74222c2273657474696e6773223a7b22636f6e74657874223a226465736b746f702d6c696e7578227d7d' could not be established <details<summarySystem Info</summary Connection to 'dev-container+7b22686f737450617468223a22633a5c5c55736572735c5c786a34735c5c446f63756d656e74735c5c726574656e74696f6e2d6d6f64656c696e672d656e7669726f6e6d656e74222c2273657474696e6773223a7b22636f6e74657874223a226465736b746f702d6c696e7578227d7d' could not be established </details<details<summaryExtensions (33)</summaryExtensionVersion ------ terraform0.2.2 sas-syntax1.0.8 better-comments2.1.0 git-temporal-vscode1.0.0 vscode-coverage-highlighter1.0.3 better-toml0.3.2 gitlens11.7.0 gitlab-workflow3.40.2 vscode-test-explorer2.21.1 r2.3.6 mysql-syntax1.3.1 vscode-python-test-adapter0.7.0 vscode-docker1.19.0 data-workspace-vscode0.1.1 mssql1.12.0 sql-database-projects-vscode0.14.1 anaconda-extension-pack1.0.1 python2022.0. vscode-pylance2022.2.0 jupyter2022.1.

jupyter-keymap1.0.0 jupyter-renderers1.0.6 remote-containers0.217.1 remote-ssh0.70.0 remote-ssh-edit0.70.0 powershell2021.12.0 test-adapter-converter0.1.5 vsliveshare1.0.5330 vscode-data-preview2.3.0 vscode-commons0.0.6 vscode-yaml1.4.0 pdf1.2.0 vscodeintellicode1.2.16 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
I can confirm that the proxy setting is not used in the 1.64 version, had to downgrade to 1.63 and disable updates.
Just had a filesave fail where Prettier had crashed. Restarted VSCode and could see a new version being installed via Windows Terminal. Now Code won't load at all - 90% of my client projects are in Docker.
Any chance we can release this ASAP? This breaks VS Code for a multitude of developers working behind corporate proxies. Also can you contribute a test for that change? Asking because I had a run-in with different issues related to proxy and remote containers.
Yes, a fix will be in 1.64.2 coming out in a few days:
Those affected using Remote-Containers could give the latest pre-release of Remote-Containers (0.219.0) a try. That falls back to downloading the server via Electron which is not affected by this bug. (Coincidental timing with this issue.) Switch to the pre-release version if you haven't: <img width="777" alt="image" src="https://user-"
Also fixed by in today's Insiders build (just verified):
I confirm it works. Thanks and
The backport to 1.64 is
Verified in the 1.64.2 candidate build ().
Can confirm that 1.64.2 fixed the issue for me. Thank you