I am very sorry about this issue.
This issue is caused by an update that was released, then quickly replaced after a few days. Details on what happened are here GlassWire 2.2.291 now available - See process IDs and services - #3 by Ken_GlassWire and that link includes a fix.
Our QA tested with the fix we suggested in the thread linked above and they found it solved the issue. I hope it will solve the issue for you also?
Thanks for your patience with this problem.
I agree it is unacceptable that this happened and we put out a fix within days once we determined the problem. If you can implement the suggested changes in the threads above it should solve the problem for your permanently.
Again, I apologize for the issue that this caused.