Since the update to 3.7.880 I’ve been having Glasswire crash extremely often. Reinstalls and things like that are not fixing the issue. If I had more free time recently I’d look at the dump files generated. It is putting entries into Event Viewer when crashing. There’s been at least four or five entries since the update, and they all say the same thing. See below.
If anyone needs the previous version for the sake of stability, you can download 3.6.859 here.
Thanks for reporting this and for your patience while we’ve been investigating.
Our team has looked into the issue, and it appears that the crash originates deep within a Windows library (CoreMessaging.dll) and is related to Qt, the framework we use for GlassWire’s interface. We’ve found similar reports from other applications on Microsoft’s forums here: Microsoft Q&A: How to fix app crash under Win11 in CoreMessaging.dll
At the moment, we don’t see any crash dumps from GlassWire that directly point to this issue. However, we believe it may be resolved when we move to Qt6, which we are currently in the process of migrating over to.
We appreciate your understanding and continued feedback. If you continue to experience crashes, please share any crash logs or additional details you might have so we can keep monitoring this closely.
It’s been almost three weeks since an update by staff and over a month since my initial report. The latest version crashes daily, often multiple times. Why hasn’t there been a fix released to at least stop the crashing? Even the previous version 3.6.859 occasionally crashes.
@Huda_GlassWire It’s been nearly two months. Why is there no update? With the length of time the holiday season is no excuse. This needs to be patched at minimum asap.
At this point I’m looking at another firewall. Why? Nothing has been addressed since OCTOBER 2025. My post here was on the 11th of October, well after this crash issue had been happening.
Two versions that crash randomly with not even a mention of a fix? It’s disappointing because this was at one point an excellent firewall.
I say this as someone who has an Elite license, as well.
Hi @Tarun, I responded to your comment about the crashes you’re experiencing in the firewall thread but wanted to provide an update here as well. I’m sorry there hasn’t been a more recent update.
I wanted to share a bit more context on where things stand. We had started work on migrating the UI to Qt6, but that work had to be temporarily put on hold while we focused on the firewall issues. We shifted focus to the firewall issues first, while continuing to track crash reports, so we could stabilize one area before moving on to the next.
Now that we’re wrapping up the firewall work, migrating to Qt6 is the next major thing we’ll be focusing on. The current framework is no longer supported, and we believe this migration will help improve overall stability and reduce crashes.
If you’re able to share any details that could help us reproduce the crashes you’re seeing, such as what you’re doing when it happens or anything that seems consistent, that would really help us investigate.
Sorry again for the lack of updates, and thank you for your patience while we work through this.
I’ve reinstalled the firewall and did a clean install. I have not had any issues yet. I was back on 3.5 and went back up to 3.7. I think there was a UI glitch when I went back to 3.7 that I had to reinstall. The Active Apps, etc appeared under the In/Out Connections area, and the reinstall fixed it.
A few details that may help reproduce the issue:
I’m pretty sure the problem stems from using the Ask to Connect firewall mode.
I have an Elite license - I have my other computers connected to my main PC firewall. They are not on the same firewall mode and have not had the same issue.
I have noticed when I’m looking over the logs of the other computers, when I click back to the firewall on my main PC I suddenly get a lot of popups from programs that have asked and been waiting to connect. I do not believe this is the proper behavior. A way to rectify this is to allow popups asking for permission to have a title for which PC they are for.
If I think of any other relevant info I’ll post about it. If the issue comes back, I’ll also share what I find.
I swear I jinxed it, the firewall crashed later last night after I made the post.
It had been fine for days until I went under the left sidebar and checked the other PCs on my network running the firewall. When I clicked back on this PC I got all the alerts of connection requests. I wonder if that’s a part of it. I’ll keep monitoring and report back my findings.
@tarun Thanks so much for sharing all of this, and sorry it decided to jinx itself on you . I know how frustrating that can be.
The details you mentioned around Ask to Connect mode, switching between PCs, and the burst of connection prompts when coming back to the main PC are really helpful. I’ll make sure this all gets shared with the team so we can dig into it.
Please do keep an eye on it and share anything else you notice. Really appreciate you taking the time to test and report back.
Hey @Tarun - I passed the latest information along to our development team, and they’d like to dig further into your specific crash. Would you be willing to send me your Device ID (in a private message) so they can look it up in our crash reporting tool?
You can find it in the Windows Registry by following these steps:
Press WIN + R
Type regedit and press Enter
Navigate to: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\GlassWire\full\CloudDeviceId
Based on what we’re seeing, the team believes this issue should be resolved when we migrate GlassWire to x64 and update the framework to Qt6, but having this information will help us confirm and investigate further in the meantime.
. I know how frustrating that can be.