Stuck "Visualizing Network"

GlassWire seems to be stuck “Visualizing Network”. The settings dialog will pop-up but is inactive. I cannot navigate the tabs in the main dialog.

Other than standard network adapters I have VirtualBox installed which adds a virtual adapter, and Microsoft’s Virtual Wifi Miniport adapter. I’ve tried launching with those adapters disabled and it doesn’t seem to work. I assume the TAP adapter is yours so have left that enabled.

Steve,

I’m sorry to hear about this problem. What OS are you using? Our team may contact you privately for more details if that’s OK.

Thanks for trying out our software.

Hello! I’m having the same issue. Feel free to contact me for more details.
Thanks

I’m using Windows 7. Feel free to contact.

I am having the same issue for both my laptop and desktop. Feel free to contact me. Below are some details that might help you (apply to both laptop and desktop).

OS: Windows 8.1 (latest updates applied)
Network Adapters: Private Access VPN adapter (https://www.privateinternetaccess.com/), VMWare, Ethernet, default windows WiFi adapter.
Firewall: Windows Firewall. Created inbound/outbound rules for Glasswire
Antivirus: ClamWin with ClamSentinel.

Edit: Should note, I have tried glasswire with the VPN off and on just out of curiosity. Did not fix anything.

I’m not sure if this is a related issue, but when I first ran it after install (no reboot), it was stuck on this as well with everything frozen. After reboot, it lingers on this for a few seconds, then goes to “Connecting to local server” where it attempts to try up to 3 times before saying, “Unable to establish connection. Push the Connect button to reconnect”. Clicking the button goes back and forth between “Connecting to local server” and “Unable to establish connection”. (I’m using win7 64-bit pro on a desktop)

Sounds like the Glasswire service is not running or did not run properly. Can you check whether is the service running? Open your start menu, type in “services.msc” and press enter. Look for the Glasswire service, is it running?

I have the same problem, when I try to start the service, it just stops, nothing useful in the system log.
I’ve also got the virtualbox adaptor installed, EMET5.0 and avast. Windows 7 64bit.

Same problem here. 30 minutes of Visualizing Network and no go. Rebooted a couple times same result. I manually restarted the service and it starts then stops immediately. OS Windows 7 32bit.

Same problem there.

Maybe it’s proxy or adminstrator account related.

We’re working to recreate this bug and fix it in the next release. Sorry for the problem. Our team may contact you for help, I hope it’s OK.

Thank you.

No problem.
It’s fine :wink:

I’m also running into this issue.

My system is a Win7 x64 install.
The following error is present in the window application event log:

Faulting application name: GWCtlSrv.exe, version: 1.0.20.728, time stamp: 0x53f5b0ff
Faulting module name: FirewallAPI.dll, version: 6.1.7600.16385, time stamp: 0x4a5bd9f1
Exception code: 0xc0000005
Fault offset: 0x0003f111
Faulting process id: 0x5a74
Faulting application start time: 0x01cfc136e3815887
Faulting application path: C:\Program Files (x86)\GlassWire\GWCtlSrv.exe
Faulting module path: C:\Windows\SysWOW64\FirewallAPI.dll
Report Id: 2279f25e-2d2a-11e4-aa6e-080027009831

And, here is the contents of the Crash report, though, there is no call stack, so I’m not sure how helpful this will be:

Let me know if there is anything else that I can provide to help correct the issue.

Version=1
EventType=APPCRASH
EventTime=130535355729646279
ReportType=2
Consent=1
UploadTime=130535355739937586
ReportIdentifier=2279f25f-2d2a-11e4-aa6e-080027009831
IntegratorReportIdentifier=2279f25e-2d2a-11e4-aa6e-080027009831
WOW64=1
Response.BucketId=456613992
Response.BucketTable=17
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=GWCtlSrv.exe
Sig[1].Name=Application Version
Sig[1].Value=1.0.20.728
Sig[2].Name=Application Timestamp
Sig[2].Value=53f5b0ff
Sig[3].Name=Fault Module Name
Sig[3].Value=FirewallAPI.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=6.1.7600.16385
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4a5bd9f1
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0003f111
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
UI[2]=C:\Program Files (x86)\GlassWire\GWCtlSrv.exe
UI[3]=GlassWire Control Service has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution (recommended)
UI[6]=Check for a solution later (recommended)
UI[7]=Close
UI[8]=GlassWire Control Service stopped working and was closed
UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
UI[10]=&Close
LoadedModule[0]=C:\Program Files (x86)\GlassWire\GWCtlSrv.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\syswow64\USER32.dll
LoadedModule[5]=C:\Windows\syswow64\GDI32.dll
LoadedModule[6]=C:\Windows\syswow64\LPK.dll
LoadedModule[7]=C:\Windows\syswow64\USP10.dll
LoadedModule[8]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\syswow64\ole32.dll
LoadedModule[15]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[16]=C:\Program Files (x86)\GlassWire\MSVCP110.dll
LoadedModule[17]=C:\Program Files (x86)\GlassWire\MSVCR110.dll
LoadedModule[18]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[19]=C:\Windows\syswow64\NSI.dll
LoadedModule[20]=C:\Windows\system32\fwpuclnt.dll
LoadedModule[21]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[22]=C:\Windows\syswow64\USERENV.dll
LoadedModule[23]=C:\Windows\syswow64\profapi.dll
LoadedModule[24]=C:\Windows\system32\WTSAPI32.dll
LoadedModule[25]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[26]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[27]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[28]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[29]=C:\Windows\system32\WINNSI.DLL
LoadedModule[30]=C:\Windows\system32\VERSION.dll
LoadedModule[31]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[32]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[33]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[34]=C:\Windows\system32\WINHTTP.dll
LoadedModule[35]=C:\Windows\system32\webio.dll
LoadedModule[36]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[37]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[38]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[39]=C:\Windows\system32\IMM32.DLL
LoadedModule[40]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[41]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[42]=C:\Windows\SysWOW64\FirewallAPI.dll
LoadedModule[43]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[44]=C:\Windows\system32\WINSTA.dll
LoadedModule[45]=C:\Windows\system32\rsaenh.dll
LoadedModule[46]=C:\Windows\system32\bcrypt.dll
LoadedModule[47]=C:\Windows\SysWOW64\bcryptprimitives.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=GlassWire Control Service
AppPath=C:\Program Files (x86)\GlassWire\GWCtlSrv.exe

I appear to have found a solution to this issue for me.

The Windows Firewall service on my machine was not starting due to the following error http://support.microsoft.com/kb/2478117

Switching the Account for the Windows Firewall service from Local System to Local Service and clearing the password allowed the Windows Firewall service to start normally.

After I was able to get that corrected, I attempted a reinstall of GlassWire and was able to start it without issue.

This is interesting.

Windows firewall is replaced at my place with McAfee HIPS.

Thank you everyone for all your help on this so we can fix it.

I have the same problem, mostly the same set up. Windows 7 Pro x64. Does Glasswire require the Windows firewall service to be started? I certainly don’t want it running. Unable to establish a connection like everyone else.

Same for me, I have Windows 8.1 64bits. I tried to start glasswire’ service, but it stops immediatly.

Ah from kmueller’s post, it was something to do with windows firewall. I had the service disabled on my system. When I enabled and started it, I could start Glasswire’s service (before it would self terminate, as DustyOne mentioned). Once that started up, it worked fine. Though, upon disabling windows firewall service, Glasswire would lose it’s connection. Does it have to be dependent on that?