This behavior may be related to a limitation in a Windows API introduced with the 24H2 update. In many cases, a clean install of GlassWire resolves the issue. If it doesn’t, the next thing to check is whether Location Services are enabled in Windows, as turning this on has been shown to fix the problem.
To help us confirm what’s happening on your system, could you please:
Check whether Location Services are currently enabled or disabled in Windows Settings.
If disabled, please enable Location Services and restart GlassWire to see if the issue is resolved.
Share GlassWire service logs with us.
Instructions to collect the logs:
Stop the GlassWire service
Open C:\ProgramData\GlassWire\service-full\glasswire.conf
as Administrator
Set the following parameter: LogEnabled = true
Save the file and start the GlassWire service
Reproduce the issue
Collect the log files from: C:\ProgramData\GlassWire\service-full\log
Please send the logs to help@glasswire.com. Once we have the logs and confirmation about Location Services, we can investigate further and advise on the next steps.