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.
None of this worked. This is when I searched the VMWare forums and found the solution on this thread.
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.
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.
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.
helped a lot . thx very much
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.
It worked! Best solution
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!
Thank you … the steps mentioned here work as is…
Thank you – exactly what I needed!
Thanks bro, i was really about to give up
I have an OS X Mavericks (10.9.5) VM under VMware Fusion 11.5.5 under MacOS Catalina 10.5.5
on a 2019 16″ Macbook Pro.
Unity is greyed out.
Of course I have tried uninstalling/installing VMware Tools. Looking at the installation logs there were no
issues, and all files are there in /Library/Application Support/VMware Tools/
The two symlinks are also fine:
ln -s ‘/Library/Application Support/VMware Tools/mount_vmhgfs’ /sbin/
ln -s ‘/Library/Application Support/VMware Tools/mount_vmhgfs’ /Library/Filesystems/vmhgfs.fs/Contents/Resources/
I have even removed and re-installed ‘VMware Fusion’.
This has, so far, defeated VMware support. Mind you they didn’t realise
‘Library/Application Support/VMware Tools/’ was root and not the user,
so I am not sure she knows enough!
worked first time! thanks again
Thank you so much for your guide! Now it work.
Thanks, this worked perfectly
Thanks!
Thanks a lot! Enabling CD-ROM totally missed out of my mind. And I struggled a lot for accessing shared drive inside guest. Now it is working after enabling CD-ROM and installing VMWare tools.
GOD! Thanks!
this fantastic even the vendor has no solution
Worked for me! Many thanks !!
thanks
it works perfect
Really, Thank you sooooo much
Worked a treat, thanks for posting
It works perfectly for fusion
It works!
You Sir, are a legend
I had the same problem in Vmware Workstation pro 16. The guest os being windows 7 x32 bit. Tried all the above methods. They didnot work. Then after much research found this page:
https://my.vmware.com/web/vmware/downloads/info/slug/datacenter_cloud_infrastructure/vmware_tools/11_x
Registered my name and downloaded vmware tools separately. Details
VMware Tools packages for Windows
File size: 125.33 MB
File type: zip
Name: VMware-Tools-windows-11.2.0-16938113.zip
Release Date: 2020-10-15
Build Number: 16938113
VMware Tools packages for Windows
VMware Tools packages for Windows. These packages support the following operating systems: Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (SP1) and later
MD5SUM: 409742dfcd24bee8798e7596430fd259
SHA1SUM: e257e07a9e2899f882cf3dde30acbe8e195982f5
SHA256SUM: 3659f65af38d704914bb566d790043678275c694d87b4fc8fb485a2a164cd952
Extracted the *.iso file. Mounted the *.iso file to cd/dvd drive in the vmware console. The vmware tools exe was seen inside the guest os and installation was as usual.
P.S.: Sometimes software companies try to test whether their end users are intelligent or not by making their lives miserable and sending them in wild goose chase. I think it was one such attempt. Worst of all it worked.
Thank you very much. Worked perfectly for my installation of a Windows 7 VM under VMware 16.1 (Windows).
Thanks sir, I was worried.
It worked like charm so I couldn’t stop myself to comment 😊
Same here , lot of thanks u just saved my day :-)
Thanks a lot, got it working by following your guide.
Thak you very much. This really works! Saved me hours of frustration.
thanks a lot
Massive thanks ! I have spent hours trying to get VMWareTools installed.
I must say that I think that the effort required to install is ridiculous. I could not find any decent information on the web explaining how to install the tools (the method is completely obscure), or even how to verify they were installed. This is by fare the worst thing about VMWare.
wow thx
works! thanks
Thank you very much! It’s been driving me nut.
Thank you
thanks, worked for me, excellent ! Bula from Fiji