So far this year we have had just two small updates, comprising four minor bug fixes and a couple of UI tweaks. No new features or anything to address some of the longstanding issues and often promised improvements. Is GlassWIre dead?
4 Likes
HI @ittroll, we are testing a new software version with a new network scanner and driver. It’s a major update, that’s why we have been silent for a while. It took time to be ready but we are finally there.
We hope to release the software in September, we are currently beta-testing it.
5 Likes
That is reassuring to hear, thanks for the update.
Any news on firewall improvements for apps which update frequently, causing approval problems and a build up of duplicate entries?
Still impossible to update the Adobe Creative Cloud app without completely disabling the firewall first.
Still have an ever growing list of Microsoft Antimalware, Edge, Office, and Teams entries for each version, with no easy way to prune the old entries. The build up of these causes slow firewall operations.
Do the devs actually run GlassWire on their production machines? They should be made to eat their own dog food. I am sure some of these things would be prioritised if they had to experience the pain on a daily basis.
After sitting down for almost a year waiting for a fix for this “broken kernel” your statement leaves me with the following image printed in my head of what the development team must look like…
Apologise if you may think this is disrespectful but… I have sat here with a broken piece of software i paid for for almost a year… that must be deemed as disrespectful too right?
Too add to this… When you say a complete “new kernel being designed from the ground up”, what does this mean for legacy license holders? I guess you could suggest this is new software and the only thing legacy holders now have connection too is the name “Glasswire”
So do Legacy users get this “new” software as part the “lifetime purchase agreement” taken up with previous owners?
hi,
before opening a completely new topic for this, considering this topic here touches on the context of how glasswire is getting a driver rewrite, what i’d like to know is if the new model will allow glasswire to function with the windows event log service disabled.
at this moment in time i cannot use glasswire (free) since i run an “iot” / sanboxed like configuration of windows with minimal services and have to either use portmaster, tinywall, simple wall or fort firewall, which actually all do not have this prerequisite of event log running. the features are more or less comparable (at least for the free version) it is more a nostalgic reason for me to like to use glasswire again because i like the way it looks & feels.
so in this regard i would like to know if with the new beta of glasswire event log will still be a hard dependency to run it, and if yes what specific functionality inside of glasswire relies on it since it is the only firewall tool (and i have tested a lot of 'em …) that seemingly has this rather strict dependency.
and i get that event log is a good data source for some reporting stuff but it certainly can’t be a technical hard requirement for the bulk of tasks a firewall manages, so i wonder if enforcing this is really neccessary. or if at least having event log deactivated simply would turn of certain reporting / analysis aspects of the firewall but still let it do its magic.
thx
f.
1 Like
Hi @free,
GlassWire still relies on the Event Log service as it is necessary not only for the firewall, but for other functionality provided by the app. The main idea of the driver redesign at this stage is the optimization and stability improvements.
Andrea
Leave Windows services alone. There are no benefits to disabling services and the resources saved are barely even anywhere near kilobytes, in an age where we have 16-32GB of RAM minimum.
1 Like
Just out of curiosity - which one firewall you will suggest as glasswire replacement?
1 Like
Well if choose to disable some services, those that serve no utility to me. Collectively they add up and use processor cycles and memory. It is especially pointless leaving services running which you have then blocked with GlassWire; e.g. telemetry gatherers which want to monitor your usage.
“Idle RAM is wasted RAM.” is a popular saying in relation to all these “optimization” myths about disabling services.
Far too often - especially during the XP days with all the BlackViper snake oil of service disabling - have I seen people disable services because they didn’t need it. Later, they buy things to use with their PC but the services were disabled and the new hardware didn’t work. They blame the hardware or Windows when it was their own fault for disabling services they thought they “didn’t need”.
Still having trouble accepting this? That’s okay, this has been debunked for years.
- 10 Windows Tweaking Myths Debunked - 2013-10-13
- Should You Disable Windows Services to Speed Up Your PC? - 2016-05-02
- Performance Oriented Windows Tweaking - 2005-09-01
- Debunking Common Windows Performance Tweaking Myths - 2008-08-06
That said, my prior statement holds true:
Leave Windows services alone. There are no benefits to disabling services and the resources saved are barely even anywhere near kilobytes, in an age where we have 16-32GB of RAM minimum.
That’s some darn old articles you’ve dug up! The trouble now is every app and their dog wants to install their own service or background tasks. Some are useful to the user, whilst others are just there to grab telemetry data for the developer. Some are just badly written and inefficient.
Most of the active services on my machine have reserved between 1 and 5 MB each. A prime example is the SamsungMagicianSVC which reserves 6MB, it autoloads, but is only required if you choose to collect status and performance data. I know reserved memory doesn’t equal used memory, but background tasks can have a small impact on more demanding and time-sensitive processes. For me it is more about the fact that I don’t want a bunch of crap running that is of no benefit to me.
If you don’t fully understand what you are doing it is indeed best to leave services alone.
You think it’s because people are old? How about this: It’s young people on TikTok instead of working that is causing the problem.