Share via

Does Credential Guard conflict with antivirus programs?

Anonymous
2024-12-27T06:02:39+00:00

Credential Guard is enabled by default in Windows Server 2025. Does this feature conflict with antivirus programs? How does it operate, and are there any known compatibility issues?

Also, what is the compatibility of Credential Guard with Hyper-V virtual machines and virtualization services?

I encountered a credential warning when using Live Migration in Hyper-V to move a virtual machine from one host to another. Could this issue be related to Credential Guard?

Windows Server High availability Virtualization and Hyper-V

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-12-30T06:02:50+00:00

    Hi,

    Credential Guard is a security feature in Windows Server that helps protect domain credentials and other secrets from attacks such as pass-the-hash. It operates by using virtualization-based security to isolate secrets and prevent unauthorized access.

    Regarding compatibility with antivirus programs, Credential Guard should not conflict with most antivirus programs. However, some antivirus programs may require specific configuration changes to work correctly with Credential Guard. It is recommended to check with your antivirus vendor for guidance on configuring their product to work with Credential Guard.

    Credential Guard is compatible with Hyper-V virtual machines and virtualization services. However, it is possible that the credential warning you encountered during Live Migration could be related to Credential Guard. It is recommended to check the event logs on both hosts to determine the cause of the warning. If the issue persists, you may need to disable Credential Guard temporarily to troubleshoot the issue further.

    0 comments