VMware Workstation 14 Player Release Notes

|

VMware Workstation 14 Player | 26 Sep 2017 | Build 6661328  

Last updated: 26 SEPT 2017

Check for additions and updates to these release notes.

What's in the Release Notes

About VMware Workstation Player

VMware Workstation Player is a streamlined desktop virtualization application that runs another operating system on the same computer without rebooting. VMware Workstation Player provides a simple user interface, unmatched operating system support, and portability across the VMware ecosystem.

For more information, see the broader VMware Workstation Player documentation 

System Requirements

Systems using Processors (CPUs) launched in 2011 or later are supported except:

  • Intel Atom processors based on the 2011 “Bonnell”  micro-architecture (e.g. Atom Z670/Z650; Atom N570)
  • Systems using Intel Atom processors based on the 2012 “Saltwell” micro-architecture (e.g. Atom S1200, Atom D2700/D2500, Atom N2800/N2600.
  • Systems using AMD processors based on the “Llano” and “Bobcat” micro-architectures (e.g. code-named “Hondo”, “Ontario”, “Zacate”, “Llano”)

In addition the following are supported:

Systems using Intel processors based on the 2010 “Westmere” micro-architecture (e.g. Xeon 5600, Xeon 3600, Core i7-970, Core i7-980, Core i7-990)

What's New

The following support is new in Workstation 14 Player:

  • Windows 10 Creators Update support 
    VMware Workstation Player provides the following support for Windows 10 Creators Update:
    • Run Windows 10 Creators Update as a virtual machine
    • Run Windows 10 Creators Update as a host operating system
    • Windows 10 Creators Update Auto Detect and Easy Install
    • Unity support for Windows 10
  • New Guest operating systems support
    Support has been added for the following operating systems: 
    • Ubuntu 17.04
    • Fedora 26
    • CentOS 7.4
    • RHEL 7.4
    • Debian 9.1
    • Oracle Linux 7.4
    • SLE 12 SP3
    • OpenSUSE 42.3
  • New CPU enablement
    Intel Skylake and AMD Ryzen CPU support is enabled.
  • Virtual NVMe support
    Workstation 14 Player introduces a new virtual NVMe storage controller. NVMe devices require virtual hardware version 13 / ESXi 6.5 compatibility and later.
  • Secure Boot
    Workstation 14 Player introduces Secure Boot support for Virtual Machines to ensure only trusted code is loaded by the UEFI firmware prior to the OS "handoff" process.
  • Network Latency simulation
    With new Network Latency Simulation feature, you can simulate a specific network environment along with existing network speed and packet loss simulator.
  • Native OVF support
    With improved OVF/OVA support, Workstation Player provides an effortless walkthrough to deploy the VMware VCSA (vCenter Server Appliance) OVA package for testing and experimentation within Workstation. VCSA6.0 and 6.5 are supported.
  • New GTK+ 3 based UI for Linux
    Linux Workstation Player UI has been rewritten to support GTK+ 3.

Known Issues

The following issues might occur in this version of VMware Workstation Player.

  • "The VMware Tools power-on script did not run successfully in this virtual machine" error prompts out when power on a VCSA6.0 appliance
    Power on an imported VCSA6.0 appliance within Workstation Pro, following error message will prompt out:"The VMware Tools power-on script did not run successfully in this virtual machine"
    Workaround: Click "OK" button to ignore the error message.
  • USB devices on some of the 3.1 xhci controllers are not available for passthrough on windows hosts
    USB devices connected to some USB 3.1 controllers are not listed under “VM > Removable Devices”, hence the device cannot be pass-through to the virtual machine.
    Workaround: None.
  • Windows 10 Insider Preview virtual machine may become black screen after exit Unity or multimonitor
    When you have more than 1 monitors connecting to your host, Windows 10 Insider Preview VM may become black screen under following scenarios:
    • Enter Unity mode and then Exit Unity mode
    • Switch to multimonitor mode, then switch back to 1 monitor
    Workaround: You can switch back to Unity mode or original multimonitor mode to get VM’s display normal.