Hitman Pro Support and Discussion Thread

Anyone know why HMP does not start after missing the time window that was scheduled?

For example, daily at 8:00 AM. If you boot your system the first time for the day at say, 9:00 AM, HMP will not start. As far as I can tell, this happens on XP as well as Win7. Do others see this too or is it just me?

Al

 

Hi erikloman

I have Hitman pro on both my laptop and my pc
how ever since last up date,

Hitman pro on my labtop is detecting Rollback Rx as a Bootkit
When I uninstall Rollback Rx and do a scan no detection of Bootkit
When I reinstall it Detection is back ,

Program from horizon datasys . com site
Version: 9.1

Build: 2696720400

 

Report it as a false positive and wait for the file to get whitelisted

 

Cool I thought it was false positive , as my other scanners don't detect anything,

 

HitmanPro performs a diff between sector 0 (MBR) and the MBR served by Windows (under control of Rollback RX). If they differ then this is an indication that something fishy is going on (rootkit like activity). TDL4, Pihar, Sinowal do the same thing.

Its a heuristic detection. We'll roll an update in the next few days to work around the problem.

Thanks for reporting!

 

HitmanPro doesn't run when it missed its window. We will address this in the next update. Thanks for reporting this again (it slipped my attention, sorry).

 

While you're at it.
Could you add a scan "at wakeup", not just at startup?

Thanks

 

After a /scanonly scan HitmanPro pops up to show the results even if nothing was found. Could you change the behavior or add another command so it does not pop up but stays in the tray.

 

It should not popup when you have a purchased license.

 

Release: HitmanPro 3.6 Build 152 BETA

HitmanPro 3.6 Build 152 BETA

Changelog

• NEW: Bitdefender logo.
• IMPROVED: Bootkit detection heuristic.
• IMPROVED: Direct Disk Access handling.
• IMPROVED: Handling of GPT disks.
• IMPROVED: Scheduler starts a scan when it has missed its time window (thanks Adric).
• IMPROVED: Scheduler performs Default scan when the last Default scan was at least 30 days ago.
• FIXED: Solved a problem where HitmanPro would keep scanning indefinitely.
• FIXED: Solved a problem where HitmanPro could not overwrite an existing activation license due to changed file attributes.
• FIXED: Solved a problem handling the license files.
• FIXED: Solved a problem handing the 'no proxy' setting.
• Updated internal white lists.

Rollback RX users should no longer see the Win32/Bootkit heuristic detection. Also these users should set HitmanPro to Compatible Disk Mode to prevent excessive report of Suspicious items due to the virtualization of the file system by Rollback RX.

If you want to run this beta as a final release then overwrite C:\Program Files\HitmanPro\HitmanPro.exe with one of the below downloads and add the following registry key:

HKLM\Software\HitmanPro\AutoUpdate REG_DWORD 0

The key should prevent the beta executable to revert to the current version.

Please report any issues and/or performance degration/improvements. Thanks

Happy Easter!

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

 

Re: Release: HitmanPro 3.6 Build 152 BETA

From your link 32-bit I'm getting the 3.6.0.148 version, not the beta

 

Re: Release: HitmanPro 3.6 Build 152 BETA

Sorry. Wrong link posted . Post updated with new link!

 

Re: Release: HitmanPro 3.6 Build 152 BETA

Thank you.

 

Re: Release: HitmanPro 3.6 Build 152 BETA

I just downloaded a couple of minutes ago, and got the same.

 

Just got the the one FP from Safe Returner...had this software on my system for more than a year.

 

Should be solved now. Found some more FP submits that were pending to be processed. Thanks!

 

All clear.

 

Downloaded and ran 32-bit beta. Smooth here. Bitdefender

 

It flags OpenDNS DNSCrypt software application as Suspicious. I reported it as being safe.

dnscrypt-proxy.exe: SHA-256 9188777B7F1E6A21BCF014265EB80EE5F0E3E9E0A7B96A51ABA19350C9F19AEF

You can download it from here: -https://github.com/downloads/opendns/dnscrypt-proxy/dnscrypt-proxy-win32-0.9.3.zip

 

Bitdefender has always been there (in GData)

 

It also detected EAZ-FIX shield as rootkit,as well, yesterday.

I believe its FPs and ignore it... waiting for fix.

 

Can you try the Build 152 from this post:
https://www.wilderssecurity.com/showpost.php?p=2038851&postcount=4190

 

just tested build.152 and still showing SHIELD of EAZ-FIX as Bootkit/Rootkit
it also flagged MBAM.sys,MBAMswissarmy.sys and Chrome_updater.exe as Suspicious

 

Odd. 152 should help as Rollback RX issue was also solved by 152. I will test EAZ on my part.

About the Suspicious files, they are caused by EAZ due to the virtualisation of the file system. Switch HitmanPro into Compatible Disk Access under Settings > Advanced. Please let me know if this helps.

 

I figured it out. In Build 152 you HAVE TO set HitmanPro in Compatible Disk Access mode when you run EAZ-FIX or Rollback RX (both programs are identical btw as per here).
This is needed because EAZ-FIX/Rollback RX hides files from Windows. But the files are actually there on the disk and are available specific in EAZ snapshots. Since HitmanPro parses the NTFS on-disk structures (instead of asking Windows for the files) it stumbles on the snapshotted files that are not visible by Windows.

I will see if I can slip automatic detection of either of these applications (and a few others listed here) in HitmanPro so the end user doesn't have to turn on Compatible Disk Access by hand.

Hope this helps.