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
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.
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.
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?
Merlin, any crash dumps sent to our bugs email on our contact page are useful along with all details about your OS and what exactly happened, plus any instructions on recreating the bug. Anything that you think might help is great!
My guess is the Glasswire service is programmed to have dependency on the Windows Firewall service, since itself is not a firewall replacement, but it can block programs by adding rules to the Windows Firewall. If the Windows Firewall is not running, the feature does not work.
I think we can’t do much about it, unless Glasswire itself becomes a standalone firewall, which I think is not its purpose. Or it can disable the feature of blocking programs when detecting that Windows Firewall is not running, but still run the rest of its functions normally, which would be ideal for compatibility with 3rd Party Firewalls.
If the Windows Firewall is required to run, I suggest adding a System Requirements section to the front page, so that at least people know that those who use 3rd Party Firewalls can’t use it.
@Ken_GlassWire, does your service write in the event log ? Because I can’t find any entry, while the service starts then stops immediatly, showing me this message : http://imgur.com/KSiT2r8
(which roughly translates to “The GlassWire control service on local computer has started then stopped. Some services stop automatically if they are not used by other services or programs”)
Is this service supposed to run ?
The only visible symptoms are this service which is stopped, and the main application stuck at “visualizing network”.
My os is windows 8.1 64bits, up-to-date (I just checked), and the windows firewall service is running.
Just wanted to inform of my situation. I installed GlassWire, rebooted, and was stuck on “Visualizing Network”. I always keep the “Windows Firewall” service disabled, so after reading this forum I enabled the service in “services.msc”. Then enabled the “GlassWire Control Service” and VOILA! IT WORKS!
If you don’t want Windows Firewall running you can turn it off in the settings and still have GlassWire work (everything except the Firewall tab). For me, I just don’t need Windows Firewall, so I had no reason to have the service enabled. GlassWire seems like a good enough reason to have the service running now (especially since I can keep Windows Firewall turned off)
So, in my instance, the reason for this error seemed to be because my “Windows Firewall” service was disabled in “services.msc”
Another data point. I had a similar problem. Glassware UI seemed to be running, but was not seeing any new activity, even when I started apps that reported their own internet activity. I stopped the UI and then the Glasswire service, restarted the service, then restarted the UI. It looks to be performing more as expected at this point, though it’s still early.
My system: Win7 x64 with all SPs and updates; default MS firewall and antivirus; wired ethernet.
In case it helps, after my initial install and system reboot, Glasswire saw a bit of “first network activity” and then nothing new for 24 hours.
FWIW, the GW UI just crashed. Nothing in the event logs.
We just released an update that should solve this “visualizing” problem https://www.glasswire.com/download/. Please upgrade and confirm it’s fixed for you. Thank you!