Discussion in 'other anti-malware software' started by bellgamin, Aug 10, 2020.
Thank you for your stellar support.
Hi, thanks for your report.
We have installed Acronis True Image 2021 and WVSX flagged "kernel.dat" as malicious.
Now it has been fixed.
Thanks for your suggestion.
We focus on improving technology nowadays, at the same time, we do not give up any opportunity to collaborate with others.
Acronis is almost like a virus if not an actual virus, very invasive with tons of services installed and still there after uninstall
I would avoid
Acronis was installed temporarily, to create a bootable USB-drive.
I already uninstalled it.
I have a small issue with getting WV to launch at startup.
WV does not start when I boot or reboot Windows and, yes, there IS an "X" in the following box of WV's settings: "Automatically launch at system startup."
This issue has existed since I first began using WV several weeks ago. However, I haven't reported the issue until now because I have been very busy with other matters. In the meantime, I have easily started WV manually each day by executing C:\Program Files (x86)\WiseVector\WiseVector.exe.
Today, however, I decided to try & streamline this manual start of WV by putting a copy of WiseVector.exe into the folder: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup.
When I restarted Windows, so as to test this work-around, WV did NOT launch. Instead I received the following pop-up message:
A quick check revealed that libcrypto-1_1.dll IS present in my computer's file folder at C:\Program Files (x86)\WiseVector. Moreover, the fact that WV readily starts manually makes it obvious that WV DOES have a valid libcrypto-1_1.dll file available.
By the way, i'm running Windows 7 and my computer is quite stable. My only other real-time security apps are Simplewall (a firewall) and SecureAPlus (an anti-exe, white-list app). This issue might (or might not) be unique to my computer but I thought you would like to know about it.
WiseVector won't run at startup unless you are using an Admin account. It's a known limitation. To get it to run at startup you would need to add a shortcut to the WiseVector exe file, rather than copying the file there. Hopefully that would work.
Have long respected and followed your posts Sir.
An earlier post in this thread suggested scheduling it as a task.
May I suggest here.
I am not a used, as the limitation with standard user accounts is a deal breaker for me.
Best of luck.
As roger_m said, WVSX can run at startup automatically when you are using an Admin account ( sorry for the inconvenience ). Please refer to the post here, #280.
Do you use a Standard account since you first began using WVSX? And please check if "WiseVector" is in your task scheduler library or not. Thanks.
I did as @roger_m suggested. Instead of putting WiseVector.exe into Startup folder, I put a shortcut to WiseVector.exe into Startup folder. WV now loads just fine at start & restart. Problem solved. 10Q to the nth, Roger!!!
@Feandur -- Aloha to you from Hawaii! Thanks for your kind comments.
@WiseVector -- Thanks for your speedy & informative reply to my issue. I have always run as an Admin account. Thus, according to that criterion, WV should have launched at startup because I selected that option in WV's settings.
Your comment #834 says (in part): "And please check if "WiseVector" is in your task scheduler library or not." Task Scheduler is disabled on my computer. I have dozens of apps that are set to launch at Startup and, despite the absence of Task Scheduler, they all launch just fine. Does WV depend on Task Scheduler in order to launch itself at Startup? If so, I'm sure you have excellent reasons for such a dependency.
In any event, Roger's work-around is simple to do & works splendidly so.... issue resolved. WiseVector is a magnificent security app. I am eagerly awaiting the paid version!
Software startet via task scheduler, can run at windows start.
Software started via startup folder starts at user logon.
So the latter delays protection.
Excellent information, @Hiltihome -- I have learned a new thing!
WVSX needs a Microsoft certified ELAM-driver, to start as first kernel mode-driver.
In this way it can start before any malware.
I expect such driver, as soon as the paid version is released.
Thanks for your feedback! We are working on some new features these days and the paid version will follow after then.
Thanks for your advice.
WVSX has Behavior Detection which can prevent suspicious driver from loading. If WVSX is installed and keeps working before a rootkit infection, the malicious driver will be blocked.
If the system is infected by a rootkit before WVSX is installed, the situation will be tricky, since the rootkit runs within ring 0 it can do almost anything including prevent users from installing any AV. On the other hand, ELAM-driver is useful for cleaning up if the malware infection is not serious. We will add it in the future.
It depends on you, if you believe that blocking exploits is important then HMPA is probably the best. However, WSVX is focused on blocking malware just like any other AV, so no matter if malware tries to run via some exploit it still should be stopped.
Separate names with a comma.