@Ken_GlassWire For what it’s worth, I just did the following steps to rule out which things on my computer are interfering with Backblaze:
- Disable Windows Defender fully (Backblaze still didn’t work)
- Disable Windows Firewall fully (Backblaze still didn’t work)
- Disable GlassWire’s firewall fully (Backblaze still didn’t work)
I did all of these things individually and all together at the same time. I also made sure to stop the Backblaze service and kill all running Backblaze processes. Backblaze still didn’t work after taking all of these steps individually and in combination.
Finally, I re-enabled all of the above features/software. Backblaze still didn’t work. Then I uninstalled GlassWire and restarted my computer. Backblaze started working again. Windows Defender is on and Windows Firewall is on (I did not restore my firewall settings to their defaults - old GlassWire firewall rules are still present in it).
I have a strong hunch that GlassWire is doing something else that interferes with Backblaze. Think about it: GlassWire is monitoring all network traffic connections that are associated with running processes, and it prompts users to Approve/Deny connections being attempted by processes. This makes me think that GlassWire is hooking parts of Windows OS that could potentially interfere with running processes’ network connectivity, even before GlassWire updates Windows Firewall’s rules.