Error installing vmci driver

When you try to install the driver in Device Manager in virtual machines, it fails and you receive the following error message:.

Windows found driver software for your device but encountered an error while attempting to install it. Moreover, a log that resembles the following is logged in the setupapi. This issue occurs for security reasons. The Telnet Server service makes some permission changes to the window station in which it's running during initialization. If you configure the Telnet Server service to run by using the Local System account without the ability to interact with the desktop, it's started under a different window station.

This may cause problems for other processes that also run under the Local System account and don't interact with the desktop. One such process is the driver install process that is used during installation of a new device driver.

To work around this problem, don't change the Telnet Server service to run under the Local System account. We recommended that you leave the Telnet Server service running under its default Local Service account. If it still doesn't resolve the issue, you can verify that the latest version of VMWare Tools that is installed. If you notice that you can't update VMWare Tools or uninstall it, follow these steps:. Click Start , click Run , type cmd, and then click OK.

A Command Prompt window opens. Install the latest version of VMware Tools and then perform a restart after you verify that the setting for the Telnet Server service logon setting is set correctly. Privacy policy. This article provides a workaround for an issue where you can't install a VMWare driver on a server that is running Windows Server R2 and that has the Telnet Server service installed. 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 E However, the second driver also doesn't install. Additionally, a log entry that resembles the following is logged in Setupapi. 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.