Ghost Solution Suite

 View Only
Back to discussions
Expand all | Collapse all

Why is WinPE 5 not using the included VMXNET 3 driver that I put into the WinPE Configuration?

  • 1.  Why is WinPE 5 not using the included VMXNET 3 driver that I put into the WinPE Configuration?

    Posted Jul 17, 2015 11:29 AM

    Dear All,

    I have a VMWare ESX 5.5 server and I need to create a Windows 7 x86 machine that uses a VMXNet 3 NIC. I have an image from another PC, ready to be deployed.

    I harvested the VMXNet 3 driver from a working Windows 7 x32 VM machine and uploaded it into GSS 3.0 and regenerated the WinPE Boot option. I can see the drivers (x86 and x64) in the drivers list and in the file system. I can also see the files in the "\Windows\System32\DriverStore\FileRepository" of the Boot.wim.

    When the VM machine boots up, I still get the dreaded DHCP message. If I change the NIC to N1000, then the WinPE works.

    I need to create a machine with the VMXNet 3 NIC, but WinPE does not work with this driver.

    Can anyone help me, please?

    Kindest regards,

    QuietLeni



  • 2.  RE: Why is WinPE 5 not using the included VMXNET 3 driver that I put into the WinPE Configuration?

    Posted Jul 17, 2015 12:27 PM

    Have you tried loading the VMWare driver dynamically using DRVLOAD from a WinPE 5 command prompt just to validate absolutely that the issue is with the driver and not with the way it is being handled in the boot environment?

    I think you need to contact VMWare if their driver does not work with WinPE 5, as Symantec have no control over driver updates from VMWare, nor do they have control over WinPE 5 which is a Microsoft product.

    Have you posted your issue in the VMWare and/or Microsoft forums?

     



  • 3.  RE: Why is WinPE 5 not using the included VMXNET 3 driver that I put into the WinPE Configuration?
    Best Answer

    Posted Jul 20, 2015 11:32 AM

    Just worked out the answer... ...the PXE booted up the x64 WinPE 5, NOT the x86 version. The driver that was uploaded was only the x86 version and that was why the driver was not loaded.

    I deleted the x64 WinPE and it worked again.