Why does the MetaDefender Core Deployment ID change after rebooting a Hyper-V VM?

This article applies to all MetaDefender Core releases deployed on Hyper-V.

Issue:

After rebooting a MetaDefender Core virtual machine hosted on Hyper-V, the Deployment ID may change unexpectedly. This behavior is typically caused by the VM’s network adapters being configured with dynamic MAC addresses.

In Hyper-V environments, dynamic MAC addresses can be reassigned during a reboot, resulting in a different MAC address.

Since MetaDefender Core generates its Deployment ID based on hardware identifiers such as the MAC address, any change to the MAC address will lead to a new Deployment ID being created.

How to Check MAC Address Settings in Hyper-V

To verify whether your VM is using dynamic or static MAC addresses:

  1. Open Hyper-V Manager on the host machine.
  2. Right-click the virtual machine in question and select Settings.
  3. In the left pane, expand the VM name and select Network Adapter.
  4. Click on Advanced Features.
  5. Check the MAC Address setting — if it is set to Dynamic, it may change after a reboot.

If your VM has multiple network adapters, repeat the steps for each one.

To prevent the Deployment ID from changing after a reboot, configure the MAC address of each network adapter to Static. This ensures that the MAC address remains consistent across reboots, maintaining the same Deployment ID.

If Further Assistance is required, please proceed to log a support case or chatting with our support engineer.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Next to read:
How to Use a RAMDISK for the tempdirectory?
On This Page
Why does the MetaDefender Core Deployment ID change after rebooting a Hyper-V VM?How to Check MAC Address Settings in Hyper-VRecommended Solution