Strange blocking since updating to Windows 2004

I don’t know if it is related, but on 2020-07-17, I updated Windows to the May Update (v2004). At some point after about noon on the 18th (I only turned this computer on the morning of the 19th), I found I had lost connectivity to the network.

Running GlassWire 2.2.210. Firewall on and set to “Ask to connect”. When I turned off the GlassWire firewall, immediately data started flowing to/from the network. Flipped it back to ON and within about 5 minutes, all traffic to the Internet was being blocked. Flipped it back OFF and traffic immediately started flowing.

I wondered if there was something I had blocked that was causing this and so went to the firewall tab and removed everything that was in the “Blocked” section by clicking the “x” that appears when you hover over a lin of a blocked app and acknowledging that I will be promoted when the app next tries to access the network.

Tried flipping the firewall on and off and got the same effect as before. In a few instances (when the GlassWire firewall was ON), I would get a tab in Google Chrome that would report that it was unable to connect to the address and then it kept trying and sometimes it would connect 15 - 30 seconds later.

I saw some recent news reports that in Windows 10 v2004, sometimes the network status indicator in Windows will incorrectly report that access to the Internet has been lost - and even though it is lying, some programs believe that indicator and will refuse to even try to access the network.

I have another computer at v2004 that does not have the problem I am experiencing on this computer.

The network status indicator on this computer never shows as having lost connectivity.

I am happy to remove GlassWire and do a clean reinstall if that’s the best approach, but I thought I would post here in case there is any value to be gained by trying other things, checking config, etc before I wipe out any evidence.

Cheers, Chris

1 Like


Sorry for the issue!

I believe another person reported this bug and it should be fixed on our next update. Have you ever moved your GlassWire database between PCs or drives by chance?

Thanks for the info about the status indicator but I don’t think it’s related in this case.

Thanks Ken

Yes, I moved my GlassWire database to a different drive. It is an internal drive, so should never be in a state where it isn’t there or anything like that.

Should I move the database back? I would rather keep it on the HDD where I now have it, rather than clutter my smaller, faster, SSD. If it MUST be moved back I can

But something odd - I looked on the web for instructions on moving the database, which I did a long time ago. I found something that said to edit c:\programdata\glasswire\service\glasswire.conf and add a string

I don’t have such a string in my glasswire.comf file. I do have
DbStorageDirectory = D:\GlassWireDB

Did I screw things up???


1 Like


This is a known bug when moving databases between devices or drives. We are looking for a way to fix it. It’s a bit complex because we’ll most likely have to create a database conversion system for everyone. I just learned it probably won’t be fixed in the next update, but probably in the one after.

The solution is to do a clean install but that isn’t acceptable of course. We appreciate your patience while we figure out what to do with this weird bug.

I will ask how that string may not be available. Maybe it’s related to the bug.

Update: The bug issue is related to that string.

1 Like

Will it fix things if I change

DbStorageDirectory = D:\GlassWireDB

(by the way - I notice I have space either side of the = sign but the examples using db_file_path don’t. Does that matter?)

Or do I need to move it back to the default location until the bug is fixed? Or is it safest to just do a clean install?



If you move the database back to its previous location and reboot the issue should go away.

I am not sure about changing the .conf file. I have been told the fix for this requires a complete database conversion of some sort, so I don’t think it will make any difference. It couldn’t hurt to try the changes you suggest temporarily though I think just to see?

I’d keep the spacing the same as your database currently shows.

Hi Ken

I decided to go with the nuclear option :slight_smile: - uninstall, reboot, clean install. So far, so good. I will leave the database on my SSD in the default location.

I noticed a couple of odd things;

The glasswire.conf file now requires admin rights to access. I don’t believe that was the case before.

In the GlassWire.conf file, the paths use a mix of forward and backward slashes, as in
DbStorageDirectory = C:\ProgramData/glasswire/service

Is that right?

Before I had all backslashes, as in;

So I am having to deal with the huge number of pop-ups I get from “Click to connect”, but I can live with that. I am looking forward to when programs signed with specific certificates can be allowed automagically.

Thanks again for your help. I was really baffled by what was happening. I am glad it wasn’t my fault. ha ha ha


1 Like


Yes, we changed the .conf file so it requires admin access for security reasons. I believe it was related to a HackerOne report.

I will ask about the mix of slashes and let you know what I find out.

Sorry you have to reset “Ask to connect”. Our next update will show publishers on the graph only at first but we’ll add them to the firewall later as an option.


The reason for the forward/back slashes is that we receive the part of the path from Windows and the other part is added by GlassWire. But it doesn’t matter. Both variants should work fine.

Thanks for all your info Ken.

Going forward, I would like to suggest a means be added to the UI that would allow people to choose a new location for the GW database and have the program take care of moving files, etc.

Also, having in the “Clear history” section of the UI an indicator of the current size of the database and how much could be save by removing older stuff.

Something like “Remove history older than 180 days, save approx. 300MB, remove history older than 90 days, save approx 100MB”

Cheers, Chris

1 Like


Yes, we are actively discussing a simple import/export feature.

Having a size component of the “clear history” feature is also a great idea. I haven’t thought of that.