Sublime Forum

**bschaaf** · December 15, 2023, 9:46am

Best guess it’s our new crash reporter (crashpad) if it’s build 4153, but there’s nothing we can do to fix that.

**fuego** · December 15, 2023, 4:42pm

I wanted to come and say that I am also having issues on 2 different Windows systems - one work, one personal starting after I was prompted to upgrade to v 4166. Based on some of the feedback here, I uninstalled the latest version and reinstalled version 4152 and it started working again. Not sure what is going on - I’ve been using (and paying) for Sublime for almost 7 years and never had an issue until now. My macOS/Linux systems are fine, so it seems localized to Windows.

**deathaxe** · December 17, 2023, 5:28pm

All ST builds running fine on my company managed Win10 x64 22H2 and private Win11 x64 22H2 machines. So this is not a general issue and probably unfixable without information about circumstances causing it.

Such early application crashes are always suspicious.

Just a guess, but maybe the issue is related with out-dated Visual Studio redistributables. ST ships with a vcruntime140.dll, but Windows ignores it if a library of that name is found in a more trustworthy location. Not sure what happens, if those are too old.

I’d be curious, whether upgrading would have any effect.

vc_redist.x64.exe

from

**manubop** · January 3, 2024, 10:27am

@deathaxe, thanks for the suggestion but, unfortunately, updating vcruntime140.dll has no effect. Oh, and, happy new year !

**Frindleblat** · January 4, 2024, 8:52am

I remember facing a similar issue once, but honestly, I can’t recall exactly how I resolved it. I think it just sorted itself out after a bit of tinkering.
For your situation, reverting back to v4166 seems like a practical solution, especially since you’ve got a lot on your plate. You can download previous versions of Sublime Text from their official website. Just go to the download page and look for the version archives.

**corporatedrone6453** · January 4, 2024, 11:54pm

4169 upgrade did not work for me in Win 10. Corporate user so anti-virus may be in play. Can’t really turn it off. However, I haven’t had any issues with upgrades before.
Downgrading to 4152 works fine for now.

Faulting application name: subl.exe, version: 0.0.0.0, time stamp: 0x655fb165
Faulting module name: ntdll.dll, version: 10.0.19041.2788, time stamp: 0x2f715b17
Exception code: 0xc0000005
Fault offset: 0x0000000000063526
Faulting process id: 0xdfc8
Faulting application start time: 0x01da3f6fa41d8b7d
Faulting application path: C:\Program Files\Sublime Text\subl.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

**deathaxe** · January 9, 2024, 3:36pm

It seems subl.exe is used to start ST and crashes. I wonder if starting sublime_text.exe directly also crahses.

**flyrape8490** · January 11, 2024, 2:59pm

Tangentially related: this ntdll issue is also occurring with sublimemerge (2083 works but 2091 fails).

**luckystreak** · January 12, 2024, 4:11pm

I have the same issues and am on Windows, and I got things to work with the newest version by doing this:

Shift-click the icon in the taskbar and run Sublime as Administrator

This makes Sublime start up and work basically like before. I hope this helps someone

EDIT: Interestingly, this worked for me yesterday, but today even this does not work…

**flyrape8490** · January 12, 2024, 2:51pm

unfortunately there are people using sublime on work machines and do not have permissions to run as administrator

**deathaxe** · January 12, 2024, 3:39pm

That’s just a hint for the devs, I guess. But actually it indicates some OS level API functions possibly being blocked by insufficient credentials or other security functions (e.g. antivirus), which is probably not expected by some of ST’s core functionality and thus breaks it.

**PseudoProxen** · January 14, 2024, 8:19pm

EXCEPTION_DEBUG_INFO:
dwFirstChance: 1
ExceptionCode: C0000005 (EXCEPTION_ACCESS_VIOLATION)
ExceptionFlags: 00000000
ExceptionAddress: ntdll.00007FFC83003ACA
NumberParameters: 2
ExceptionInformation[00]: 0000000000000001
(x64dbg://localhost/address64#0000000000000001) Write
ExceptionInformation[01]: 0000000000000024
(x64dbg://localhost/address64#0000000000000024) Inaccessible Address
First chance exception on 00007FFC83003ACA
(x64dbg://localhost/address64#00007FFC83003ACA) (C0000005, EXCEPTION_ACCESS_VIOLATION)!

Some info with x64dbg, which is an interesting issue to say the least

Between versions 4152 to 4153 something changes that cause this to happen on my side.

**PseudoProxen** · January 14, 2024, 8:23pm

Which I am now wondering if it is dealing with Macro Recording, since that can invite loads of HIP-related issues.

**gatapia** · February 5, 2024, 8:56pm

Downgrading to 4152 also fixed for me (4166 still crashes)

**wkr** · February 14, 2024, 1:12pm

+1 on this. Funny thing tho, got new work laptop, ran 4169 no issues for a month, then it would start with plugin host 3.3 and 3.8 errors with all plugins not working, and then it wouldnt start at all. Downgrade to 4152 + redownloading package control and lsp solved the issue. Unfortunately not sure which one of these specifically, but reinstalling 4169 would not make it start, 4152 would.

**NWB** · February 14, 2024, 3:08pm

I am getting this error when I start sublime on Windows 10

Nome dell’applicazione che ha generato l’errore: sublime_text.exe, versione: 4.1.6.9, timestamp: 0x655fb2ce
Nome del modulo che ha generato l’errore: ntdll.dll, versione: 10.0.19041.3636, timestamp: 0x9b64aa6f
Codice eccezione: 0xc0000005
Offset errore 0x00000000000634f6
ID processo che ha generato l’errore: 0x7134
Ora di avvio dell’applicazione che ha generato l’errore: 0x01da5f5c9b1297ff
Percorso dell’applicazione che ha generato l’errore: C:\Program Files\Sublime Text\sublime_text.exe
Percorso del modulo che ha generato l’errore: C:\Windows\SYSTEM32\ntdll.dll
ID segnalazione: db82e655-1be7-463a-bf77-0bae31539049
Nome completo pacchetto che ha generato l’errore:
ID applicazione relativo al pacchetto che ha generato l’errore:

**EvanG** · February 15, 2024, 6:35pm

Using the Sublime Text 4.1.6.9 portable version on Windows 10, I noticed the compatibility troubleshooter must be executed on the sublime_text.exe file. The troubleshooter reconfigures the executable to use Windows 8 compatibility mode, even though it may already be set.

Anyone else have this issue?

**larrygrobertson** · February 15, 2024, 8:30pm

You might try opening a cmd window, change directory to the directory where Sublime Text’s version of VCRUNTIME140.dll resides and re-register the dll with the following commands.
regsvr32 /u VCRUNTIME140.dll
regsvr32 VCRUNTIME140.dll

**flyrape8490** · February 29, 2024, 3:41pm

You might try opening a cmd window, change directory to the directory where Sublime Text’s version of VCRUNTIME140.dll resides and re-register the dll with the following commands.
regsvr32 /u VCRUNTIME140.dll
regsvr32 VCRUNTIME140.dll

This did not work. Running the command in the install directory gave me this error message:

@EvanG 's suggestion of troubleshooting compatibility did not work either.

**deathaxe** · February 29, 2024, 4:27pm

I would have been surprised if that would have worked because vcruntime is NOT a COM library and therefore does not expose anything for regsvr32 to use.

Whatever you do, Windows uses this application-local file only as a very last fallback in case no other file is present in a more trustworthy location.

According to various feedback discussions this issue is most likely caused by Anti-Virus programs. It’s not ST’s fault. It just suffers from API calls being blocked or something along those lines.

Sublime Text 4 Does not start