You copy a command on your PC, click into the VM, press paste - and nothing happens. This is the single most common VMware complaint, and it is the main problem solved in the video. It is almost never a bug: the VM is missing VMware Tools, or two little checkboxes were never switched on.
Clipboard sharing in VMware is a guest feature, not a host feature. It is delivered by VMware Tools inside the VM and gated by the guest isolation settings. That gives you an exact checklist: Tools installed and running, isolation options on, then a clean power cycle. Work through it in that order and do not skip ahead - each step depends on the one before it.
Nothing else on this page works without Tools. Look at the VM menu in Workstation: if it offers Install VMware Tools, Tools is missing - install it and reboot the guest. If it offers Update or Reinstall, Tools exists; on a Windows guest, open services.msc inside the VM and confirm the VMware Tools service is running. A stopped Tools service means a dead clipboard, every time.
Shut the guest down cleanly, then open VM Settings, Options tab, Guest Isolation. Tick Enable copy and paste and Enable drag and drop. These options ship switched off in some templates and in VMs cloned from strict environments, which is why a VM can have perfect Tools and still refuse to share a clipboard. Power the VM back on after changing them.
If both boxes are on and it still fails, restart the VMware Tools service inside the guest - or simply reboot the guest, which does the same job more reliably. Then test in stages: copy a line of plain text from Notepad on the host and paste it into Notepad in the guest. Text is the clipboard's basic job. Files are a different feature (drag and drop), and some rich content copied from browsers or Office simply does not cross - use a shared folder for those instead of declaring the clipboard broken.
Honest expectation-setting: even with everything working, the shared clipboard is for text and small content. Dragging a 2 GB file between host and guest is slow and fragile. For real file movement, enable a shared folder in VM Settings under Options, or copy over the network. Half of all "copy paste is broken" reports are actually "I tried to move a huge file the wrong way".
If your VM lives on an ESXi host rather than Workstation, clipboard sharing is disabled by default on purpose - shared infrastructure treats the clipboard as a data-leak path. It can only be enabled per VM by an administrator editing the VM's advanced settings in the .vmx configuration, for example:
isolation.tools.copy.disable = "FALSE"isolation.tools.paste.disable = "FALSE"If you are not the ESXi admin, the honest answer is that clipboard sharing is off by policy, not by fault - use shared storage or the network to move data instead.
The video enables copy paste on a live VM and shows the exact settings - watch it once and you will never forget where they hide.
Watch Full VideoBecause they are two different features. Text uses the shared clipboard; files use drag and drop, which is a separate guest isolation option and struggles with large files. For anything big, a shared folder or a network copy is faster and far more reliable.
Yes, with open-vm-tools installed from the Linux repository - and on desktop guests, the companion desktop package as well. The same guest isolation checkboxes in VM Settings control it, exactly as with a Windows guest.
Tools and Workstation are a matched pair. After a Workstation upgrade, update VMware Tools inside the guest from the VM menu and reboot. A version mismatch between the two is the classic cause of a clipboard that dies quietly after an update.