Sorry for not replying for a few days, I was collecting more details (what I had wasn’t much) and just generally monitoring GlassWire’s behavior.
I decided to post this here publicly as I feel this may be a situation where experiences from other people (and their hardware) is very valuable.
First off, a couple screenshots:
^ Screenshot from Chrome, shows random connections not displaying upload bandwidth. (This is just one example of many)
^ I didn’t get a screenshot of the two apps merging into one entry but here you can see Discord randomly becoming the LXSS (Linux Subsystem) “ping” command. This “entry swapping” seems to start and end randomly, although a creating new GlassWire database/history files is an instant fix.
Interestingly the upload bandwidth recording seems to work fine sometimes right after booting but breaks shortly after.
My setup: Everything worked fine until around the beginning of this month then the whole issues with upload bandwidth recording started on my old install (LTSC 2019/1809) and continued over to my new install (Windows 10 Enterprise 1903), the new install was installed completely fresh (disk reformatted) and I didn’t import my old GlassWire data.
Edit: I also had it happen once or twice that download bandwidth wasn’t recorded at all (or only a few hosts) for a specific application until it was restarted.
Edit 2: Very interesting, seems like i am not alone with this issue? No upload visible on some programs But that thread was started last year…
Edit 3: I just remembered a few other things that I should mention: I am using DNSCrypt-Proxy https://github.com/jedisct1/dnscrypt-proxy for DNS (I don’t think that should matter for upload bandwidth?) I also disabled nslookup in the GlassWire config, I left it enabled for a test and it didn’t fix the issue.
I also totally forgot to put this in the post right away: I actually previously experienced bugs with “0” upload when using IPv6! I usually have it disabled for various reasons but this was something that I found noteworthy, interestingly it never affected IPv4 before now. This all is such a weird issue!