As of lately the Glasswire service on my computer and generating memory dumps on my Desktop and then the application doesn’t do anything until i open it and press the restart service button.
Is there anyway i could possible resolve this?
3 Likes
hey @Airchunk, could you please send those dumps over, (with something like a wetransfer) to help@glasswire.com? We would like to investigate and help
Best,
Andrea
I have sent the latest dump over wetransfer
1 Like
same here… service dies within seconds. One could restart it manually or even configure to auto restart if being down, but that’s not a solution.
Happens since it updated to the latest version I’d say.
Edit:
Since I got the elite version some more comments:
It does work on my old Win10 machine.
But it fails on 2 of my Win11 machine.
Just in case that does matter.
exactly the same for me,
service crash within a minute of the computer start and can’t get it back
and it send me to a link without any support …
www glasswire com/faq/#glasswire-cant-connect-local-server
elite version
Win11 GW3.4.748 => Ko
Win10 GW3.4.748 => Ok (but a warning to unblock itself)
Win11 GW3.4.748 => Ok (but a warning to unblock itself)
Downgraded my 2 main machines by now.
Glasswire www site > download
Then scroll down until you see “change list page”
You get 2 links presented, the 3.4.648 (buggy) and an older one “3.3664”
So you copy one of the links, past it into a new browser view and modify the versionnumber so it matches 3.4.694
I installed it straight on top of the newer one and it worked.
Server doesn’t quit anymore.
Remember to turn of auto-update in the settings.
After a while a popup reminds you about a new version.
I selected “skip that version” and I think I got it solved.
have fun … there’s other more stupid and less appealing firewall solutions around. 1 problem within 12 months is quite one I’d say.
Nevertheless firewall software is a critical one … since so it should be tripple checked before being spread if it really does work.
Glasswire is an Outbound Firewall only you must have Windows Firewall on as well so your Computers are not exposed. 
Also no issues here on Windows 10 Pro.
1 Like
Well nope, yesterday Win10Pro worked … but yesterday eve I realised it suffers the very same problem. GW service dies within minutes, so I also had to downgrade.
@darkness
I wouldn’t be that harsh. Bugs do happen.
But their support seems to have some days off 
In the past it was lots faster reacting upon emails sent to the support, if only with a small note “under investigation”.
Not to mention that I used other firewall software prior to GW and most of these had lots more problems. With GW I seem to remember I had 2-3 issues since it licendes GW back in 2016, which is quite a bunch of years and I can hardly name other software titles with less bugs/problems across such a period of time.
1 Like
@darkness I deleted your post. If the forum is the right place where to express doubts and critiques, we want to keep a decent language.
We are definitely committed to listen to our community, no matter the topic, as long as there is respect for the work of everybody.
Andrea
@Andrea_GlassWire
After this update it seems like Glasswire doesn’t load it’s services anymore completely. I run windows 11 pro 23H2 with an admin and an SUA account.
When I upgraded it while running the admin account the GUI was broken on the SUA account.
I used my backup software and rolled back before the update. I updated Glasswire while running on the SUA account (NO elevation or admin pw was needed) now
glasswire was broken on the admin account.
Tldr: For me the account that wasn’t used while updating gets a borked Glasswire install.
Updated while on admin acount= GW on Sua broken
Updated while on SUA account= GW on Admin broken
Only these services get loaded on the borked account:
Same issue, client keeps crashing since update. Unable to resolve.
thx, work like a charm, i was feeling naked without it
Same issue here. The service keeps crashing since the most recent Glasswire update and have to manually restart it.
Same here. Old issue is back almost 1 year after previous similar issue emerged.