Vmware Others Driver Download For Windows

Download Windows 10 and all the tools you need to build for Universal Windows apps for tablet, phone, PC, Windows IoT, or Xbox on the Universal Windows Platform or Windows applications for the desktop.

  1. Vmware Others Driver Download For Windows 10
  2. Vmware Others Driver Download For Windows
  • Install VMware USB Pointing Device driver for Windows 7 x64, or download DriverPack Solution software for automatic driver installation and update.
  • Note: The Intel® USB 3.0 eXtensible Host Controller Driver is not supported on Windows XP. and Windows Vista. This is a new version release: Not sure if this is the right driver or software for your Intel® chipset? Run Intel® Driver & Support Assistant (Intel® DSA) to automatically detect driver or software updates.
  • The vmware administrator has several different virtual network adapters available to attach to the virtual machines. Subscribe my virtual nic installed, vmxnet3 driver. How to change the network adapter to vmxnet3 for a windows guest published. VMware Workstation Pro. It appears that you need a vm 9. In april this year, we launched vmware tools.

This article provides a workaround for an issue where you can't install a VMWare driver on a server that is running Windows Server 2008 R2 and that has the Telnet Server service installed.

Original product version: Windows Server 2008 R2 Service Pack 1
Original KB number: 3066752


Consider the following scenario:

  • On a computer that is running Windows Server 2008 R2, you add an Ethernet adapter to a VMWare vSphere environment.
  • The Telnet Server service is installed.
  • In the Services snap-in of the Microsoft Management Console (MMC), you configure the Telnet Server service to start manually or automatically.
  • In the Services snap-in, you configure the Telnet Server service to log on by using the Local System account. Additionally, you don't select the Allow service to interact with desktop checkbox.

In this scenario, when you try to install the driver through Device Manager, the attempt fails, and you receive the following error message:

Windows found driver software for your device but encountered an error while attempting to install it.

After the installation failure occurs, you try unsuccessfully to install another available Ethernet adapter from the VM Settings list. For example, you select Intel E1000. However, the second driver also doesn't install. Additionally, a log entry that resembles the following is logged in Setupapi.dev.log under %windir%/inf/:

dvi: {Plug and Play Service: Device Install for PCIVEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01FF565000B37984FE00}
ump: Creating Install Process: DrvInst.exe <DateTime>
ump: Server install process exited with code 0xc0000142 <DateTime>
ump: {Plug and Play Service: Device Install exit(c0000142)}
ndv: Device Install failed for new device...installing NULL driver.
dvi: {Plug and Play Service: Device Install for PCIVEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01FF565000B37984FE00}


This problem occurs because the Telnet Server service makes some security-related permission changes during initialization to the window station that it's running in. If you configure the Telnet Server service to run by using the Local System account without the ability to interact with the desktop, the service starts under a different window station. This may cause conflicts with other processes that also run under the Local System account and that don't interact with the desktop, such as the installation process for a new device driver.


To work around this problem, don't run the Telnet Server service under the Local System account. We recommend that you leave the Telnet Server service to run under its default Local Service account.

If this doesn't temporarily fix the problem, verify that the latest version of VMWare Tools is installed. If you can't update or uninstall VMWare Tools, follow these steps:

  1. Obtain the setup files for the latest version of VMWare Tools.

  2. Click Start, type cmd in the Start Search box, and then click OK.

  3. At the command prompt, change the drive to your CD-ROM drive (For example, drive D).

  4. Type setup /c, and then press Enter to force removal of all registry entries and delete any previous versions of VMware Tools.


    For 64-bit guest operating systems, type setup64 /c instead.

  5. Install the latest version of VMWare Tools.

  6. Verify that the Telnet Service logon setting is set correctly.

  7. Restart the server.

Third-party information disclaimer

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.


This document describes how to install device drivers on the Cisco Unified Computing System (UCS) for common operating systems.



Cisco recommends that you have knowledge of these topics:

  • Cisco UCS Manager
  • Cisco Integrated Management Controller (CIMC)
  • Virtual Machine-ware (VMware), Windows Server, or Linux Operating Systems (OS)

Components Used

The information in this document is based on these hardware platforms:

  • UCS B Series
  • UCS C Series

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Background Information

Driver Definition

A device driver is software that is the interface between the OS and the hardware. The device driver translates general OS commands into specialized commands for a particular device, which allows the OS to communicate with hardware devices.

Devices that Require a Driver

Here is a list of hardware devices that require device drivers:

  • Ethernet Network Interface Card (ENIC)
  • Fibre Channel Network Interface Card (FNIC)
  • Redundant Array of Indepent Disks (RAID) Controller
  • Motherboard Chipset
  • Video Card
  • Trusted Platform Module (TPM)

Drivers Versus Firmware

Device drivers are different from firmware. Device driver software is installed on the OS, whereas firmware is lower-level code that is installed on hardware devices. Firmware is stored in non-volatile memory, such as ROM, Erasable Programmable ROM (EPROM), or flash memory.

Driver Dependence on Firmware

Device drivers have a strong dependence on the device firmware. Device drivers must be compatible with the firmware level of a hardware device, so that they properly communicate with each other; driver and firmware functionality must match for correct operation to take place.

When Drivers Must be Installed and Updated

Device drivers come pre-installed with operating systems (such as Cisco OEM VMware ESXi images), or they can be manually installed post-OS setup.

Device drivers generally need to be updated after these procedures:

  • UCS firmware upgrades
  • Major OS upgrades/patches
Vmware Others Driver Download for windows

Driver Versions Required

The UCS Hardware and Software Interoperability matrix outlines the driver versions that are required for a particular OS, device, and firmware combination.

Warning: The driver versions listed on the matrix have been tested and verified by the Cisco Engineering Quality Assurance team, and it is crucial to install the correct driver; otherwise, you might run into unexpected behavior which could lead to network outages.

This example shows that an FNIC driver version of is required for a B200 M4 with a Virtual Interface Card (VIC) 1240 that runs ESXi 6.0 U3, on UCS Release 3.2.2.

Download the Driver Bundle

Complete these steps in order to download the driver bundle:

  1. In a web browser, navigate to http://www.cisco.com.
  2. Under Support, click Download Software.
  3. Click Unified Computing and Servers.
  4. Choose your server. Cisco UCS drivers are available for both Cisco UCS B-Series Blade servers and Cisco UCS C-Series Rack-Mount.
  5. Click Unified Computing System (UCS) Drivers.
  6. Select the bundle you want to download, and click Download Now.

Tip: When you choose which driver bundle to download, it is important to select the driver bundle version that is most similar to the server firmware release. For example, if you run a UCS-B Release 3.2(2b), then VMware driver bundle ucs-bxxx-drivers-vmware.3.2.2.iso is required.

Tip: Most VMware ESXi drivers are downloaded directly from www.vmware.com/download, with a search for the driver version. This is often quicker than if you were to download the entire driver bundle.

Identify Server Hardware

Before you select the correct driver, you must identify what hardware devices are installed on the server. This section describes how to find the devices located on the UCS Manager and in the CIMC.

UCS B Series

This example shows how to find the server inventory in UCS Manager. Server 1/1 has two adapter models installed: the VIC 1240 and 1280.

UCS C Series

This example shows how to find the server hardware devices in the CIMC. The server has a LSI 9266-8i RAID controller installed.

Identify the UCS Firmware Release

Before the correct driver version is selected, the UCS release must be identifed. This section describes how to identify the current UCS release installed on the servers.

UCS B Series

In this example, the UCS B Series runs UCS Release 2.1(1a).

UCS C Series

In this example, the UCS C Series runs UCS Release 1.4(6d).

OS Specifics

This section describes how to check driver versions and how to install drivers on common OSs.

VMware ESXi

Use these commands in order to check the current driver versions and VMware build:


Tip: These commands are executed from the ESXi CLI. Secure Shell (SSH) must be enabled before an SSH session is initated.

vmware -vlDisplays the VMware build and patch level
esxcli software profile getDisplays flavor of install ISO
esxcfg-scsidevs -aLists the hosts HBAs and the associated driver name
esxcfg-nics -lLists the host vmnics and network interface card (NIC) models
ethtool -i vmnicXDisplays the Ethernet driver used by the specified vmnic
esxcli network nic get -n vmnicXDisplays the Ethernet driver used by the specified vmnic on ESXi 6.5
vmkload_mod -s fnicDisplays the host bus adapter (HBA) driver version for the Cisco VIC
vmkload_mod -s enicDisplays the Ethernet driver version for the Cisco VIC
vmkload_mod -s nenicDisplays the Ethernet driver version for the Cisco VIC for ESXi 6.5 and later releases
vmkload_mod -s megaraid_sasDisplays the LSI MegaRAID driver version
vmkload_mod -s lsi_mr3Displays the LSI lsi_mr3 driver version(Native driver on ESXi 6.7)
vmkload_mod -s driver_nameDisplays the driver version for a specified driver

These examples show that vmnic2 uses a Cisco VIC and a driver version of

These examples show that the Qlogic Host Bus Adapter (HBA) uses driver qla2xxx Version 901.1k.1-14vmw.

Install the Driver

Complete these steps in order to install the driver:

  1. Extract the contents of the driver zip file, and identify the *.vib file.
  2. Use the Datastore Browser in order to upload the *.vib file to an ESXi host datastore.
  3. Enter the host into Maintenance mode.
  4. Install the driver.

ESXi 5.x/6.x

Use this command in order to install the driver on ESXi Release 5.x/6.x:

Note: If the drivers require a signature verification, run this command with the --no-sig-check switch. Ensure that you use the full path to the file.

ESXi 4.x

Use this command in order to install the driver on ESXi Release 4.x:

Finish the Installation

After you install the driver with one of the previously mentioned commands, exit Maintenance mode and reboot the host. For more information on how to install drivers, reference the Related Information section at the end of this document.

Useful VMware CLI Commands

Here are some other useful VMware commands that you can use when you install a driver:

Check Maintenance Mode Status

Check for Powered-On VMs

Power-Off VMs

Enter Maintenance Mode

Exit Maintenance Mode

Microsoft Windows Server

This section describes how to install a driver on a Microsoft Windows server.

Check Current Driver Version

In order to check the device drivers in Microsoft Windows, use the Device Manager located in the Control Panel.

Check Current Driver Version CLI

For Windows Server Core the Plug-and-Play (PnP) Utility (PNPUtil.exe) is used to check driver versions.

Missing Drivers

Hardware devices with missing drivers are displayed in the Device Manager with a yellow question mark. These devices should be updated with the correct driver in order to prevent unexpected behavior.

Install the Driver

In order to install or update a driver in Microsoft Windows, right-click on the device, and choose Install/Update Driver in order to start the Installation Wizard.

Install the Driver from CLI

The PNPUtil tool can also be used to install drivers from the CLI. The driver ISO bundle can be mounted via the UCS KVM Console Virtual Media.

Useful Windows CLI Commands

pnputil.exe -eList all installed 3rd party drivers
pnputil.exe -a <INF name>Install driver
pnputil.exe -d <INF name>Delete driver
pnputil.exe -f -d <INF name>Force delete driver

Red Hat and SUSE Linux

This section describes how to install and validate a driver on Red Hat Enterprise Linux (RHEL) and SUSE Linux Enterprise Server (SLES).

SUSE Background Information

Starting with SLES 12 SP1, the Cisco eNIC and usNIC drivers are bundled together into a single RPM (vs. being packaged in separate RPMs, as they are for other Linux distributions). Bundling both drivers into a single RPM is required because of how kernel module dependencies are managed in SLES 12 SP1 and later. If you are not using Cisco usNIC functionality (i.e., if you have not provisioned any usNIC devices in UCSM / CIMC), the usNIC driver will effectively be ignored.

The eNIC and usNIC drivers have their own distinct version numbers. If you install the cisco-enic-usnic RPM on SLES 12 SP 1 or later, once those drivers are loaded into the running kernel (e.g., via rebooting), use cat /sys/module/enic/version and cat /sys/module/usnic_verbs/version to view their respective version numbers. The cisco-enic-usnic RPM has its own distinct version number as well. Because it represents the packaging of the eNIC and usNIC drivers, the RPM version number may look similar, but does not reflect the specific version of either driver.

For additional information on the exact driver versions query and review the RPM description section. The query looks similar to the example below:

Verify current driver versions and OS Release

Here is a list of commands used in order to check the current driver version and OS release:

modinfo driver_nameDisplays driver version for the specified driver that will be loaded (by default) at next reboot
modinfo /path/to/driver_name.koDisplays driver version for the specified driver kernel object file
cat /sys/module/enic/versionDisplays the Ethernet driver version currently loaded in the running Linux kernel for the Cisco VIC adapter
cat /sys/module/fnic/versionDisplays the FC NIC driver version currently loaded in the running Linux kernel for the Cisco VIC adapter
cat /sys/module/megaraid_sas/versionDisplays the LSI MegaRAID driver version currently loaded in the running Linux kernel
lsmod -lLists currently-loaded drivers in the kernel
cat /etc/redhat-releaseShows the RHEL release (for RHEL 6.x and earlier)
cat /etc/SuSE-releaseShows the SUSE release (for SLES 11 SP3 and earlier)
cat /etc/os-releaseShows the RHEL release (for RHEL 7.x and later, and SLES 11 SP4 and later)
uname -aShows kernel related information

Note: Be aware of the command modinfo [ driver name ]shows the module information about the driver that will be loaded upon next reboot. This is not necessarily the same driver version currently loaded in the running kernel. Review cat/sys/module/DRIVER_NAME/version to validate the driver version loaded in the currently running kernel, and/or use the command modinfo [ /path/to/driver.ko ] to validate the module info for a specific driver kernel object file.

Tip: Refer to the Driver Name Reference Table located in the Appendix for examples of other common driver names.

This example shows that an ENIC driver version of bundled in the cisco-enic-usnic RPM package is installed on SLES 15 GA.

Install the Driver

Drivers in RHEL and SLES are installed using the Redhat Package Manager (RPM). Use this command in order to install the driver:

Vmware Others Driver Download For Windows 10

Tip: When you install drivers in Linux, ensure that you review the README files associated with the driver if available. You can look at the contents of the RPM to see where its associated README file was installed (e.g., rpm -qp kmod-enic). Some RPM driver packages have dependencies on other modules, and require installation of additional RPM packages. The README files contain full instructions on how to install the driver file.


Driver Name Reference Table

This table shows the driver names or prefixes for common drivers.

enicCisco VIC Ethernet NIC
fnicCisco VIC FC NIC
qle or qlaQlogic adapter
lpfcEmulex HBA (light pulse)
be2netEmulex Ethernet NIC
igb or ixgbeIntel NICs
bnxBroadcom adapter
megaraidLSI MegaRAID
megasrEmbedded SW RAID
nenicCisco VIC Ethernet NIC for ESXi 6.5

Vmware Others Driver Download For Windows

Related Information