This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Intercept X issues

Trying to test run with Intercept X. I run the software on a MS Surface 3, Windows 10 AU. It looks like it is not possible to get Intercept running on this configuration without the disable of the secureboot feature because of the not signed drives Intercept wants to install. Very strange feeling to disable security features to install security software. After I re enabled the Secureboot feature I receive errors that the Hitmanpro service is no longer running. So only way for now is to keep secure boot disabled and keep Hitmanpro running.

Question is: why? any more people same experience? Is this product mature enough to sell to our customers? Why does it not have signed drivers?

This thread was automatically locked due to age.

0 jak over 8 years ago

I don't have it to hand but when were they signed? It could be significant as I think Microsoft changed some rules about the type of signing.

This might hold some clues:

http://www.thewindowsclub.com/driver-signing-changes-windows-10
https://blogs.msdn.microsoft.com/windows_hardware_certification/2016/07/26/driver-signing-changes-in-windows-10-version-1607/

Regards,

Jak
Cancel
Vote Up 0 Vote Down

Cancel
0 Aditya Patel over 8 years ago

HI hscholing,

Yes the issue is addressed with as a feature on Windows 10 AU as affects Hitman Pro , It would seem the issue was from Microsoft and have resolved with a latest update . If you are still facing an issue kindly mention your Windows Build.

Thanks and Regards

Aditya Patel

Regards,

Aditya Patel
Global Escalation Support Engineer | Sophos Technical Support
Knowledge Base | @SophosSupport | Sign up for SMS Alerts
If a post solves your question use the 'This helped me' link.
Cancel
Vote Up 0 Vote Down

Cancel
0 Ryan Arnold over 8 years ago

I am in the exact same boat, running Windows 10 AU(Build 10.0.14393) with latest patches from MS. I have the issues listed in the "Intercept-X Known Issues" knowledge base https://community.sophos.com/kb/en-us/124988#BSoD triggered after enabling Hyper-V role, Windows Biometrics or Credential Guard on Windows 10 Anniversary

I'm affected by the driver unassigned message and the BSoD. We just got our license keys yesterday and already 3 of my test machines cannot boot to Windows anymore. We exclusively run the AU build and as of now I purchased a product I can't even use. Is there an ETA on a fix for this? Pretty ridiculous that this is still an issue....
Cancel
Vote Up 0 Vote Down

Cancel
0 hscholing over 8 years ago in reply to Aditya Patel

Enabled secureboot again and problems are instantly back. My Windows version is 10.0.14393

Error states Hitman.pro alert service stopped

Any quickfix?
Cancel
Vote Up 0 Vote Down

Cancel