Open 0x416c69 opened 3 weeks ago
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 See https://github.com/VSCodium/vscodium/issues/1917
@daiyam As a temporary workaround, should we just reinstall the latest package manually? Or only macOS is affected?
@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...
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 I've added a new comment directly on your issue.
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
Please confirm that the issue/resolution isn't already documented
To Reproduce Steps to reproduce the behavior:
Expected behavior To get updated, obviously
Screenshots
Desktop (please complete the following information):
OS: Windows 11 IoT Enterprise LTSC 24H2 26100.1457
Architecture: x64
Version:
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)