Hitman Pro Support and Discussion Thread

Defrag of the computer reduced the scan time to normal. I definitely defragged it a few days ago though. Strange this occured so quickly after that

 

Okay, glad you are back to normal.

 

Re: HitmanPro 3.6 Final - Build 137

Is this version suppose to update automatically from 3.5.9 build 131? I'm guessing not since it hasn't for me or I have something wrong.

 

Re: HitmanPro 3.6 Final - Build 137

It won't auto-update until the next build release, due to localizations I believe.

 

Is Hitman wrong on SHELL32.DLL and ieframe.dll? Or is this a false positive or what?


http://imageshack.us/photo/my-images/716/64627845.png/

 

Have you modified either with Resource Hacker or similar?

 

http://imageshack.us/photo/my-images/402/13567449.png/
i have to allow hitmanpro cause it was getting block by webroot

 

I sincerely apologize if this has been asked & answered...

How effective is Hitman Pro in the sense that it is using "watered down" versions of the real AV engines? Or is it not using "watered down" versions? I know that was the case with Prevx 3.0, but is that the case with the other engines it is using today? And by "watered down" I mean like...just using their signatures...or just using one part/component of their protection engine, etc...

Does it really find a way to incorporate the entire protection of the product it is using? How is that possible with a 3 minute scan from 4 vendors?

I ask this because a lot of people (especially lately) are cracking down on services like VirusTotal that do not really give a good reflection on the said product's detection. I am not certain by any means if the same applies to Hitman Pro. I certainly hope not, because I love it.

 

Prevx 3 is gone on HitmanPro 3.6.
It doesn't use "watered down" versions. HitmanPro analyzes most malware-targeted locations using a behavioral engine for malicious patterns and it classifies them, if found suspicious, the file is sent to the cloud to see if it matches a signature.
It's an on-demand scanner, so it doesn't run all the time, there's no way one can expect it to use a protection engine...

 

No i havnt,you think they are suspect then?

 

You run in EWS. You run in this mode only if you suspect an infection.
The files are likely recently updated by Microsoft. Thats why they are listed (I think). Choose More Information from the drop down at the end of the row to see why it was flagged.

Hope this helps.

 

I think this is an FP. 2/43 on VirusTotal. Being flagged by

Emsisoft Trojan-Spy.Win32.Zbot!IK
Ikarus Trojan-Spy.Win32.Zbot

It's a switchless installer for Java 7 Update 03

 

Can you send me the SHA256 or the actual file?

 

HitmanPro 3.6.0 Build 140 Beta

HitmanPro 3.6.0 Build 140 Beta

Changelog

• Improved removal of new 64-bit variant of ZeroAccess (aka Sirefef).
  This new variant re-infects the SubSystems registry key on reboot using Netsvcs.
• Improved Crusader (HitmanPro's malware removal engine) that now blocks malware watchdogs trying to redeploy while being removed.
• Re-added the languages from HitmanPro 3.5.
• Added Slovak language
• Added Serbian language
• Added Bengali language
• Several small fixes

What's coming in the next build(s)

• Fixed VirusTotal integration. Currently not working properly due to excessieve slashes in the URL. A fix has already been checked in.
• Volume Boot Record scan and repair.
• ... (your suggestion here) ...

32-bit: -http://dl.surfright.nl/HitmanPro36beta.exe-
64-bit: -http://dl.surfright.nl/HitmanPro36beta_x64.exe-

Please let me know how this version runs. Is it running faster, slower or is it causing problems. Thanks

PS. In the past weeks we've been improving our Scan Cloud. In addition we are in the progress of adding more Remnants to the cloud. More on this next week.

 

running very smooth here no problems at all
good job Erik

 

No problems here. Scan was smooth maybe a few seconds faster.

 

Sorry about that. I forgot to include it with my post.

6cfe033cdc0734ae5ac2267fd02abdda3b499d5666641a0eb60ee89688864407 ?SHA256*java7u03.exe

Al

 

Thanks! Should be fixed now.

 

No probs here. Just scanned on two win 7 machines. Both scanned in about 1 minute 30 seconds.

 

Just did a couple of scans for comparison. Seems the Build 140 runs a little slower on my system.





BTW, I don't recall seeing a Build 139 beta. Just wondering.

 

No problems here. Using early warning scoring, 64-bit Build 138 scanned in 1m 44s, new version scans in 1m 40s.

 

Hi

Any News for the update from 3.5 to 3.6 Release date

 

Yes. Scheduled for next week.

 

any future plans to implement real time protection?

 

Thank you very much for your Info about it