VS Code will not install (stuck on preparing to install page)

[bevanm8]

Type: Bug

How to reproduce:
Run the windows x64 installer
Click through the standard pages
Click install
The installer then freezes.

I know it's frozen because I can't click anything, or drag it, I get the "Ding" noise as though there is something else open that I need to accept, but nothing is visible. This happens with the User and System builds, and I've tried the insiders build with the same result.

When I go to the task view option in Windows I see there are 2 items named Setup. When I look in Task Manager there are 3: "Console Window Host", Setup/Uninstall (32bit), Windows Powershell (32bit) - This is running the 64bit installer.

Interestingly if I kill just the "Windows Powershell" process the installer will continue on. Seems that there is an initial script that is getting stuck which is causing the installer to freeze.

I found an almost identical issue that was raised in 2018, which interestingly was listed as "Wont fix". Link Here:
#43949

Running Win 11 Pro

Let me know if I can provide any further information.

Screenshots:

VS Code version: Code 1.83.1 (f1b07bd, 2023-10-10T23:48:05.904Z)
OS version: Windows_NT x64 10.0.22631
Modes:

Extensions (11)

Extension	Author (truncated)	Version
op-vscode	1Pa	1.0.4
prettier-vscode	esb	10.1.0
code-runner	for	0.12.1
homey-apps-extension	hom	0.10.0
vscode-docker	ms-	1.27.0
vscode-kubernetes-tools	ms-	1.3.15
isort	ms-	2023.10.1
python	ms-	2023.18.0
remote-wsl	ms-	0.81.8
powershell	ms-	2023.8.0
vscode-yaml	red	1.14.0

[abraxas86]

Good call on the ending the powershell task. That kicked my installer into gear, too. Thanks!

[JohnR-LoD]

Ending the PowerShell task also worked for me.

[CyMad7001]

This maybe caused by a powershell profile that maybe needs some user input, a solution could be for the installer to execute that powershell without loading profiles e.g. powershell -noprofile -command ...

You could temporarily execute the following in another powershell session until the installer has been fixed/updated:

    do {
        $installerPIDs=$(Get-WmiObject -Class Win32_Process |
            Where-Object { $_.CommandLine -match ('vscode(user|machine|system|)(setup|install)') } |
            Select-Object -ExpandProperty ProcessId)
        if ($null -ne $installerPIDs) {
            $filter = "name = 'Powershell.exe' AND (parentProcessId = $($installerPIDs -join ' OR parentProcessId = '))"
            Get-WmiObject -Class Win32_Process -Filter $filter |
                ForEach-Object { Stop-Process -Id $_.ProcessId -Force }
        }
    } while ( $null -ne $installerPIDs )

[rgehrsitz]

That script worked! I started the install, let it hang, then ran the script in PowerShell. The installation immediately proceeded.

[gdeubner-trimble]

killing the script fixed the issue for me too

[site-speed]

This maybe caused by a powershell profile that maybe needs some user input, a solution could be for the installer to execute that powershell without loading profiles e.g. powershell -noprofile -command ...

You could temporarily execute the following in another powershell session until the installer has been fixed/updated:

    do {
        $installerPIDs=$(Get-WmiObject -Class Win32_Process |
            Where-Object { $_.CommandLine -match ('vscode(user|machine|system|)(setup|install)') } |
            Select-Object -ExpandProperty ProcessId)
        if ($null -ne $installerPIDs) {
            $filter = "name = 'Powershell.exe' AND (parentProcessId = $($installerPIDs -join ' OR parentProcessId = '))"
            Get-WmiObject -Class Win32_Process -Filter $filter |
                ForEach-Object { Stop-Process -Id $_.ProcessId -Force }
        }
    } while ( $null -ne $installerPIDs )

I have this issue and at the moment my PowerShell profile, (due to an unrelated issue) is definitely prompting for user input

agree that it may make sense for the installer (also installers e.g. for .NET updates that run when VS Code is up and running) to use -noprofile so that custom profiles can't interfere with correct operation of the installer(s)

[tfitzpatrickSymplr]

Killing that script still working on 2025... thanks!

[Maven-Rachit]

Works for me too.
Try to look for the powershell tab in the background tasks of Task manager and end it from there.

[NicoKiaru]

Works for me as well, and I confirm @Maven-Rachit comment: you need to look for the powershell process and kill it
(Note: the same issue exists for the Cursor installer, and can be fixed the same way)

[tejasaudichya]

It Works!! Thanks