vscodium icon indicating copy to clipboard operation
vscodium copied to clipboard

VSCodium updates not working

Open 0x416c69 opened this issue 1 year ago • 9 comments

Describe the bug I press Install update and it gets stuck (i.e. updates don't happen, it's like it's failing somewhere silently)

Please confirm that this problem is VSCodium-specific

  • [x] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

To Reproduce Steps to reproduce the behavior:

  1. Press Install update
  2. Get stuck on "Installing Update..."

Expected behavior To get updated, obviously

Screenshots VSCodium_3XHCNkxDXV

Desktop (please complete the following information):

  • OS: Windows 11 IoT Enterprise LTSC 24H2 26100.1457

  • Architecture: x64

  • Version: VSCodium_kP0EMYWLkN

  • App Manager: My hands, downloaded from the web

  • Sandboxed: ? no

Additional context I have a CodeSetup-stable-21b1e2955ddda36eeba3a94e643128e465285b93.exe (Size: 111,841,280 bytes, SHA1: 4bab1d9b0a6057008b4c8a3fc1cd438432cfd68c) under AppData\Local\Temp\codium-stable-undefined-x64

Codium update never worked for me since 1 month ago (which was the first time I installed codium)

0x416c69 avatar Aug 19 '24 07:08 0x416c69

same for me on macOS 14.5.

My VSCodium updated last 4 months ago onto 1.88.1 (could also be a full re install then, I'm not sure)

SteveOverSea avatar Aug 21 '24 21:08 SteveOverSea

@SteveOverSea See https://github.com/VSCodium/vscodium/issues/1917

daiyam avatar Aug 22 '24 07:08 daiyam

@daiyam As a temporary workaround, should we just reinstall the latest package manually? Or only macOS is affected?

0x416c69 avatar Aug 22 '24 10:08 0x416c69

@0x416c69 #1917 is only for macOS.

I'm assume you have installed it with a .msi and I can confirm there is an issue. The CodeSetup-stable-21b1e2955ddda36eeba3a94e643128e465285b93.exe is correct binary and when renaming as an .msi, you can run it manually. But the command line (msiexec.exe /i CodeSetup-stable-21b1e2955ddda36eeba3a94e643128e465285b93.exe or with the renamed .msi) used to run the update generates the error (This installation could not be opened.)

After a quick google, it seems a recurrent error with .msi, not specific with VSCodium. Not sure how to fix that...

daiyam avatar Aug 22 '24 10:08 daiyam

I recently opened #1994 but reading you guys made me consider something... Does anyone can confirm if auto-update only works if the installer was used, but not if its a portable folder instead?

Novack avatar Aug 22 '24 12:08 Novack

@Novack I've added a new comment directly on your issue.

daiyam avatar Aug 22 '24 13:08 daiyam

The same has been happening to me for around the same amount of time on Windows 11. I am using the MSI installer with updates enabled. Been manually downloading the installer for the past few months.

ghost avatar Dec 18 '24 08:12 ghost

Also confirming that the msi (with updates enabled) installer doesn't seem to be updating on Win11.

meichthys avatar Jan 24 '25 16:01 meichthys

Same here. VSCodium-x64-1.92.2.24228.msi Windows 10 Pro

Every time it opens it prompts to update, clicking update does nothing. I haven't come to manually install yet because I've been working on projects. Curious if there's a known fix for this.

Lexiconmancer avatar Jan 25 '25 20:01 Lexiconmancer

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!

github-actions[bot] avatar Jul 25 '25 01:07 github-actions[bot]

This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue, please open a new issue.

github-actions[bot] avatar Aug 25 '25 01:08 github-actions[bot]