Windows MSI: VSCodium not starting after update (manual re-install or repair necessary)

[JamesRand12]

Describe the bug
VSCodium fails to start after the latest update (version 1.98.2.25077). The application does not launch, and no error message is displayed.

Please confirm that this problem is VSCodium-specific
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
I checked the Docs page and the Troubleshooting page, and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

1. Update VSCodium to version 1.98.2.25077 using the auto-update feature within VSCodium.
2. Attempt to launch VSCodium.
3. Observe that the application does not start.

Expected behavior
VSCodium should launch successfully after the update, allowing me to use the application as usual.

Screenshots
N/A (No visual error or message to capture.)

Desktop (please complete the following information):*

• OS: Windows 10
• Architecture: x64
• Version: 1.98.2.25077
• App Manager: Originally installed using the installer with auto-update enabled, updated via the auto-update feature within VSCodium.
• Sandboxed: No

Additional context
The issue began immediately after updating to version 1.98.2.25077. Prior to the update, VSCodium was functioning correctly. I have tried restarting my computer and reinstalling VSCodium, but the problem persists.

[JamesRand12]

Now I remember why I disabled updates over a year ago. Every friggin time with VScodium... do you guys have any quality control at all?

[youdie323323]

Same issue here, is vscodium developer testing application before publish release?

[sebathefox]

Same issue here, when i try to start using powershell it gives the following error:

#
# Fatal error in , line 0
# Version mismatch between V8 binary and snapshot.
#   V8 binary version: 13.2.152.36-electron.0
#    Snapshot version: 13.2.152.41-electron.0
# The snapshot consists of 693457 bytes and contains 3 context(s).
#
#
#
#FailureMessage Object: 000000C7E3FFEEB0
----- Native stack trace -----

 1: 00007FF69D22F37A uv_cpumask_size+61482
 2: 00007FF69D9B3C3D uv_fs_get_path+43245
 3: 00007FF6A1E86698 Cr_z_adler32_combine+3181608
 4: 00007FF69BE9F75F v8::MemorySpan<std::__Cr::basic_string_view<char,std::__Cr::char_traits<char> > const >::end+317615
 5: 00007FF69BCC042B v8::Isolate::Initialize+267
 6: 00007FF69CF9771A uv_fs_get_system_error+353578
 7: 00007FF69B3CE5E4 uv_setup_args+6244
 8: 00007FF69B2A977A node::AsyncResource::CallbackScope::~CallbackScope+1498
 9: 00007FF69B2A543B v8_inspector::V8InspectorClient::generateUniqueId+73643
10: 00007FF69F80A2E2 Cr_z_adler32+5723138
11: 00007FF911BEE8D7 BaseThreadInitThunk+23
12: 00007FF912F5BF6C RtlUserThreadStart+44

[DomenicoMammola]

Same issue here

[daiyam]

I don't have the issue on my Win10 rig.

Can you try to run with .\VSCodium.exe --verbose?

[youdie323323]

@daiyam with the latest release 1.98.2.25078:

C:\Program Files\VSCodium>.\VSCodium.exe --verbose

C:\Program Files\VSCodium>


#
# Fatal error in , line 0
# Version mismatch between V8 binary and snapshot.
#   V8 binary version: 13.2.152.36-electron.0
#    Snapshot version: 13.2.152.41-electron.0
# The snapshot consists of 693457 bytes and contains 3 context(s).
#
#
#
#FailureMessage Object: 00000044475FE730
----- Native stack trace -----

 1: 00007FF7CBA5F37A uv_cpumask_size+61482
 2: 00007FF7CC1E3C3D uv_fs_get_path+43245
 3: 00007FF7D06B6698 Cr_z_adler32_combine+3181608
 4: 00007FF7CA6CF75F v8::MemorySpan<std::__Cr::basic_string_view<char,std::__Cr::char_traits<char> > const >::end+317615
 5: 00007FF7CA4F042B v8::Isolate::Initialize+267
 6: 00007FF7CB7C771A uv_fs_get_system_error+353578
 7: 00007FF7C9BFE5E4 uv_setup_args+6244
 8: 00007FF7C9BE7279 uv_fs_get_result+69721
 9: 00007FF7CAAE8302 v8::internal::compiler::CompilationDependencies::DependOnInitialMapInstanceSizePrediction+2026450
10: 00007FF7CAAEC1E7 v8::internal::compiler::CompilationDependencies::DependOnInitialMapInstanceSizePrediction+2042551
11: 00007FF7CAAE78FD v8::internal::compiler::CompilationDependencies::DependOnInitialMapInstanceSizePrediction+2023885
12: 00007FF7C9D977E2 v8::ScriptCompiler::ScriptStreamingTask::ScriptStreamingTask+472482
13: 00007FF7C9D9891A v8::ScriptCompiler::ScriptStreamingTask::ScriptStreamingTask+476890
14: 00007FF7C9D9873A v8::ScriptCompiler::ScriptStreamingTask::ScriptStreamingTask+476410
15: 00007FF7C9D96FE4 v8::ScriptCompiler::ScriptStreamingTask::ScriptStreamingTask+470436
16: 00007FF7C9D9718D v8::ScriptCompiler::ScriptStreamingTask::ScriptStreamingTask+470861
17: 00007FF7C9AD5391 v8_inspector::V8InspectorClient::generateUniqueId+73473
18: 00007FF7CE03A2E2 Cr_z_adler32+5723138
19: 00007FFB53B6E8D7 BaseThreadInitThunk+23
20: 00007FFB553BBF6C RtlUserThreadStart+44

[daiyam]

Can you try by disabling ~/.vscode-oss? (rename it to ~/.vscode-oss-no)

[sebathefox]

It doesnt work when renaming ~/.vscode-oss to ~/.vscode-oss-backup @daiyam, im getting the same error as earlier

[daiyam]

Have you tried to uninstall/install? Can you tell me which installer you use?

The issue is to be due the use of different V8 versions (13.2.152.41-electron.0 vs 13.2.152.36-electron.0)
I've checked on my VSCodium, it's use 13.2.152.41-electron.0 (in the about dialog).

[daiyam]

Here my windows:

> systeminfo | findstr /B /C:"OS Name" /B /C:"OS Version" /B /C:"System Type"
OS Name:                   Microsoft Windows 10 Home
OS Version:                10.0.19045 N/A Build 19045
System Type:               x64-based PC

What's yours?

[sebathefox]

I got an update notification from the previous version of VSCodium, which after some digging around used the VSCodium-x64-1.98.2.25078 installer

Heres my windows:

OS Name:                       Microsoft Windows 11 Business
OS Version:                    10.0.26100 N/A Build 26100
System Type:                   x64-based PC

[sebathefox]

It works when im uninstalling and using the VSCodium-x64-1.98.2.25072.msi installer

[Nalci]

Got the same issue. Not starting with the new update - Windows 11 Home.

Edit: It seems the previous version was not replaced. Initially, I had versions 1.98.2.25077 and 1.98.2.25078 listed under programs after the update. After removing version 1.98.2.25077, I no longer had any version of VSCodium, even though version 1.98.2.25078 was still listed. I uninstalled both versions, manually installed version 1.98.2.25078 and now it works.

[JamesRand12]

@daiyam I had installed a fresh VSCodium just a day before, this one exactly: VSCodium-x64-1.98.2.25072.msi

And then a update came last night within the editor and it downloaded and installed it, and now it doesn't start at all.