Hitman Pro Support and Discussion Thread

I got rid of all of it, and even with the Beta, if you create the C: Progfiles/ ect in the default install location and schedule a scan, watch what happens, it's the same as installing. If I do it again I will post pics to show i know what I am saying, as it stands now I don't feel motivated given the current weirdness.

 

After launching of 3.7.20beta the first time, did you see "Do you want to install HitmanPro into Program files" ?
I have noticed it only with stable versions, but not with a beta:

I have tested it and it works.
Btw.: I guess you have copied the beta to Program Files? If yes, launch it, look at the window and you'll see: "HitmanPro 3.7.20 - Build 286 (64-bit)"
Now download the beta from their website, launch it and you can see that the word "BETA" is mentioned: "HitmanPro 3.7.20 - Build 286 BETA (64-bit)"

 

Thanks, mood.
I suppose, on details, CyberGhosT may have done differently than what you described in your posts #7590 and #7584.

 

+1
just maybe

 

Does 3.17.20 Build 286 FIXED: Right click scan (Scan with HitmanPro) mean I should have Shell Integration?

 

No, not if you run HMP 3.7.20.286 beta.
Running the beta does not install it, so it does not repair shell integration.
As soon as the new version is released as final, when you open HMP it automatically updates and shell integration is fixed. That will be in a couple of days, I hope.
If you really cannot wait, you could do as mood described in posts #7590 and #7584.

 

Well, I tried move and tried copy/paste the file HitmanPro_x64.exe to the location c:\Program Files\HitmanPro\HitmanPro.exe. and hmpshext.dll won't delete because it's open? and the Date modified with hmpshext.dll has not changed?

 

See details under a) and b) in mood's post #7584.

 

thought I followed a), b) & c) .... but, hmpshext.dll digital signature is still Mar 02.
So, I did something wrong?
Thanks

 

I cannot tell. I haven't tested mood's method, and also, I can't say whether or not you did anything different than what mood described.

 

You have to delete the old one (hmpshext.dll).
If it can't be deleted because it is in use, disable the Shell Integration in the settings and reboot. After a reboot it can be deleted.
After enabling of the Shell Integration with HitmanPro 3.7.20, the new file hmpshext.dll (Apr 06, 2017) can be seen in the directory.

 

agree

 

Yes, after reboot I was able to delete hmpshext.dll.
Shell Integration with HitmanPro 3.7.20 is greyed with check.
Maybe, I'll start over. I did not change reg auto-update.

 

HitmanPro 3.7.20.286 BETA

Spoiler: Early Warning Scoring

Code:

HitmanPro 3.7.20.286
www.hitmanpro.com

   Computer name . . . . : BJM-PCW10
   Windows . . . . . . . : 10.0.0.14393.X64/4
   User name . . . . . . : BJM-PCW10\bjms
   UAC . . . . . . . . . : Enabled
   License . . . . . . . : Paid (681 days left)

   Scan date . . . . . . : 2017-04-22 20:48:27
   Scan mode . . . . . . : EWS
   Scan duration . . . . : 5m 46s
   Disk access mode  . . : Direct disk access (SRB)
   Cloud . . . . . . . . : Internet
   Reboot  . . . . . . . : No

   Threats . . . . . . . : 0
   Traces  . . . . . . . : 2

   Objects scanned . . . : 1,616,570
   Files scanned . . . . : 25,466
   Remnants scanned  . . : 275,063 files / 1,316,041 keys

Early Warning Scoring _______________________________________________________

   C:\WINDOWS\system32\drivers\hitmanpro37.sys
      Size . . . . . . . : 55,232 bytes
      Age  . . . . . . . : -0.0 days (2017-04-22 20:48:27)
      Entropy  . . . . . : 6.9
      SHA-256  . . . . . : 7DE39018166AE4341FACD9B6E7854C46922FAD5E8BD96C64DAC9F54259B93150
      Product  . . . . . : HitmanPro 3.7
      RSA Key Size . . . : 2048
      Service  . . . . . : hitmanpro37
      LanguageID . . . . : 0
      Authenticode . . . : Valid
      Fuzzy  . . . . . . : 6.0
         Time indicates that the file appeared recently on this computer.
         Authors name is missing in version info. This is not common to most programs.
         Version control is missing. This file is probably created by an individual. This is not typical for most programs.
         The file is located in a folder that contains core operating system files from Windows. This is not typical for most programs and is only common to system tools, drivers and hacking utilities.
         Starts automatically as a service during system bootup.
         The file is a device driver. Device drivers run as trusted (highly privileged) code.
         Program is code signed with a valid Authenticode certificate.
      Startup
         HKLM\SYSTEM\CurrentControlSet\Services\hitmanpro37\

 

You're right. Loses connection altogether? A scan that ordinarily takes 45 seconds took over 3 minutes, with a " no connection to scan cloud" message. Wonder what's going on. This snip shows the scan that was stuck on an Audio .dll for over 2 1/2 minutes.

 

It actually doesn't scan that file, it just shows last file that was scanned. It seems that after scan it tries to connect to their server but for some reason it can't.

 

noticed inability to connect to the scan cloud, also. hmp is trying to check some files. I hope this is fixed soon.

 

No this was what it got stuck on during scanning:

Then in addition, it couldn't upload the AdwCleaner false positive to its cloud. It's having general connection problems, it seems.

 

Now this happens to me too.
After HitmanPro has found a suspicious file, i clicked on "Upload" (I don't want HitmanPro to automatically upload all unknown suspicious files) and i was able to see: "No connection to Scan Cloud"

 

Yes it got stuck on my system also (with other file displayed under the progress bar). I just wanted to point out that file displayed under progress bar is probably not actually being scanned during this pause. It just shows the last file that it scanned and it would be different file for different user/system.

 

@CyberGhosT.
I had pretty much the same experience. After uninstalling 3.7.18 with Revo advanced settings and making sure no remnants where left, I shut down the computer. Did a cold start and apply the 3.7.20 beta exe provided from @mood link.
The exe did install 3.7.20 also, not just run it. As in your case once I did a on demand scan, the installed version reverted to 3.7.18.
BTW no shell integration available.

I repeated the all above process again.
Now both installed and folder exe. shows the shell integration feature. Though it is not running a scan at startup as per my preference settings.
A "beta" sure it is...
Let's see what happen if I run a on demand scan again.
I'll let you know.

 

#7622 continued:

After on demand scan the installed version now is 3.7.20 (not beta) Shell integration is active.

From folder program, version 3.7.20 beta, shell integration is greyed out.

After reboot no scan at startup.

At least now I have shell integration, fingers crossed...

 

HMP is showing early stages of abandonware.

 

Hmm, nice if HitmanPro developers drop us a brief line or something on both products, it seems there's a little neglect right now. I see product revamping is in the works for maybe the past 3-4 weeks (?) but no official words.

Yes, it varies among machines and given scans, right? Mine was just an example.

 

[OT] I cannot speak on behalf of SurfRight, just only telling that it is vacation time in The Netherlands. Many folks are having a vacation; whether that goes for Mark and Erik, I don't know.