While performing Windows OS patching and VM Tools patching simultaneously, a VMXNET3 adapter or other device may no longer appear in Windows post reboot
search cancel

While performing Windows OS patching and VM Tools patching simultaneously, a VMXNET3 adapter or other device may no longer appear in Windows post reboot

book

Article ID: 416139

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Windows OS patching and VM Tools patching was being performed simultaneously and the system was rebooted during the VM Tools update. After the reboot the network adapter was no longer present.

Environment

ESXi 8.0.3

Windows Server 2022

VMware Tools 12.5.2.52591 (build-24697584) and 13.0.5.0 (build-24915695)

Cause

The VMware Tools update removed the vmxnet3 device and failed to reinstall it due to a system shutdown from the other updates. This could happen with any device and not just vmxnet3.

Reviewing setupapi.dev.log and vminst.log showed the following:

In C:\windows\INF\setupapi.dev.log you see the following:

!!! dvi: Error 1115: A system shutdown is in progress.
!!! dvi: Error while installing services.
!!! dvi: Error 1115: A system shutdown is in progress.
!!! dvi: Cleaning up failed installation
!!! dvi: Error 1115: A system shutdown is in progress.
     dvi: {Install DEVICE exit (0x0000045b)}
!!! dvi: Cleaning up failed installation (0000045b)
!!! dvi: Default installer: failed
!!! dvi: Error 1115: A system shutdown is in progress.
     dvi: {DIF_INSTALLDEVICE - exit(0x0000045b)} 17:41:34.725
!!! dvi: Error(0000045b) installing device!
...
     ump: {Plug and Play Service: Device Install exit(0000045b)}
!!! ndv: Device install failed for device.
!!! ndv: Error 1115: A system shutdown is in progress.
     ndv: Installing NULL driver.
    ump: {Plug and Play Service: Device Install for PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\#################}
! dvi: Installing NULL driver!
     dvi: {Core Device Install} 17:41:34.741
     dvi: {Configure Device - PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\#################} 17:41:34.741
     dvi: Device Status: 0x0180600a
     dvi: Config Flags: 0x00000400
    dvi: Parent Device: PCI\VEN_15AD&DEV_07A0&SUBSYS_07A015AD&REV_01\##################
     dvi: Install Device: Configuring device. 17:41:34.757
     dvi: Configuration: null
     dvi: Install Device: Configuring device completed. 17:41:34.757
     dvi: Device Status: 0x0180600a
    dvi: Install Device: Removing device 'PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\#################' and sub-tree. 17:41:34.757
     dvi: Install Device: Removing device sub-tree completed. 17:41:34.835
     dvi: Install Device: Restarting device. 17:41:34.835
     dvi: Install Device: Restarting device completed. 17:41:34.835
! dvi: Device not started (unknown reason): Device has no problem.
     dvi: {Configure Device - exit(0x00000000)} 17:41:34.835
     dvi: {Core Device Install - exit(0x00000000)} 17:41:34.835
     ump: {Plug and Play Service: Device Install exit(00000000)}
     ndv: {Update Device Driver - exit(0000045b)}
!!! ndv: Failed to install device instance 'PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\#################'. Error = 0x0000045b
<<< Section end 2025/10/18 17:41:34.835
<<< [Exit status: FAILURE(0x0000045b)]

 

In C:\Windows\Temp\vminst.log you see the following:

tools-build-24915695| I1: PnpDriverManager::EvalUpdateNeeded: Determined that vmxnet3 is newer
tools-build-24915695| I1: PnpDriverManager::EvalUpdateNeeded: Prior vmxnet3 info:
tools-build-24915695| I1: DriverVersionInfo::Print: Driver version (valid) 1.9.19.0 is WHQL (ca ver 1) inf "oem5.inf"
tools-build-24915695| I1: PnpDriverManager::EvalUpdateNeeded: New vmxnet3 info:
tools-build-24915695| I1: DriverVersionInfo::Print: Driver version (valid) 1.9.20.0 is WHQL (ca ver 1) inf "vmxnet3.inf"
tools-build-24915695| I1: DriverVersionInfo::Print: Driver version (valid) 1.9.20.0 is WHQL (ca ver 1) inf "vmxnet3.inf"
tools-build-24915695| I1: DriverBaseInfo::DeleteFromRegistry: No info for driver vmxnet3ndis5 to delete
tools-build-24915695| I1: DriverBaseInfo::DeleteFromRegistry: No info for driver vmxnet3ndis6 to delete
tools-build-24915695| I1: PnpDriverManager::InstallDriverImpl: Installing new version of the vmxnet3 driver
tools-build-24915695| I1: DriverBaseInfo::DeleteFromRegistry: Deleted info for driver vmxnet3
tools-build-24915695| I1: DriverBaseInfo::DeleteFromRegistry: Deleted info for driver vmxnet3
tools-build-24915695| I1: Util_GetKeyValueDWORD: Cannot query key value HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\vmxnet3ndis6\DeleteFlag| winerror code 2 (The system cannot find the file specified.)
tools-build-24915695| I1: PnpDriverManager::InstallPnPDevices: Installing driver with INF: "C:\Program Files\Common Files\VMware\Drivers\vmxnet3\Win10\vmxnet3.inf", flags: 1
tools-build-24915695| I1: PnpDriverManager::InstallPnPDevices: Inf file C:\Program Files\Common Files\VMware\Drivers\vmxnet3\Win10\vmxnet3.inf was installed as oem5.inf (full path C:\Windows\INF\oem5.inf)
tools-build-24915695| E1: PnpDriverManager::InstallPnPDevices: Failed to install vmxnet3 driver| winerror code 1115 (A system shutdown is in progress.)

Resolution

Reinstall VMware Tools and keep VMware Tools updates/installs separate from other patching

Additional Information

Useful logs:

  • C:\Windows\INF\setupapi.dev.log
  • C:\Windows\Temp\vminst.log
  • C:\Windows\Temp\vmmsi.log

Enabling debug logging for VMware Tools within a guest operating system