In general i use a VPN router, but sometimes when i want to switch to another location, without changing the manual config, i use the app.
I recently discovered that when i enable killswitch on the app, SS is being disabled. As soon as i disable killswitch, SS starts to function normal again.
Received, thank you. Can you confirm what version of SpyShelter you use, if you go to our top right cog icon, then choose “About”? Does this happen with our latest software we just released? 15.4.0.1012
Most likely your VPN software prevents communication between the SpyShelter UI application and SpyShelter system service that is required for correct functioning of the app. If possible, try whitelisting (allowing) SpyShelter.exe and sps_service.exe (located in C:\Program Files\SpyShelter\ui and C:\Program Files\SpyShelter folders respectively) with your VPN application if it allows it, this should resolve the issue.
I could try to send a request to the VPN support, but i’m with them for a long time already, and i assume i will get a default answer for this, but not many action from their side because everything in general is working like it should. Probably they will respond, ask SS support or something like this.
Well, since i didn’t see more VPN users joining for killswitch issues, i guess it’s a unique case. And as you stated, most likely there is no solution, so be it.
But if this is true, isn’t it weird that this is possible in the first place? How would a VPN be able to block SpyShelter from working correctly? Shouldn’t SS be designed in a way that this isn’t possible?
I was a bit surprised that with the killswitch enabled, the VPN intervened with SS, but i understand that a killswitch is certainly not flawless.
A killswitch has besides it’s intended purpose at times more strange behavior, hence i use it not to much.
For example with killswitch enabled sometimes it breaks the connection when downloading torrents, or connecting to some trading platforms or to certain websites fail as well.
Sorry for this issue. We will see if there is some solution, but some of our features like checking for malware or insights require the network.
However, we do have a privacy mode also as mentioned in our privacy policy:
"To activate the SpyShelter privacy mode, you should install SpyShelter from the Windows Terminal with the command SpyShelterSetup.exe /privacy. Once SpyShelter is installed in this privacy mode you will have no access to our Threat Detection, Insights, or any other SpyShelter features that require anonymized executable data to operate.
To leave the SpyShelter privacy mode you should reinstall SpyShelter again with the SpyShelterSetup.exe /clean command, and SpyShelter will once again have access to anonymized executable data, and will once again offer its full set of security features. We require this reinstallation so SpyShelter users cannot somehow accidentally begin sharing executable data when using our privacy mode.
If you have already installed SpyShelter in its default mode, you can go to the “Protection” tab and switch off “Threat Protection” and “Executable Insights” to stop sending executable data to SpyShelter at any time."
I’m not sure if our team tested in that mode to see if this issue still happens. I will see what I can find out.
As described in my previous response, although my logic’s say it’s odd that killswitch causes issues with SS, i know the flaws of the vpn killswitch as well.
In general it works ok, but i know from personal experience that using vpn killswitch sometimes has collateral damage as well.
I appreciate you want to investigate this further, but personally i think this is waste of time and energy. It’s up to you and the team…
It’s a bit confusing, because I thought you meant that SpyShelter was completely disabled and didn’t work at all anymore after the VPN killswitch was enabled? Or was it only certain parts that didn’t work?
Obviously, it would be normal that certain features won’t work anymore (with no network connection), but it seems that the topic starter said that SpyShelter didn’t work AT ALL anymore, so I hope he can clear this up.
Also, one of your developers said that perhaps SpyShelter’s GUI was blocked from communicating with SpyShelter’s system service, this should NEVER happen just because there is no network connection. So have you guys been able to reproduce this or what?