Error vmware workstation cannot be installed

error vmware workstation cannot be installed

What I did was to open a CMD as administrator, navigating to the directory where the executable for installation was from the command line, and launching the. During VMware Workstation installation, the Setup window goes blank. Installation fails and presents an empty dialog box. In the vmware. · This. Set up your virtual machine and proceed to install Windows 11. · When installing Windows 11 in VMware Workstation, you will see the This PC can't.

Error vmware workstation cannot be installed - the

Installing and upgrading VMware Tools on Windows VMs

This article describes how to use VMware Tools on Windows VMs. For Linux VMs, see Installing and upgrading VMware Tools on Linux VMs.

Contents

Overview

VMware Tools provides many drivers specific to running your x86 VM operating system. Among others, VMware Tools provides the video driver that allows you to control your VM mouse cursor and the networking drivers required for VM network connectivity.

If you’re having issues with the mouse cursor or connecting to the VM, make sure you’re using the Skytap-supported version of VMware Tools. Newer versions of VMware Tools may not work with Skytap VMs.

Notes

  • Don’t install VMware Tools on Power (non-x86) VMs.
  • Skytap supports VMware Tools version 11.0.5 build 15389592 for Windows VMs and version 10.0.6 build 3560309 for legacy Linux VMs. These versions are available as an .ISO in the Skytap public assets library. They can also be downloaded from the VMware website. Using unsupported versions of VMware Tools may cause unexpected behavior in Skytap VMs.
  • Most modern major Linux distributions include , an open-source product that generally works with Skytap. For more information, see github/vmware/open-vm-tools. If your VM has and problems with (for example, if it doesn’t shut down correctly), follow the instructions below to install VMware tools.

Checking the VMware Tools version

To check which version of VMware Tools is installed on a Windows VM
  1. Locate the VMware Tools icon in the System Tray. Move the mouse pointer over the icon. The the message VMware Tools can be updated. displays, the VMware Tools installation is out of date. needs update

    If the VMware Tools icon isn’t in the System Tray, VMware Tools isn’t installed.

  2. To check which version is installed, right-click the VMware Tools icon and select About VMware Tools. The About VMware Tools dialog displays information about the currently installed version. Toolbox-win

Updating VMware Tools

To update your version of VMware Tools

Installing VMware Tools

These instructions describe the process for installing VMware Tools on Windows Server 2012 R2. The steps for other versions of Windows may be different.

  1. Before editing the VM, create a template of it. Should any issues arise, you can restore your VM from this template.
  2. Navigate to the environment details page for the environment that contains the VM you want to update. Make sure that the VM is powered on and that you’re logged in.
  3. On the tile for the VM you want to update, click Load ISO (Load ISO). load ISO

  4. Click All.
  5. Select the ISO to install VMware Tools for Windows. select ISO

  6. Click load ISO (Load ISO).
  7. If the installer doesn’t auto-load in your VM, navigate to Computer and double-click the CD-ROM to start the installer.

    If you don’t have mouse control in the VM, use the Tab, Spacebar, Enter, and arrow keys on your keyboard to navigate the UI.

    Start-installer

  8. Follow the instructions for a complete install.

    Complete-install

  9. After the installation is complete, reboot the VM.

    Restart

  10. After the VM reboots, check for video driver updates.

    Example: Checking the video driver in Windows Server 2012 R2

    To check which driver the VM is using

    1. Right-click on Start, and then click Device Manager.
    2. Expand Display Adapters to see the current driver. If the driver listed isn’t VMware SVGA 3D follow the instructions below to update it. If the driver listed is the VMware SVGA 3D driver, make sure you’re using the most recent version.

    To check the WDDM driver version

    1. Right-click the current driver, and click the Properties.
    2. Check the Driver Date on the Driver tab. Make sure to use the VMware SVGA 3D driver from 7/12/2016 (older versions don’t provide as much video RAM).

    To update to the most recent VMware SVGA 3D driver version

    1. Right-click the current driver, and click Update Driver Software.
    2. Click Browse my computer and select C:\Program Files\Common Files\VMware\Drivers\video_wddm.

Uninstalling VMware Tools

  1. Click Start > Control Panel.

    • If viewing by Category, select Uninstall a Program.
    • If viewing by Icons, select Programs and Features.
  2. From the Programs and Features window, select VMware Tools and then click Uninstall. Uninstall

After you uninstall VMware Tools and reboot the machine, you must reinstall VMware Tools to restore mouse control.

Troubleshooting “Setup can’t continue because a later version of this product is already installed” error

The most common error when you update VMware Tools is Setup cannot continue because a later version of this product is already installed.

error

This error usually occurs when a VM is imported to Skytap. To resolve this error:

  1. Uninstall the newer version of VMware Tools (see Uninstalling VMware Tools).
  2. Install the Skytap recommended version (see Installing VMware Tools).
I125+ undefined symbol

A workaround is to downgrade to earlier version, or more preferably, force VMware to use its own shipped version of :

# export LD_LIBRARY_PATH=/lib/vmware/lib/librsvg-2.so.2:$LD_LIBRARY_PATH

VMware also has a variable:

$ env VMWARE_USE_SHIPPED_LIBS=1 vmware

vmplayer/vmware fails to start from version 12.5.4

As per [3] the temporary workaround is to downgrade the package to version 1.6.28-1 and keep it in the parameter in /etc/pacman.conf.

An easier workaround is to make VMWare use the system's version of zlib instead of its own one:

# cd /usr/lib/vmware/lib/libz.so.1 # mv libz.so.1 libz.so.1.old # ln -s /usr/lib/libz.so.1 .

vmplayer/vmware fails to start from version 12.5.3 to version 12.5.5

It seems to be a problem with the file , missing .

If the system have installed gcc-libs, that library is already installed. Therefore, it is possible to remove that file and vmplayer will use the one provided by gcc-libs instead. As root do:

# mv /usr/lib/vmware/lib/libstdc++.so.6/libstdc++.so.6 /usr/lib/vmware/lib/libstdc++.so.6/libstdc++.so.6.bak

Also there is a workaround:

# export VMWARE_USE_SHIPPED_LIBS='yes'

vmware 12 process terminates immediately after start, no GUI is launched

Registered bug at Mageia, but it seems that there are no error messages shown in terminal with arch. When inspecting the logs, which are in , there are , , , issues. Process simply terminates with after vmware or vmplayer is executed. Solution is the same, as root do:

# mv /etc/vmware/icu/icudt44l.dat /etc/vmware/icu/icudt44l.dat.bak

Also there is a workaround:

# export VMWARE_USE_SHIPPED_LIBS='yes'

Despite setting the VMWARE_USE_SHIPPED_LIBS variable, VMWare may still fail to find certain libraries. An example is the libfontconfig.so.1 library. Check vmware logs in the tmp directory to see which libraries are still not found. Copy them to the appropriate path with libraries existing on the system:

# cp /usr/lib/libfontconfig.so.1 /usr/lib/vmware/lib/libfontconfig.so.1/

Instead of copying all these files manually, you may want to try exporting an additional setting:

# export VMWARE_USE_SYSTEM_LIBS='yes'

On systems with fontconfig version 2.13.0 and above, it may be needed to force VMware to use the shipped libfontconfig file instead of the newer system file. In such case, it is also necessary to provide a shared object library file for the shipped fontconfig. This applies for at least VMware version 12.5.9. As root do:

# ln -s /usr/lib/libexpat.so /usr/lib/vmware/lib/libfontconfig.so.1/libexpat.so.0 # export LD_LIBRARY_PATH=/usr/lib/vmware/lib/libfontconfig.so.1:$LD_LIBRARY_PATH

Guest Issues

Unable to download VMware Tools for Guests

To download the tools manually, visit the VMware repository.

Navigate to: "application name / version / build ID / linux / packages/" and download the appropriate Tools.

Extract with:

$ tar -xvf vmware-tools-name-version-buildID.x86_64.component.tar

And install using the VMware installer:

# vmware-installer --install-component=/path/vmware-tools-name-version-buildID.x86_64.component

If the above does not work, try installing ncurses5-compat-libsAUR.

Guests have incorrect system clocks or are unable to boot: "[...]timeTracker_user.c:234 bugNr=148722"

This is due to incomplete support of power management features (Intel SpeedStep and AMD PowerNow!/Cool'n'Quiet) in VMware Linux that vary the CPU frequency. In March 2012, with the release of linux 3.3-1 the maximum frequency Performance governor was replaced with the dynamic Ondemand. When the host CPU frequency changes, the Guest system clock runs too quickly or too slowly, but may also render the whole Guest unbootable.

To prevent this, the maximum host CPU frequency can be specified, and Time Stamp Counter (TSC) disabled, in the global configuration:

/etc/vmware/confighost.cpukHz = "X" # The maximum speed in KHz, e.g. 3GHz is "3000000". host.noTSC = "TRUE" # Keep the Guest system clock accurate even when ptsc.noTSC = "TRUE" # the time stamp counter (TSC) is slow.

Tip: To periodically correct the time (once per minute), in the Options tab of VMware Tools, enable: "Time synchronization between the virtual machine and the host operating system".

Networking on Guests not available after system restart

This is likely due to the module not being loaded [4]. See also the #systemd services section for automatic loading.

Mouse issues

Mouse buttons above 5 do not work

If your mouse's thumb buttons or other additional buttons do not work, set guest to use advanced mouse.

Strange mouse wheel behavior on Guest

This is related to the current Xorg keyboard layout on Host system. Keep primary layout (e.g., English) selected on Host while working on Guest.

No IP address and network access for nested VMs

This issue is related to promiscuous mode which, following standard Linux practice, can only be enabled by the root user. To work around these limitations, the permissions for the networking device in question have to be changed.

Give permissions to one group:

# chgpr group /dev/vmnetX # chmod g+rw /dev/vmnetX

Give permissions to all users:

# chmod a+rw /dev/vmnetX

Uninstallation

To uninstall VMware you need the product name (either or ). To list all the installed products:

$ vmware-installer -l

and uninstall with ( skips the confirmation):

# vmware-installer -u product --required

Tip: Use for the console UI.

Remember to also disable and remove the services:

# rm /etc/systemd/system/vmware.service # rm /etc/systemd/system/vmware-usbarbitrator.service

You may also want to have a look at the module directories in for any leftovers, and remove if now empty.