We'd love to hear about it! Click here to go to the product suggestion community
After update EAP Intercept X my virtual machines do not start. I have a information like this:
After uninstalling intercept x virtual machines started to run. (The same situation is with my other computer with HitmanPro.Alert but after reinstall of hitman virtual machines was starting)
Problem is with start vmcompute.exe process. I have exceptions form executables from Hyper-V and folders containing data of virtual machines.
Hi Tom, thank you for logging this. Our engineering team is looking into this.
In reply to Pedrode Barros Jose:
Do we have any acknowledgement of this issue, work arounds or ETA on an actual solution to this problem??
In reply to Vini:
I have had a ticket open with them since 11/2 and there has been another thread running on this since August 25...
In reply to Kyle Parrish:
From tests performed;
Looks like a rather vague KB article relating to this has been published @ https://community.sophos.com/kb/en-us/127797.
Solution? Please contact Support for the work around.
I tried this exception, but it didn't make any difference.
We're having the same issue on two PCs here, and the only way we can get it working is by uninstalling sophos.
In reply to Ashley Hurst:
I've same issue, does anyone fixed the bug?
In reply to Jose Batista:
Installing Sophos without the Intercept-X component works. Certainly on the Enterprise side of things.
It's not really an acceptable solution, but it works.
According with this KB127797 there is a workaround to exclude the process that cause the issue.
Anyone has access to this workaround?
You guys want to come over to this thread --> https://community.sophos.com/products/sophos-home/f/sophos-home-for-windows/95353/sophos-home-beta-windows-10-fall-update-insider-hyper-v-issue/355238#355238
I'm trying to prise the workaround from Support, but they won't escalate my ticket without logs, which I've just sent today.
Other suggest the workaround is to exclude 'vmcompute.exe' from the Policies, but that doesn't help in my case (nor anyone elses by the looks).
I had already exclude the 'vmcompute.exe' process in Threat Protection Policy, but vm start still failing.
I think the exclusion in this policy will not help. The problem is with hitmarpro.alert. For this purpose, it is done in another place https://cloud.sophos.com/manage/endpoint/config/settings/exploit-mitigation-exclusions
But there you can not select items related to the process vmcompute.exe Hyper-V. Entry can be made by Sophos or if InterceptX detects this process as malicious and will be available in the event.
I have exclusion for Skype fo Bussiness because I have a problem with video call.
In reply to TomKor:
Great TomKor, looks like nobody in Sophos or Support Staff are pending about this topic.
Can you download a more current build of HMPA and retest.
Place the executable in the HMPA folder. For example C:\Program Files (x86)\HitmanPro.Alert
To upgrade your EAP1 to 723, just open a command prompt as administrator and run: hmpalert3b723.exe /upgrade
Don’t forget to reboot the machine and you’re good to retest.
This build is still in validation, but as you are on the EAP, we are giving you early access to it. We believe it should address the issue. As normal, we recommend that you only deploy this build to your endpoints on the EAP.
Let us know how you get on.
After the update HitmanPro.Alert finally the virtual machines started.Thank you for your help