Click to Block pulldown unselectable /Update check for an app fails

@frustrated

Our latest software is now 2.2.210. I recommend updating if possible and see if the problem continues or not.

If the problem continues please let me know if you use any other firewall software. If you use a secondary firewall along with ours it can cause conflicts like this where the firewall cannot function normally.

image

I updated to 2.2.210 and I am extremely concerned since I went to the firewall page and the pull down to toggle between Ask to Connect and Click to Block seems to work althought as the graphic shows it appears the Firewall is disabled. Why?

P.S. I had to reboot the computer as no matter how much I clicked on the OFF box to toggle it back on I got no response from Glasswire. I noticedt that even if I toggle it to an OFF state I have to wait a minute or two it seems before I can toggle the firewall back on.

Shouldn’t Glasswire alert the end user when it is in a OFF state after all what use is a software based firewall when it can be disabled and not inform the end user that it has become disabled?

@frustrated

Do you use another firewall software besides ours by chance? Usually if our firewall is not working it will give the other app name that is blocking it.

May I ask what other security software you use?

Would you consider clearing your firewall rules and trying a clean install? Please confirm and I can provide instructions.

Other than perhaps Windows10 firewall that is it security wise I use Eset Antivirus and Malwarebyte Anti-Malware.

Is there anyway of backing up these settings so that I can restore them should the clean install not solve the issue?

@frustrated

Before we do a clean reset, I was curious if your ESET version uses their own firewall or not? I found this page with information.
https://help.eset.com/essp/12/en-US/idh_page_epfw_settings.html

I also found this page https://support.eset.com/en/kb2421-eset-firewall-compatibility-with-microsofts-windows-firewall.

We use the Windows firewall API for blocking. If another security software is blocking us from using it then we cannot block and that would explain why your firewall is set to off. Usually GlassWire can detect this and tells which app is causing the issue and this error appears on the firewall screen.

Malwarebytes should have no issues with GlassWire.

No this is strictly Eset NOD32 antivirus only no firewall in the product at all.

@frustrated

Have you installed or tried any other firewall-related software recently? It’s not usual for our firewall to just not turn on at all.

With the Windows Firewall API is very reliable and relatively simple. It’s quite strange it would not turn on at all unless another app may have modified the API rules or settings somehow.

You mention you want to back up your rules. Did you modify the Windows Firewall manually at one point and is that what you want to back up, or do you just want to back up GlassWire’s rules?

I would not recommend backing up GlassWire’s rules because something is clearly very wrong here and it’s probably due to the rules with Windows Firewall.

I just wanted to back up Glasswire rules. I have been down this road before with Glasswire when I was using the free version of the product 3 years ago. That was on Windows7 on another computer and I wiped out Glasswire rules and it did not help the issue. I gave up and uninstalled the free version at the time

Personally do not think I ever used any firewall product on this Windows10 computer.

Well this morning I booted up the computer used it for 3 hours then decided to check GLasswire and discovered the Firewall was turned off. No amount of clicking on OFF toggle would turn it on. Rebooted the computer and the Firewall is now on.

If everything is working now then I’d leave it alone. If you want to reset everything related to the firewall you should do the following:

  1. Uninstall GlassWire in add/remove programs.

  2. Go to the Windows Firewall control panel and choose “restore defaults”.

  3. Reboot

  4. Install our latest version and choose “reset firewall” in the installer as an option.

This will keep all your other GlassWire settings, but reset your firewall. If the problem continues then it’s most likely something wrong with the Windows Firewall API itself (which is not something I see very often). I’d recommend running Windows Update and see if there are any updates available if you can.

I think I will reset everything because like yesterday on boot up this morning the Glasswire firewall was disabled completely and could not be turned on

I wish I could suggest another solution but this is an unusual problem. I follow all support for GlassWire and nobody else has reported this, unless they are using two firewalls or using an antivirus that disables the Windows Firewall API. In those cases there is usually a setting with the antivirus to use the Windows Firewall API.

If the problem continues after the reset please let me know and we can provide a version of GlassWire that has logging. We might be able to find the cause of this with detailed logs.

I did the uninstall. I told Windows Firewall to reset to defaults. Rebooted and during the reinstall told Glasswire to do a clean install. Firewall was enabled. Rebooted machine and checked and the Firewall was again disabled on reboot.

P.S. Rebooted a 2nd time and still can not get Glasswire Firewall enabled.

OK. I will let our team know about this issue and I’ll probably message you privately for next steps (most likely a logging version).

Interesting. I went into Services tab under Task Manager and restarted GlassWire service and the Firewall in GlassWire became enabled.

@frustrated

Do you see any .dmp files on your desktop? If so our service crashed and that .dmp file would give us details on how and why.
https://www.glasswire.com/contact/

You could email us the .dmp using a cloud service like Dropbox or Google Drive.

Sorry no .dmp files on the desktop here. By the way the service was running before I restarted it and got the firewall running.

1 Like

I hope the situation is fixed permanently with the restart. Thank you for trying that.

Personally I doubt it since I rebooted Windows10 here probably 6+ times today and it was hit and miss on whether the Firewall became active. It was more deactivated than anything after all those reboots. If it was a service issue then FW should of been solved after the first reboot. At least for now I have a way of re-enabling the firewall. I wonder if I change Glasswire service to Delayed-Start in services would help at all? Perhaps this computer has an issue with all the services starting up at the same time.

I have never heard of delayed-start solving something with GlassWire but I don’t think it can hurt.

Meanwhile we have a ticket open with our team on your issue. I will let you know what they want to know next. Thanks for your patience.