Glasswire crashes regularly

I am a Glasswire Elite user, and it is crashing every couple of days on one laptop, requiring a restart of the service.
I have tried a clean install several times now but it is still occurring.
I have a GWCCtlSrv.exe.6452.dmp on my desktop but it is 1.90 GB.
I would love to know the culprit but how do I transfer such a large file to you?

I am using v3.3.498 but these crashes started some time/versions ago.
Win 10 Reliability Monitor shows the following:

GlassWire Control Service

Stopped working

‎2023-‎03-‎27 2:18 AM

Report sent

Faulting Application Path: C:\Program Files (x86)\GlassWire\GWCtlSrv.exe

Problem signature
Problem Event Name: BEX
Application Name: GWCtlSrv.exe
Application Version: 3.3.498.0
Application Timestamp: 641896d4
Fault Module Name: ucrtbase.dll
Fault Module Version: 10.0.19041.789
Fault Module Timestamp: 82dc99a2
Exception Offset: 0009eddb
Exception Code: c0000409
Exception Data: 00000007
OS Version: 10.0.19045.
Locale ID: 1033
Additional Information 1: 59bf
Additional Information 2: 59bf3ad3c2f1211030adbc88b988b236
Additional Information 3: 2cdc
Additional Information 4: 2cdc46fb01bf33b93264ab1fd39fe6e0

Extra information about the problem
Bucket ID: 6c706ea087e67a72328f7c5c27f4795c (1337424349601495388)

Hi @paulderdash,

Please can you upload the crash dump to Google Drive or Dropbox and email the access link to me

Please address the email FAO Katie so that I can make sure it redirected to the right team.


I sent two dump links on 28 March FAO Katie. Any news?
It still happens.
Can I delete those dumps, and/or send more dumps?


As mentioned here: Glasswire Continues to Crash Regularly - #2 by paulderdash

I see this sort of thing after each crash >

Still awaiting a response from the devs.

It may be an edge case, but I have it on two laptops (every night on my main laptop, less frequently on the other).

But on the other hand, these may be the same problem?:

1 Like

I have done multiple clean installs as described, with no effect.

And perhaps it is not an isolated issue: