This was a totally clean install as the conversions left GlassWire with serious problems on both my computers. I had removed every remnant of earlier installs as well.
The services are running.
The only thing that I did differently, which might have a bearing on the cause, was to have the Usage view open at midnight. I say this, because many versions ago I did have problems with change of day.
It turns out that the Graph is affected as well. The slow updating of the Graphs meant that I didn’t notice it last night.
This looks similar to an unresolved issue I reported in the past. That problem also occurred after I had also been doing a lot of different things in GlassWire:
I’m going to restart my system and see if the data is also lost this time.
The problem occurred before midnight, as you can see on the graph, so I don’t think that is related.
Initially, I was reminded of past problems that I had also had with having the GlassWire window open at midnight:
The other time that GlassWire stopped logging data was on an earlier test version, 1.2.57b. The only common thread I have noticed is that the data logging stops after I spend a couple of hours working in the GlassWire window. But it doesn’t stop while I am actually viewing GlassWire:
Please email our contact page and we can give you a version that takes logs, then you can email us the logs if you feel comfortable. If you don’t want to it’s OK, meanwhile we’ll continue to try to reproduce this on our end.
I used “Exit” and ran GlassWire again on both computers.
First computer MA04 is stuck visualizing network.
Second computer MA03 says “The GlassWire service stopped running”. The two options to continue don’t make any difference: “(Restart GlassWire)” or “Connect”.
Is it possible that it is related to the Windows 10 auto-update system as I am experiencing the same problem after an update. And That would explain It stopping at around the same time due too the fact your computer chooses times your not using it to update
You might be right as the only event I can see at that time relates to changing the start setting for the Background Intelligent Transfer Service, which is used by Windows Update.