#1 Global Leader in Data Protection & Ransomware Recovery

VMXNET3 Drivers Missing From Recovery Media for Server 2022 vSphere VM

KB ID: 4506
Product: Veeam Agent for Microsoft Windows | 5.0 | 6.0 | 6.1
Published: 2023-10-26
Last Modified: 2023-11-01
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

When attempting to perform a Bare Metal Restore on a vSphere VM using Veeam Recovery Media, which was created from a vSphere VM running Server 2022, the network adapter drivers fail to load. This issue persists despite having the 'Include hardware drivers from this computer' option enabled.

Note: This issue often appears in scenarios where VMXNET3 network adapters are used.

Cause

The exact cause remains under investigation and will be resolved in a future version.

Solution

To work around this issue:

  1. Recreate the Veeam Recovery Media
    1. On the Recovery Media tab of the Recovery Media creation wizard, select the option to "Include the following additional storage and network hardware drivers."
    2. Add the VMware Drivers folder:
C:\Program Files\Common Files\VMware\Drivers
Enable
Browse
Select
  1. Perform the Bare Metal Restore again using the newly created Recovery Media.
  2. During the Bare Metal Restore, on the 'Backup Location' tab, load the manually inserted NIC drivers:
    1. Click 'Load Driver'.
    2. Select the Ethernet Controller.
    3. Browse to the driver's location on the recovery media and select the driver:
      VMXNET3 — X:\Drivers\Drivers\vmxnet3\Win8\vmxnet3.inf
    4. Perform the same for any other devices that may be missing their VMware driver.
  3. Proceed with the restore.

More Information

If Veeam Backup & Replication is also installed in the environment, another option is to perform Instant Recovery to VMware vSphere.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.