Virtual machines don't start after EDR Client is installed on Hyper-V

Technical Articles ID: KB94074
Last Modified: 2023-07-03 07:01:38 Etc/GMT

Environment

Endpoint Detection and Response (EDR)

Problem

After you install the EDR client on your Hyper-V server, you see that your virtual machines (VMs) can't be started.

Solution

Trace process exclusions are required for VMs to run on Microsoft Hyper-V. Add the following exclusions to the Trace Policy in the EDR Client extension:

Vmms.exe (%systemroot%\System32\Vmms.exe)
Vmwp.exe (%systemroot%\System32\Vmwp.exe)
Vmsp.exe (%systemroot%\System32\Vmsp.exe)
Vmcompute.exe (%systemroot%\System32\Vmcompute.exe)

For information about how to ignore processes within the Trace Policy, see the "Trace policy configuration" section of the Endpoint Detection and Response Product Guide.

For product documents, go to the Product Documentation portal.

Affected Products

Endpoint Detection and Response
Endpoint Detection and Response - All Versions

Languages:

This article is available in the following languages:

English United States
Spanish Spain
French
Italian
Portuguese Brasileiro

Knowledge Center

Virtual machines don't start after EDR Client is installed on Hyper-V

Environment

Problem

Solution

Affected Products

Languages:

Title

Title

Knowledge Center

Virtual machines don't start after EDR Client is installed on Hyper-V

Environment

Problem

Solution

Affected Products

Languages:

Choose your region

Title

Title