Same. Installed over 2.73. @WiseVector Please can you supply that link again describing the different firewall levels , etc.? Can't find that post. Left it on 'Automatic' for now ...
I can visit our site without problems Anyway, the change log is: 1. Fix the issue that the program may crash under certain circumstances. 2. Fix the issue that may cause computer freezes. 3. Fixed a bug in firewall driver that may cause BSOD. 4. Fixed the high CPU usage when the network traffic is high. 5. Fix the problem that the software updates may fail under Windows XP system and also optimized resource usage in XP. 6. Optimized the firewall for maximum performance. 7. Now only prompt once for the same malicious DNS queries, to avoid too many popups. 8. Other bug fixes. Download at: https://update2.wisevector.com/WiseVector_StopX_V30.exe
Introducing the Firewall level and HIPS level Starting from WiseVector StopX 3.0, we decided to give more options to advanced users, who can write their own rules and adjust the security level to get personalized protection. Firewall Level: Block All: Blocks all network activity, recommend choosing when you walk away from your computer for a long time or if your computer is infected. Maximum Security: Whitelisted programs will be allowed to access the network. The user will be prompted to allow or deny the connection for all other programs, including Microsoft's own programs. This mode has most pop-ups. It is recommended for experienced users. High Security: Whitelisted programs will be allowed to access the network. The user will be prompted to take action for programs that are identified to be moderately suspicious by AI. Automatic mode: Whitelisted programs will be allowed to access the network. The user will be prompted to take action for programs that are identified to be highly suspicious by AI. Low-level Security: It relies entirely on the AI's independent judgment, and basically there will be no pop-ups. Rules-based mode: Only match the rules written by the user, the connections will be allowed if it does not match any rule. HIPS level: All risky behaviors will be analyzed by the AI first, and if they are determined to be malicious, they will be terminated directly without prompting the user. Those events that are not automatically processed will proceed to the following levels, Maximum Security: This is the strictest mode, which is very similar to the Default Deny mode provided by other security software. Where all risky behaviors are prompted to the user except for whitelisted programs. For example, running untrusted programs, running scripts, running PowerShell, creating startup items, creating scheduled tasks, accessing user's private data, accessing the camera, etc. In this mode, there are many pop-ups, so it is recommended for experienced users. High Security: Whitelisted programs will be allowed. The user will be prompted to take action for programs that are identified to be moderately suspicious by AI. Automatic mode: Whitelisted programs will be allowed. The user will be prompted to take action for programs that are identified to be highly suspicious by AI. Low-level Security: The AI will judge the behavior completely by itself, basically there will be no pop-ups. Rule-based mode: Only match the rules written by the user, the action will be allowed if it does not match any rule.
Just installed this beta, it says - Firewall, what firewall? I can not see one and thoose options about it that is present, how do they work? What do they do? Enlighten me please.
Since it has not got a FW on its own, does it mean that it works in conjunction with the inbuilt or FW in use? For short, how does this work when there is no FW present in WVSX?
This v3.01 beta version seems to work fine, compared to the initial beta release... However, I get this every time, and also previously, when I tried to run the previous version. So, I am sure it has something to do with WVSX. At least, it doesn't seem to prevent WVSX [from] running, now.
An hour after installing 3.01 my internet connection dropped. Same situation as reported with 3.0. This is through iVPN wireguard connection. Reinstalled 2.73.
Oh oh. Thanks for sharing an issue. That's very important. Is that result from a Windows 10? I want to assume it is but some also run Windows 8. Thank You
Pretty close to an hour. It was an hour and 10 minutes between the time I downloaded 3.01 and the time I downloaded 2.73 to reinstall. This happened repeatedly with 3.0, but it took much longer to drop the connection. Somewhere in the neighborhood of 6-8 hours.
I suppose that's possible, but if you read Wisevector's response to my earlier post about it happening in 3.0, they said they had identified the problem. And anecdotally after having the problem occur several times with 3.0 installed, and reinstalling 2.73, it did not occur again. .
I am running my first quick scan in WVSX in beta v3.01... @WiseVector I just noticed these two DMP files from in C:\Program Files (x86), dated July 8 and July 11, respectively. I don't know if you want to have them, as they were created under beta v3.00.
@GPM: Loosing a VPN connection can be caused by the router, closing the tunnel/port-forwarding. Maybe WVSX blocks some sort of keep-alive.
Don't know. All I know is that only this computer lost connection, this time and the others with 3.0. Other devices, including another Windows 10 machine running the iVPN app without Wisevector did not lose connection. As I said they acknowledged the problem earlier, with another VPN app as well and they said it would be fixed in 3.01. I'll just wait to hear from them. If they think the problem should be resolved I am willing to reinstall and test further.
Yes, I had described a problem with my Windscribe VPN, but since installing WVSX about 7 hours ago, I haven't activated the VPN. Just waiting to see how WVSX goes, before I try it with Windscribe active.