Thanks for your feedback. We will download Simplewall and tested it. If the proplem persists, please let me know.
Hi Lyx, If the uninstaller detects "WiseVector.exe" is running, it will prompt the user to exit it first. The problem seems to be that WVSX continues to execute after exit. For now it's hard to tell what the cause is. If you can reinstall WVSX, please exit it and then open Task Manager to see if "WiseVector.exe" is still active or not. Thanks.
the starting of WVSX is taking too long, after it has been closed by right clicking on the tray icon, it should be less than 1 minute
Hi lucd, Did you manually end "WiseVectorSvc.exe" by using any process manager after quitting WiseVector? If so, it will take some time to start the service again. But in any case, it should not take more than 1 minute
right click then end from menu (exit), maybe some wrong overclock on ram cpu but other programmes start fast and I don't have stability issues. I know how to OC. I also have Eset so double Av trouble may be it, I also use blackfog. I need eset because of compulsive site clicking ( I like to do research) and some bait sites use script injection. I know very well I should not be using WVSX with Eset or another AV, so when you release pro version? hopefully soon. I am afraid you don't understand, mine also takes 1 second to start: the GUI, but it is not fully functional but after 1 minute, try to do a scan it will most likely say : the service is starting..
WiseVector has been designed to be able to be used alongside other antiviruses, so it's fine to be using it with ESET. You will have heard that you should never run two antiviruses, but that is not the case for antiviruses which have been designed to be used with others. While you can use WiseVector by itself, there is an issue. Because as of yet, WiseVector does not register itself in Windows Security Center, Microsoft Defender will not be disabled. While you can disable MD's protection with Defender Control for example, most likely in time, MD will enable itself again. This isn't an issue if you another antivirus alongside WiseVector, as Windows will reognise the other antivirus and MD will stay disabled.
Thanks for a peek to the HIPS feature being considered. I will have more to say to that regard to the new beta rollout try since first HIPS intro introduced solid granular preferences to discover and cover in years it was high trend and reliable. Coupled with feature rich set already integrated w/reliabilty, it will add to better coverage IMHO.
@WiseVector Im curious as to what will happen with the free version... will it be maintained and updated?
Normally "WiseVectorSvc.exe" will not exit when you quit WVSX. It is recommended not to end the WiseVectorSvc.exe manually, otherwise you will have to wait for it to start next time。 The new version will be released soon!
In the new version, most features are free. We want to keep users safe even if they don't want to pay. Users can choose to pay for premium features or not.
@roger_m thanks roger , always nice informative answers WiseVector I right click exited WVSX because it was spiking at 30% cpu during work, that's why I thought it's no operative with ESET Maybe I should whitelist a couple of programmes because perhaps WVSX is looking at them with suspicious eyes and perfoming scans, I chose to close down manually because WSVX is slowing me down, maybe AI works for usual computer use (browse Internet, send email) but anything out of the ordinary and it spikes just threoretical assumptions I understand it's just much slower than any other AV restarting
At best there should be a 50% off offer for one year ( maybe a free year) for members who contributed to WV bugs and issues in this thread. Just because your a member of Wilders in no way shape or form should you get a discount. Hiltihome, I don't know if you contributed and found bugs in this thread or not.
@WiseVector - And anyone else using WVSX as only AV (it may exhibit same coupled) and ON WINDOWS 8.1 (not 10) On Windows 8.1 set Wise Vector Stop X Document Protection on Documents Folder. Now copy some common executables like a few Nirsoft Utilities or anything else you can click on to launch in that Documents folder protected with WVSX. Now execute one by one directly a few files and let run. On closing the file THEN and ONLY THEN Wise Vector Stop X Document Protection raises an ALERT- UNAUTHORIZED ACCESS BLOCKED- After you have already closed the executable. Please check this and confirm or deny your own results. It didn't prevent a manual launching from succeeding or using the same program nor alert until AFTER user closed app. THEN the ALERT popped up immediately AFTER user terminates single executable program. Just want to bring this up since it seemed odd to only get the Document Protection Alert box with the End task button AFTER the file is already manually closed by user action. Thanks Also @WiseVector- Does clearing the alerts recently logged in document protection log also RESET the WVSX Documents Protection anew? Or is there no difference. Cheers!
When a program starts, WVSX will scan the memory space of that program deeply to check any signs of malicious activity. When a file is created or changed, it will also be scanned, but the whole process will be fast. Unless a large number of new processes or files are created in a short period of time, in which case WVSX may consume high CPU.
@digmor crusher We will definitely offer discounts or free licenses to some enthusiastic users, but we should not offer lifetime licenses. Lifetime license is not a good ideal for a long-term business strategy.
Document protection is used to prevent programs from modifying files in the protected folder, not to prevent programs from starting. When you close a program in the protected folder, it may write a configuration file to the folder. This is why you will get the ALERT. Emptying the log has nothing to do with the documents protection settings. If you want to change documents protection settings, Open WVSX, click Settings->Advanced->Document Protection-> Set up. In the following 3.0 version, you can easily prevent a program from starting in a specific folder just by adding a rule.
@WiseVector - So right- It is those "attempts" at dropping/writing their config file WVSX protection is acting on. And in that respect I do not see where those files succeeded but Document Protections did. Thank You for your concise explanation
I create very large files very often, I work with large files, can I be impacted, normally an AV checks hashes, when I exit WVSX I am bit faster