How to install VMWare tools if the option is grayed out
I use VMWare Workstation Player primary to run Linux but a few days ago I wanted to install a virtual copy of Windows 10 to test some upcoming features. Virtual machines are great for testing operating systems or programs as they can be set up relatively quickly, don't alter existing installations and don't interfere with the underlying operating system.
I got the ISO using Martin's guide and the installation went fine. But then, I noticed that it didn't install the VMWare tools like it would normally do.
One of the important features that these tools add is the ability to copy data from the virtual machine to the host operating system or vice-versa. That's how I actually came to know that the tools weren't installed, it didn't let me move some folders from my main Windows 10 to the VM version.
I knew that I had chosen the option to download VMWare tools when creating the virtual machine. I even remember the message log displaying the notification that the tools had been downloaded. Oddly, when I clicked the Manage option the install VMWare tools option was grayed out.
Hoping to find a fix, I began to look around and came across official documentation on VMWare's support portal. According to the page, the virtual CD/DVD drive should be set to "Auto Detect" so that VMWare would let the user install VMWare Tools. The option which I wanted to change in the virtual machine's CD/DVD drive was set to use my Windows 10 ISO and I couldn't change this setting.
Here's what I tried (and failed)
- Ejecting the Windows ISO. I hoped this would free the drive and the virtual machine would let me install the tools.
- Disconnecting and reconnecting the virtual optical drive.
- Adding a second CD/DVD drive. It just kept giving me SATA0 errors.
None of this worked. This is when I searched the VMWare forums and found the solution on this thread.
How to install VMWare tools if the option is grayed out
1. Shut down the virtual machine.
2. Open VMWare Workstation Player and right-click on the VM. (Don't start the VM)
3. Select the "Settings" option to edit the hardware settings.
4. Highlight the CD/Drive on the left side-bar under the Hardware tab and click on the remove button.
5. Repeat the above step to remove the Floppy Drive. (Optional, but this is what fixed it for me. Courtesy: AskUbuntu forums)
6. Click on the "Add button" and select "CD/DVD" Drive and select finish. The right pane should have now have the option "Use Physical Drive > Auto Detect" enabled. (Previously, it had the Windows ISO selected)
7. Click on "OK" to close the window, and Start the VM as normal.
8. Once it has booted to the desktop, click on the menu at the top left corner and go to "Player > Manage > Install VMWare Tools".
The option should no longer be greyed out. Click on it to install the VMWare Tools. You will also see a new tab at the bottom of the screen prompting you to install the tools.
If this doesn't work, you can try to manually download the VMWare Tools ISO, mount it in a virtual drive and install it. This isn't limited to Windows 10 VMs, it should work on any VM be it Linux, macOS, or older versions of Windows.
Previous Post: « How to use Sandboxie for browsing, downloading and installing programs
Next Post: How to copy, select and search text in ePub books using SumatraPDF »
Good to find a non-enterprise user of VMware. Several years ago I considered getting up to speed on it but VMware reportedly laid off the development staff of Workstation (or Player, or whatever they call it this week :().
Say, what do they call it now and what version is it?
Is the free version hard to find and are there any significant limitations compared to Virtualbox or KVM?
TIA, Mike
VMware Workstation free version =
https://www.vmware.com/products/workstation-player/workstation-player-evaluation.html
I prefer VirtualBox simply because it works well with any distro. I rather doubt Ashwin’s problem would occur on VirtualBox.
Yet, when it works and one does whatever is necessary, I find VMware to have a more polished look and feel.
One will eventually encounter a problem with either tool which will require a bit of research–no “real” problems, though.
Windows Hyper-V works fine.
VMWare Workstation Player also requires some VMX file editing to tweak some of the features not available via GUI.
Why not just use VirtualBox instead?
These days the most important and most valuable product of Oracle is VirtualBox! Nobody cares about Oracle Database, Oracle eBusiness Suite and the like anymore.
Thank you. This article helped me. My issue was my 2019 MacBook Pro doesn’t have a CD/DVD so my VM image never had a CD drive. Adding the CD to the VM allowed the VM to boot with CD in a disconnected state but it was there. Then the option to install VMware Tools was not grey! hurray! Got my VMware tools installed and was then able to use the features such as sharing a drive with my VM.
Thanks for the tip of adding a CD drive. I never realized this before because all my other VM hosts had CD drives. This should allow my other Kubernetes VM’s to also get the tools now. I’ll try that next.
Thank you so much. This got me out of the few hours rant of frustration.
Very Helpful! Thank you
thanks. Worked instantly
Thank you so much. You saved my time!
This procedure really helped me.
Thank you so much – really helped me out of a problem
May cause an issue with the IDE device configured as a slave. See, for solution:
https://kb.vmware.com/s/article/2010477
Appreciate it. It was useful.
thanks
Thank, Ten seconds to find your tips and five sends to fix my issue.
Thanks a million!
I have tried the Removing the CD solution , it will work if you add a CDRom drive again.
if there is no CDROM you can’t install the tools
It saved me so much time instead of reinstalling the entire VM.
Removing the floppy disk did it for me, thanks!
Thank you very much! Followed your instructions to a tee to remove the CD/DVD and Floppy drives on my Windows 7 VM. Much appreciated!
This really helped a lot. Thanks!
Thanks a lot, I spent hours tying to find a fix.
This works very well!
THANK YOU SO MUCH!