If you are using 15 Pro, you may also want to enable (check) "Automatically adjust user interface size in the virtual machine" (under VM -> Settings -> Hardware -> Display).
(Just set the host's resolution to 1080P before launching Workstation 14 Pro, AND ensure that you have set the "high DPI settings" appropriately: using the Properties for the Workstation Pro shortcut, go to the Compatibility tab, then "Change high DPI settings," and select "Program DPI" with "I signed in to Windows" for the corresponding dropdown option.) This said, the 4K support is nice if you do decide to fork out the bucks for 15 Pro. Even 4K support is questionable: one can achieve workable 1080P across 1080P and 4K screens with Windows 10 (1809) for example. There are very few reasons to upgrade to 15 Pro from 14 Pro IMO. NOTE: Within a VM, NVME drives particularly suffer for multithreaded reads and writes, as may be seen in the AS SSD Benchmark tool's 4K-64Thrd (i.e., 64-threads) read and write tests. Notably, Workstation 15 continues to recommend SCSI drives over all others for performance, so at least that much is yet true. So, VMware has yet to actually address this problem. There is not even a recognizable marginal improvement in NVME performance between Workstation 14 and 15. (Even under the SCSI option, read/write performance is DRAMATICALLY worse in the VM than on the host for NVME drives.) I tested using a Samsung 970 Evo 2TB NVME drive in all cases for this. I have extensively tested the latest versions of Workstation Pro 15 and Workstation Pro 14, and can definitively state that the SCSI drive option continues to be faster than the NVME drive option, and both are much slower than they should be within VMs. VMware's claim of "performance improvements for virtual NVMe storage" are just hot air. It is just as relevant today under version 15.5.x, as it was when I posted it back in January 2019:Īs of version 15.0.2 of Workstation, this is still NOT fixed. I posted this important information in January 2019, and apparently some unhappy individual (presumably with VMWare) foolishly removed it, so here it is again.