Содержание
- VMWare Tools не устанавливается: VMWare Tools installation cannot be started while Easy Install is in progress
- Vmware tool install error
- admin.txt
- … заметки IT’шника…
- Не устанавливается VMware tools? есть причина.
- Vmware tool install error
При установке VMware Tools на новую виртуалку очень часто, а может быть даже и всегда, получаю ошибку «VMWare Tools installation cannot be started while Easy Install is in progress», что переводится примерно так «Установка VMware Tools не может быть запущена в то время как идет Easy Install «.
Не помню уже сколько времени я потратил на поиск того, как отключить Easy Install в настройках самой программы, но даже похожего в настройках не нашел. Искал как получается всегда не там где нужно. Как потом оказалось, эта ошибка возникает по вине не размонтированной загрузочной дискеты в флоппи дисководе, необходимой для установки Операционной Системы. Вот это нами мешает. Если вы зайдете на флоппи дисковод то увидите примерно тоже самое, что и на картинке внизу.
Чтобы навсегда избавиться от ошибки надо сделать несколько действий. Если виртуальная машина у вас запущена, то ее следует выключить и зайти в настройки. В настройки можно попасть выбрав вашу машину и нажав на «Edit virtual machine settings» или нажав комбинацию клавиш CTRL+D. В настройках следует перейти на вкладку Floppy и в группе Connection выбрать «Use physical drive», в выпадающем меню «Auto detect» и нажать OK. Вот мы и размонтировали загрузочную дискету, которая нам мешала установить VMware Tools.
Загрузив Операционную Систему вы сможете без ошибок установить VMware Tools.
Источник
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I try to install vmware tools on ubuntu server. After using the command apt-get install update and upgrade, the Install VMware tools then grayed out. Can anyone help me find the root cause?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Generally this option will grey out if you have already initiated this and Tools image is mounted to guest VM. Go to VM settings and check if tools image is mounted. You might have initiated it previously.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
when you see this option grayed out that’s means sometimes that you don’t have a virtual Optique drive in your Vmware guest , so try to make one from menu VM->settings->ADD .
regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After adding a CD/DVD drive, «Install VMware Tools» is not grayed out anymore.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I had a similar problem when installing a 64-bit Debian 9.x VM from a VirtualBox .ova file on VMware Workstation 14 Pro.
The problem was that the guest OS was set to «other» in Settings->Options->General
If I set the OS to Debian 9.x, VMware complained about the BusLogic SCSI driver being incompatible and would not launch the VM.
Finally following another post, I set the OS type to ubuntu (even though it’s Debian). Then it all worked; I was able to mount the vmware tools ISO and the «Install VMware Tools» menu option was available. Then in the VM it just appeared as if a CD had been put in the drive.
Источник
admin.txt
… заметки IT’шника…
Работая с виртуальными машинами, всегда стараюсь устанавливать в гостевую систему инструментарий от среды виртуализации. Это дает более гибкое управление и мониторинг за состоянием гостевой системы. Чаще мне приходится работать с виртуализацией от VMware, на различных платформах. Установка VMware tools в среде MS Wndows — вообще никогда не вызывает проблем. С установкой в системах GNU/Linux приходится больше работать вручную.
Вот сегодня пришлось убить час, на решение проблемы с установкой VM tools’ов в среде Windows. Проблема появилась при переносе виртуальной машины с моего хоста (VMware Workstation 6.5) на гипервизор ESXi 3.5. И вроде мастер переноса (VMware Converter) справился с задачей — я заметил некие «заедания» в работе крусора мыши на новом месте. Решено было переустановить tools’ы. Однако привычный вызов установщика в среде MS Windows, кликом в меню виртуальной машины ничего не принес (не сработал ни интерактивный ни автоматический режим установки). Я сделал несколько попыток, перезагружал гостевую систему, менял различные настройки — все тчетно… Следующим шагом я удалил уже установленные (еще когда машина крутилась на VMware Workstation 6.5) туллзы и снова повторил вышеописанный процесс — результат тот же. Инсталляция либо выдает ошибку (таймаут) либо завершается как бы успешно, судя по событиям ESXi.
Казалось бы в чем может быть дело? Однако уже в конце рабочего дня у меня включился мозг и я вспомнил процесс инсталяции VMware Tools в среде Линукса. Там кликая пункт меню — мы просто помещаем образ в устройство чтения компакт дисков. А потом монтируем и сетапим все ручками. А вот полная автоматизация процесса в Windows заблокировала мой мозг…
Оказывается при конвертации и переносе виртуальной машниы, VMware Converter отрубил все лишние устройства, в том числе был и виртуальный привод копакт дисков…. После ручного добавления в виртуальную машину нвоого привода установка Tools’ов прошла в привычном автоматическом режиме….
Вот так всегда, можно над одной мелочью «битый час» возиться и изводить свой разум 🙂
Источник
I have been searching around on Google but I can’t seem to find anything definitive yet. I am using:
- Windows 7 Host
- Linux Mint 17 XFCE 64-bit VM
- Workstation 9.0.4 build-1945795
- VMware Tools version 9.2.4.27715 (build-1398046)
When installing the tools I am receiving an error when enabling host-guest file system sharing.
The VMware Host-Guest Filesystem allows for shared folders between the host OS
and the guest OS in a Fusion or Workstation virtual environment. Do you wish
to enable this feature? [yes]
Before you can compile modules, you need to have the following installed.
kernel headers of the running kernel
Searching for GCC.
Detected GCC binary at «/usr/bin/gcc».
The path «/usr/bin/gcc» appears to be a valid path to the gcc binary.
Would you like to change it? [no]
Searching for a valid kernel header path.
Detected the kernel headers at «/lib/modules/3.13.0-24-generic/build/include».
The path «/lib/modules/3.13.0-24-generic/build/include» appears to be a valid
path to the 3.13.0-24-generic kernel headers.
Would you like to change it? [no]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-hTifx3/vmhgfs-only’
/usr/bin/make -C /lib/modules/3.13.0-24-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/.
make[1]: Entering directory `/usr/src/linux-headers-3.13.0-24-generic’
CC [M] /tmp/modconfig-hTifx3/vmhgfs-only/backdoor.o
CC [M] /tmp/modconfig-hTifx3/vmhgfs-only/backdoorGcc64.o
In file included from /tmp/modconfig-hTifx3/vmhgfs-only/backdoor.h:30:0,
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/backdoor_types.h: In function ‘BACKDOOR_STRUCT_SIZES’:
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_assert.h:320:20: warning: typedef ‘AssertOnCompileFailed’ locally defined but not used [-Wunused-local-typedefs]
typedef char AssertOnCompileFailed[AssertOnCompileMisused];
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_assert.h:342:7: note: in definition of macro ‘MY_ASSERTS’
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/backdoor_types.h:112:12: note: in expansion of macro ‘ASSERT_ON_COMPILE’
ASSERT_ON_COMPILE(sizeof(Backdoor_proto) == 6 * sizeof(uintptr_t));
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_assert.h:320:20: warning: typedef ‘AssertOnCompileFailed’ locally defined but not used [-Wunused-local-typedefs]
typedef char AssertOnCompileFailed[AssertOnCompileMisused];
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_assert.h:342:7: note: in definition of macro ‘MY_ASSERTS’
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/backdoor_types.h:113:12: note: in expansion of macro ‘ASSERT_ON_COMPILE’
ASSERT_ON_COMPILE(sizeof(Backdoor_proto_hb) == 7 * sizeof(uintptr_t));
In file included from /tmp/modconfig-hTifx3/vmhgfs-only/backdoor.h:30:0,
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/backdoor_types.h: In function ‘BACKDOOR_STRUCT_SIZES’:
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_assert.h:320:20: warning: typedef ‘AssertOnCompileFailed’ locally defined but not used [-Wunused-local-typedefs]
typedef char AssertOnCompileFailed[AssertOnCompileMisused];
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_assert.h:342:7: note: in definition of macro ‘MY_ASSERTS’
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/backdoor_types.h:112:12: note: in expansion of macro ‘ASSERT_ON_COMPILE’
ASSERT_ON_COMPILE(sizeof(Backdoor_proto) == 6 * sizeof(uintptr_t));
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_assert.h:320:20: warning: typedef ‘AssertOnCompileFailed’ locally defined but not used [-Wunused-local-typedefs]
typedef char AssertOnCompileFailed[AssertOnCompileMisused];
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_assert.h:342:7: note: in definition of macro ‘MY_ASSERTS’
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/backdoor_types.h:113:12: note: in expansion of macro ‘ASSERT_ON_COMPILE’
ASSERT_ON_COMPILE(sizeof(Backdoor_proto_hb) == 7 * sizeof(uintptr_t));
CC [M] /tmp/modconfig-hTifx3/vmhgfs-only/bdhandler.o
CC [M] /tmp/modconfig-hTifx3/vmhgfs-only/cpName.o
CC [M] /tmp/modconfig-hTifx3/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/modconfig-hTifx3/vmhgfs-only/cpNameLite.o
CC [M] /tmp/modconfig-hTifx3/vmhgfs-only/dentry.o
In file included from /tmp/modconfig-hTifx3/vmhgfs-only/./shared/vmci_defs.h:33:0,
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h: In function ‘AtomicAssertOnCompilePtr’:
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h:2397:20: warning: typedef ‘AssertOnCompileFailed’ locally defined but not used [-Wunused-local-typedefs]
typedef char AssertOnCompileFailed[AssertOnCompileMisused];
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h:2558:1: note: in expansion of macro ‘MAKE_ATOMIC_TYPE’
MAKE_ATOMIC_TYPE(Ptr, 64, void const *, void *, uintptr_t)
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h: In function ‘AtomicAssertOnCompileInt’:
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h:2397:20: warning: typedef ‘AssertOnCompileFailed’ locally defined but not used [-Wunused-local-typedefs]
typedef char AssertOnCompileFailed[AssertOnCompileMisused];
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h:2562:1: note: in expansion of macro ‘MAKE_ATOMIC_TYPE’
MAKE_ATOMIC_TYPE(Int, 32, int, int, int)
CC [M] /tmp/modconfig-hTifx3/vmhgfs-only/dir.o
CC [M] /tmp/modconfig-hTifx3/vmhgfs-only/file.o
In file included from /tmp/modconfig-hTifx3/vmhgfs-only/./shared/vmci_defs.h:33:0,
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h: In function ‘AtomicAssertOnCompilePtr’:
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h:2397:20: warning: typedef ‘AssertOnCompileFailed’ locally defined but not used [-Wunused-local-typedefs]
typedef char AssertOnCompileFailed[AssertOnCompileMisused];
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h:2558:1: note: in expansion of macro ‘MAKE_ATOMIC_TYPE’
MAKE_ATOMIC_TYPE(Ptr, 64, void const *, void *, uintptr_t)
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h: In function ‘AtomicAssertOnCompileInt’:
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h:2397:20: warning: typedef ‘AssertOnCompileFailed’ locally defined but not used [-Wunused-local-typedefs]
typedef char AssertOnCompileFailed[AssertOnCompileMisused];
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h:2562:1: note: in expansion of macro ‘MAKE_ATOMIC_TYPE’
MAKE_ATOMIC_TYPE(Int, 32, int, int, int)
In file included from /tmp/modconfig-hTifx3/vmhgfs-only/./shared/vmci_defs.h:33:0,
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h: In function ‘AtomicAssertOnCompilePtr’:
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h:2397:20: warning: typedef ‘AssertOnCompileFailed’ locally defined but not used [-Wunused-local-typedefs]
typedef char AssertOnCompileFailed[AssertOnCompileMisused];
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h:2558:1: note: in expansion of macro ‘MAKE_ATOMIC_TYPE’
MAKE_ATOMIC_TYPE(Ptr, 64, void const *, void *, uintptr_t)
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h: In function ‘AtomicAssertOnCompileInt’:
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h:2397:20: warning: typedef ‘AssertOnCompileFailed’ locally defined but not used [-Wunused-local-typedefs]
typedef char AssertOnCompileFailed[AssertOnCompileMisused];
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h:2562:1: note: in expansion of macro ‘MAKE_ATOMIC_TYPE’
MAKE_ATOMIC_TYPE(Int, 32, int, int, int)
/tmp/modconfig-hTifx3/vmhgfs-only/file.c: In function ‘HgfsOpen’:
/tmp/modconfig-hTifx3/vmhgfs-only/file.c:658:27: error: incompatible type for argument 3 of ‘HgfsSetUidGid’
In file included from /tmp/modconfig-hTifx3/vmhgfs-only/file.c:45:0:
/tmp/modconfig-hTifx3/vmhgfs-only/fsutil.h:92:6: note: expected ‘uid_t’ but argument is of type ‘kuid_t’
void HgfsSetUidGid(struct inode *parent,
/tmp/modconfig-hTifx3/vmhgfs-only/file.c:658:27: error: incompatible type for argument 4 of ‘HgfsSetUidGid’
In file included from /tmp/modconfig-hTifx3/vmhgfs-only/file.c:45:0:
/tmp/modconfig-hTifx3/vmhgfs-only/fsutil.h:92:6: note: expected ‘gid_t’ but argument is of type ‘kgid_t’
void HgfsSetUidGid(struct inode *parent,
CC [M] /tmp/modconfig-hTifx3/vmhgfs-only/filesystem.o
make[2]: *** [/tmp/modconfig-hTifx3/vmhgfs-only/file.o] Error 1
make[2]: *** Waiting for unfinished jobs.
In file included from /tmp/modconfig-hTifx3/vmhgfs-only/./shared/vmci_defs.h:33:0,
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h: In function ‘AtomicAssertOnCompilePtr’:
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h:2397:20: warning: typedef ‘AssertOnCompileFailed’ locally defined but not used [-Wunused-local-typedefs]
typedef char AssertOnCompileFailed[AssertOnCompileMisused];
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h:2558:1: note: in expansion of macro ‘MAKE_ATOMIC_TYPE’
MAKE_ATOMIC_TYPE(Ptr, 64, void const *, void *, uintptr_t)
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h: In function ‘AtomicAssertOnCompileInt’:
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h:2397:20: warning: typedef ‘AssertOnCompileFailed’ locally defined but not used [-Wunused-local-typedefs]
typedef char AssertOnCompileFailed[AssertOnCompileMisused];
/tmp/modconfig-hTifx3/vmhgfs-only/./shared/vm_atomic.h:2562:1: note: in expansion of macro ‘MAKE_ATOMIC_TYPE’
MAKE_ATOMIC_TYPE(Int, 32, int, int, int)
/tmp/modconfig-hTifx3/vmhgfs-only/filesystem.c: In function ‘HgfsInitSuperInfo’:
/tmp/modconfig-hTifx3/vmhgfs-only/filesystem.c:234:15: error: incompatible types when assigning to type ‘uid_t’ from type ‘kuid_t’
/tmp/modconfig-hTifx3/vmhgfs-only/filesystem.c:240:15: error: incompatible types when assigning to type ‘gid_t’ from type ‘kgid_t’
make[2]: *** [/tmp/modconfig-hTifx3/vmhgfs-only/filesystem.o] Error 1
make[1]: *** [_module_/tmp/modconfig-hTifx3/vmhgfs-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-24-generic’
make: *** [vmhgfs.ko] Error 2
make: Leaving directory `/tmp/modconfig-hTifx3/vmhgfs-only’
The filesystem driver (vmhgfs module) is used only for the shared folder
feature. The rest of the software provided by VMware Tools is designed to work
independently of this feature.
If you wish to have the shared folders feature, you can install the driver by
running vmware-config-tools.pl again after making sure that gcc, binutils, make
and the kernel sources for your running kernel are installed on your machine.
These packages are available on your distribution’s installation CD.
I have tried to reinstall the tools several times and I have made sure that open-vm-tools is not on the VM. That same vmhgfs error keeps coming up. I also have this output.
| Header 1 |
|---|
lsmod | grep -i vm
vmw_balloon 13415 0
vmw_vmci 62966 0
vmwgfx 175358 3
ttm 85115 1 vmwgfx
drm 302817 4 ttm,vmwgfx
It would appear that vmhgfs is not being properly built but I’m not sure why that is. Copy and pasting files from host to VM works just fine and the folder /mnt/hgfs is created but the shared folders, which are enabled, are not displayed. Do I need a newer version of the tools?
Источник
| Header 1 |
|---|
by Milan Stanojevic
Milan has been enthusiastic about technology ever since his childhood days, and this led him to take interest in all PC-related technologies. He’s a PC enthusiast and he… read more
Updated on January 17, 2023
- VMware allows you to run several virtual machines in a sandbox environment.
- You can install VMware Tools manually or add an optical drive if the installation option is grayed out.
XINSTALL BY CLICKING THE DOWNLOAD FILE
This software will repair common computer errors, protect you from file loss, malware, hardware failure and optimize your PC for maximum performance. Fix PC issues and remove viruses now in 3 easy steps:
- Download Restoro PC Repair Tool that comes with Patented Technologies (patent available here).
- Click Start Scan to find Windows issues that could be causing PC problems.
- Click Repair All to fix issues affecting your computer’s security and performance
- Restoro has been downloaded by 0 readers this month.
On VMware, if the Install VMware Tools option is grayed out, you won’t be able to perform simple operations.
Some of these operations include copying and pasting data between guest and host machines.
Asides the copying function, the VMware Control Panel also features other useful utilities that improve your VMware experience.
Virtualization is crucial for testing applications and operating systems in a sandbox without altering or interfering with the host computer.
However, an absence of VMware tools defeats the purpose and ruins your experience using VMware.
Thankfully, this issue is not a complicated one. You can fix it easily with the solutions we’ll provide here.
Scroll down to find out why the Install VMware Tools option is unavailable, and some more useful information about the VMware toolset.
The Install VMware tools option grays out when you start installing it on a guest system with the function already mounted. It also happens when the guest machine doesn’t have a virtual optical drive.
VMware tools can even grey out if you select the option during the VMware installation and the log confirms the download. In the section that follows, you will learn how to install VMware tools if grated out.
What is the latest version of VMware tools?
When you use VMware, you need VMware Tools to effectively share folders between the guest and host operating systems.
With VMware Tools, you can copy and paste files directly between the connected systems.
Here are the most useful tools that come included in the VMware toolkit.
- VMware OS Optimization Tool – a useful tool for VMware Horizon. It expands your usability of guest systems by tweaking features and services.
- VMware Workstation for Windows – a robust virtualization tool that helps you run several operating systems on one host system.
- VMware Fusion – a computer utility that lets you install and use virtual machines on a host operating system
1. Add an optical drive and install VMware tools
- Power off your virtual machine.
- Launch VMware Workstation Player and right-click on the virtual machine.
- Go to Settings and modify the hardware settings.
- Navigate to the Hardware tab on the left-hand sidebar, select the CD or DVD drive, and click on Remove.
- On the Hardware tab, remove the Floppy Drive the same way you did for the CD/DVD drive.
- Click on Add, choose CD/DVD, and then hit Finish.
- Click OK to exit the window and begin to use the virtual machine.
- Wait for the VM to load up as normal. On completion of the booting process, go to the menu at the top left-hand area.
- Navigate to Player, then click Manage, and select the Install VMware Tool option.
After completing the steps above, then the install VMware Tools grayed out option will now be available.
2. Install the missing component manually
Set up your VM
- Download the latest version of VMware Tools.
- Turn on the virtual machine.
- Configure the CD/DVD drive to detect your hard drive automatically (if you’re using an ISO image file).
- Log in as an Administrator.
- Select the Menu command and mount the VMware virtual disk on the guest machine.
- Choose Interactive Tools Upgrade or Interactive Tools Installation and hit the OK button.
- Click on OK if this is the first time installing VMware Tools.
Launch the installation wizard manually
- Open the Run dialog box by pressing the Windows key + R combination.
- Enter D:setup.exe (replace D with the letter for your first virtual CD-ROM drive).
- Follow the on-screen guide to complete the manual installation of VMware.
This method doesn’t only work on Windows 10 virtual machines but also on macOS, Linux, as well as older Windows editions.
We hope that you found this guide useful and that you managed to sort out your VMware virtual machines.
If you want to share your experience with us, don’t hesitate to leave a comment in the section found below this guide.
Still having issues? Fix them with this tool:
SPONSORED
If the advices above haven’t solved your issue, your PC may experience deeper Windows problems. We recommend downloading this PC Repair tool (rated Great on TrustPilot.com) to easily address them. After installation, simply click the Start Scan button and then press on Repair All.
Newsletter
by Milan Stanojevic
Milan has been enthusiastic about technology ever since his childhood days, and this led him to take interest in all PC-related technologies. He’s a PC enthusiast and he… read more
Updated on January 17, 2023
- VMware allows you to run several virtual machines in a sandbox environment.
- You can install VMware Tools manually or add an optical drive if the installation option is grayed out.
XINSTALL BY CLICKING THE DOWNLOAD FILE
This software will repair common computer errors, protect you from file loss, malware, hardware failure and optimize your PC for maximum performance. Fix PC issues and remove viruses now in 3 easy steps:
- Download Restoro PC Repair Tool that comes with Patented Technologies (patent available here).
- Click Start Scan to find Windows issues that could be causing PC problems.
- Click Repair All to fix issues affecting your computer’s security and performance
- Restoro has been downloaded by 0 readers this month.
On VMware, if the Install VMware Tools option is grayed out, you won’t be able to perform simple operations.
Some of these operations include copying and pasting data between guest and host machines.
Asides the copying function, the VMware Control Panel also features other useful utilities that improve your VMware experience.
Virtualization is crucial for testing applications and operating systems in a sandbox without altering or interfering with the host computer.
However, an absence of VMware tools defeats the purpose and ruins your experience using VMware.
Thankfully, this issue is not a complicated one. You can fix it easily with the solutions we’ll provide here.
Scroll down to find out why the Install VMware Tools option is unavailable, and some more useful information about the VMware toolset.
The Install VMware tools option grays out when you start installing it on a guest system with the function already mounted. It also happens when the guest machine doesn’t have a virtual optical drive.
VMware tools can even grey out if you select the option during the VMware installation and the log confirms the download. In the section that follows, you will learn how to install VMware tools if grated out.
What is the latest version of VMware tools?
When you use VMware, you need VMware Tools to effectively share folders between the guest and host operating systems.
With VMware Tools, you can copy and paste files directly between the connected systems.
Here are the most useful tools that come included in the VMware toolkit.
- VMware OS Optimization Tool – a useful tool for VMware Horizon. It expands your usability of guest systems by tweaking features and services.
- VMware Workstation for Windows – a robust virtualization tool that helps you run several operating systems on one host system.
- VMware Fusion – a computer utility that lets you install and use virtual machines on a host operating system
1. Add an optical drive and install VMware tools
- Power off your virtual machine.
- Launch VMware Workstation Player and right-click on the virtual machine.
- Go to Settings and modify the hardware settings.
- Navigate to the Hardware tab on the left-hand sidebar, select the CD or DVD drive, and click on Remove.
- On the Hardware tab, remove the Floppy Drive the same way you did for the CD/DVD drive.
- Click on Add, choose CD/DVD, and then hit Finish.
- Click OK to exit the window and begin to use the virtual machine.
- Wait for the VM to load up as normal. On completion of the booting process, go to the menu at the top left-hand area.
- Navigate to Player, then click Manage, and select the Install VMware Tool option.
After completing the steps above, then the install VMware Tools grayed out option will now be available.
2. Install the missing component manually
Set up your VM
- Download the latest version of VMware Tools.
- Turn on the virtual machine.
- Configure the CD/DVD drive to detect your hard drive automatically (if you’re using an ISO image file).
- Log in as an Administrator.
- Select the Menu command and mount the VMware virtual disk on the guest machine.
- Choose Interactive Tools Upgrade or Interactive Tools Installation and hit the OK button.
- Click on OK if this is the first time installing VMware Tools.
Launch the installation wizard manually
- Open the Run dialog box by pressing the Windows key + R combination.
- Enter D:setup.exe (replace D with the letter for your first virtual CD-ROM drive).
- Follow the on-screen guide to complete the manual installation of VMware.
This method doesn’t only work on Windows 10 virtual machines but also on macOS, Linux, as well as older Windows editions.
We hope that you found this guide useful and that you managed to sort out your VMware virtual machines.
If you want to share your experience with us, don’t hesitate to leave a comment in the section found below this guide.
Still having issues? Fix them with this tool:
SPONSORED
If the advices above haven’t solved your issue, your PC may experience deeper Windows problems. We recommend downloading this PC Repair tool (rated Great on TrustPilot.com) to easily address them. After installation, simply click the Start Scan button and then press on Repair All.
Newsletter
Содержание
- VMWare Tools не устанавливается: VMWare Tools installation cannot be started while Easy Install is in progress
- install vmware tools не активно
- … заметки IT’шника…
- Не устанавливается VMware tools? есть причина.
- How to install VMWare tools if the option is grayed out
- Here’s what I tried (and failed)
- How to install VMWare tools if the option is grayed out
- About Ashwin
- Related content
- How to enable the new TweetDeck Preview interface in Firefox and Chrome
- Use the Windows Task Manager to find power leeching processes quickly
- How to download YouTube videos with Internet Download Manager
- How to turn off the News and Interests feature of Windows 10
- How to turn off Text Predictions in Word and Outlook
- Create your own SDelete shortcut for secure file deletion
- Comments
- Install vmware tools не активно windows 7
- install vmware tools не активно
- … заметки IT’шника…
- Не устанавливается VMware tools? есть причина.
При установке VMware Tools на новую виртуалку очень часто, а может быть даже и всегда, получаю ошибку «VMWare Tools installation cannot be started while Easy Install is in progress», что переводится примерно так «Установка VMware Tools не может быть запущена в то время как идет Easy Install «.
Не помню уже сколько времени я потратил на поиск того, как отключить Easy Install в настройках самой программы, но даже похожего в настройках не нашел. Искал как получается всегда не там где нужно. Как потом оказалось, эта ошибка возникает по вине не размонтированной загрузочной дискеты в флоппи дисководе, необходимой для установки Операционной Системы. Вот это нами мешает. Если вы зайдете на флоппи дисковод то увидите примерно тоже самое, что и на картинке внизу.
Чтобы навсегда избавиться от ошибки надо сделать несколько действий. Если виртуальная машина у вас запущена, то ее следует выключить и зайти в настройки. В настройки можно попасть выбрав вашу машину и нажав на «Edit virtual machine settings» или нажав комбинацию клавиш CTRL+D. В настройках следует перейти на вкладку Floppy и в группе Connection выбрать «Use physical drive», в выпадающем меню «Auto detect» и нажать OK. Вот мы и размонтировали загрузочную дискету, которая нам мешала установить VMware Tools.
Загрузив Операционную Систему вы сможете без ошибок установить VMware Tools.
Источник
Бывает так что по каким-то причинам вы не можете ни установить дополнения для виртуальной машины VMWare ни загрузить их через саму программу.
В таком случае придется или переустанавливать виртуальную машину, что мягко говоря «не очень» или искать отдельно VMWare Tools.
Оказывается есть открытый официальный источник, где можно загрузить VMWare Tools не только для Windows, но и для других ОС.
Но после этого будьте готовы к следующей преграде — это перенести дополнения в виртуальную машину, для этого используйте функцию Map жесткого диска в настройках виртуальной ОС. Это позволит открыть диск в физической ОС.
Здесь можно загрузить последние дополнения для вашей виртуальной машины.
Переходим по ссылке.
В самом низу должна быть папка latest, в которой должны быть последние версии VMWare Tools для разных ОС. Переходим в нее.
После этого в зависимости от ОС выбираете папку, у меня это папка windows.
После чего выбираем архитектуру, у меня это x86.
После этого мы попадаем уже собственно в папку нашего дополнения.
Осталось только сохранить и установить на виртуальную машину, то есть именно сперва перенести любым способом в виртуальную и уже там установить.
Для того чтобы перенести стоит просто открыть виртуальный диск в физ. системе и туда «закинуть» это дополнение. Открыть можно через настройки, там где диск в меню Utilities выбрать Map и снять галочку «только чтение», после чего откроется доступ к виртуальному диску.
Рубрика: Программы / Метки: VMWare / 19 Ноябрь 2014 / Подробнее
При установке VMware Tools на новую виртуалку очень часто, а может быть даже и всегда, получаю ошибку «VMWare Tools installation cannot be started while Easy Install is in progress», что переводится примерно так «Установка VMware Tools не может быть запущена в то время как идет Easy Install «.
Не помню уже сколько времени я потратил на поиск того, как отключить Easy Install в настройках самой программы, но даже похожего в настройках не нашел. Искал как получается всегда не там где нужно. Как потом оказалось, эта ошибка возникает по вине не размонтированной загрузочной дискеты в флоппи дисководе, необходимой для установки Операционной Системы. Вот это нами мешает. Если вы зайдете на флоппи дисковод то увидите примерно тоже самое, что и на картинке внизу.
Чтобы навсегда избавиться от ошибки надо сделать несколько действий. Если виртуальная машина у вас запущена, то ее следует выключить и зайти в настройки. В настройки можно попасть выбрав вашу машину и нажав на «Edit virtual machine settings» или нажав комбинацию клавиш CTRL+D. В настройках следует перейти на вкладку Floppy и в группе Connection выбрать «Use physical drive», в выпадающем меню «Auto detect» и нажать OK. Вот мы и размонтировали загрузочную дискету, которая нам мешала установить VMware Tools.
Загрузив Операционную Систему вы сможете без ошибок установить VMware Tools.
… заметки IT’шника…
Работая с виртуальными машинами, всегда стараюсь устанавливать в гостевую систему инструментарий от среды виртуализации. Это дает более гибкое управление и мониторинг за состоянием гостевой системы. Чаще мне приходится работать с виртуализацией от VMware, на различных платформах. Установка VMware tools в среде MS Wndows — вообще никогда не вызывает проблем. С установкой в системах GNU/Linux приходится больше работать вручную.
Казалось бы в чем может быть дело? Однако уже в конце рабочего дня у меня включился мозг и я вспомнил процесс инсталяции VMware Tools в среде Линукса. Там кликая пункт меню — мы просто помещаем образ в устройство чтения компакт дисков. А потом монтируем и сетапим все ручками. А вот полная автоматизация процесса в Windows заблокировала мой мозг…
Оказывается при конвертации и переносе виртуальной машниы, VMware Converter отрубил все лишние устройства, в том числе был и виртуальный привод копакт дисков…. После ручного добавления в виртуальную машину нвоого привода установка Tools’ов прошла в привычном автоматическом режиме….
Вот так всегда, можно над одной мелочью «битый час» возиться и изводить свой разум 🙂
Источник
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)
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.
About Ashwin
Related content
How to enable the new TweetDeck Preview interface in Firefox and Chrome
Use the Windows Task Manager to find power leeching processes quickly
How to download YouTube videos with Internet Download Manager
How to turn off the News and Interests feature of Windows 10
How to turn off Text Predictions in Word and Outlook
Create your own SDelete shortcut for secure file deletion
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 =
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.
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.
Thank, Ten seconds to find your tips and five sends to fix my issue.
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 … 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.
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 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.
this fantastic even the vendor has no solution
Really, Thank you sooooo much
Worked a treat, thanks for posting
It works perfectly for fusion
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:
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 😊
Thanks a lot, got it working by following your guide.
Thak you very much. This really works! Saved me hours of frustration.
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.
Источник
Bugatt1 (3 posts since Dec 5, 2013) Oct 13, 2014 11:23 PM
в свойствах ВМ для CD-ROM стоит галка Connected?
Нет не стоит, и поставить не получается поле не активно
прикрепи скрин с настройками вм.
скрин в прикреплённом файле
машина выключена, пункты CONNECTED не активны
добавлял CD-ROM, тоже самое
После запуска установки из меню InstallUpgrade VMware tools, если в клиенте руками попробывать примапить диск к виртуалке что пишет?
Да, кстати, а какая операционная система выбрана в настройках ВМ, и соответствует ли она реально установленной ОС?
В настройках ВМ выбрана ОС Windows 7 х86, фактически она же и стоит
После запуска установки из меню InstallUpgrade VMware tools, вылазит стандартное окно и ВСЁ, больше ничего не происходит, исошник не монтируется
Руками можно примонтировать iso из datastore, но это не по феншую
Та же самая проблема, как вручную можно примапить образ vmtools? Т.к. даже скачав в гостевую машину, vmtools из инета, не получается их запустить.
Только в одной виртуалке вы наблюдаете подобное поведение или в разных?
Запостите vmware.log виртуальной машины после запуска попытки инсталляции тулзов.
Источник
Бывает так что по каким-то причинам вы не можете ни установить дополнения для виртуальной машины VMWare ни загрузить их через саму программу.
В таком случае придется или переустанавливать виртуальную машину, что мягко говоря «не очень» или искать отдельно VMWare Tools.
Оказывается есть открытый официальный источник, где можно загрузить VMWare Tools не только для Windows, но и для других ОС.
Но после этого будьте готовы к следующей преграде — это перенести дополнения в виртуальную машину, для этого используйте функцию Map жесткого диска в настройках виртуальной ОС. Это позволит открыть диск в физической ОС.
Здесь можно загрузить последние дополнения для вашей виртуальной машины.
Переходим по ссылке.
В самом низу должна быть папка latest, в которой должны быть последние версии VMWare Tools для разных ОС. Переходим в нее.
После этого в зависимости от ОС выбираете папку, у меня это папка windows.
После чего выбираем архитектуру, у меня это x86.
После этого мы попадаем уже собственно в папку нашего дополнения.
Осталось только сохранить и установить на виртуальную машину, то есть именно сперва перенести любым способом в виртуальную и уже там установить.
Для того чтобы перенести стоит просто открыть виртуальный диск в физ. системе и туда «закинуть» это дополнение. Открыть можно через настройки, там где диск в меню Utilities выбрать Map и снять галочку «только чтение», после чего откроется доступ к виртуальному диску.
Рубрика: Программы / Метки: VMWare / 19 Ноябрь 2014 / Подробнее
При установке VMware Tools на новую виртуалку очень часто, а может быть даже и всегда, получаю ошибку «VMWare Tools installation cannot be started while Easy Install is in progress», что переводится примерно так «Установка VMware Tools не может быть запущена в то время как идет Easy Install «.
Не помню уже сколько времени я потратил на поиск того, как отключить Easy Install в настройках самой программы, но даже похожего в настройках не нашел. Искал как получается всегда не там где нужно. Как потом оказалось, эта ошибка возникает по вине не размонтированной загрузочной дискеты в флоппи дисководе, необходимой для установки Операционной Системы. Вот это нами мешает. Если вы зайдете на флоппи дисковод то увидите примерно тоже самое, что и на картинке внизу.
Чтобы навсегда избавиться от ошибки надо сделать несколько действий. Если виртуальная машина у вас запущена, то ее следует выключить и зайти в настройки. В настройки можно попасть выбрав вашу машину и нажав на «Edit virtual machine settings» или нажав комбинацию клавиш CTRL+D. В настройках следует перейти на вкладку Floppy и в группе Connection выбрать «Use physical drive», в выпадающем меню «Auto detect» и нажать OK. Вот мы и размонтировали загрузочную дискету, которая нам мешала установить VMware Tools.
Загрузив Операционную Систему вы сможете без ошибок установить VMware Tools.
… заметки IT’шника…
Работая с виртуальными машинами, всегда стараюсь устанавливать в гостевую систему инструментарий от среды виртуализации. Это дает более гибкое управление и мониторинг за состоянием гостевой системы. Чаще мне приходится работать с виртуализацией от VMware, на различных платформах. Установка VMware tools в среде MS Wndows — вообще никогда не вызывает проблем. С установкой в системах GNU/Linux приходится больше работать вручную.
Казалось бы в чем может быть дело? Однако уже в конце рабочего дня у меня включился мозг и я вспомнил процесс инсталяции VMware Tools в среде Линукса. Там кликая пункт меню — мы просто помещаем образ в устройство чтения компакт дисков. А потом монтируем и сетапим все ручками. А вот полная автоматизация процесса в Windows заблокировала мой мозг…
Оказывается при конвертации и переносе виртуальной машниы, VMware Converter отрубил все лишние устройства, в том числе был и виртуальный привод копакт дисков…. После ручного добавления в виртуальную машину нвоого привода установка Tools’ов прошла в привычном автоматическом режиме….
Вот так всегда, можно над одной мелочью «битый час» возиться и изводить свой разум 🙂
Источник
Не получается установить. Пожалуйста, посмотрите, где ошибка
user@user-virtual-machine:/tmp/vmware-tools-distrib$ sudo ./vmware-install.pl -dThe installer has detected an existing installation of open-vm-tools packages
on this system and will not attempt to remove and replace these user-space
applications. It is recommended to use the open-vm-tools packages provided by
the operating system. If you do not want to use the existing installation of
open-vm-tools packages and use VMware Tools, you must uninstall the
open-vm-tools packages and re-run this installer.
The packages that need to be removed are:
open-vm-tools
Packages must be removed with the --purge option.
The installer will next check if there are any missing kernel drivers. Type yes
if you want to do this, otherwise type no [yes]
INPUT: [yes] default
A previous installation of VMware Tools has been detected.
The previous installation was made by the tar installer (version 4).
Keeping the tar4 installer database format.
You have a version of VMware Tools installed. Continuing this install will
first uninstall the currently installed version. Do you wish to continue?
(yes/no) [yes]
INPUT: [yes] default
Uninstalling the tar installation of VMware Tools.
Stopping services for VMware Tools
Stopping VMware Tools services in the virtual machine:
VMware User Agent (vmware-user): done
Unmounting HGFS shares: done
Guest filesystem driver: done
Stopping Thinprint services in the virtual machine:
Stopping Virtual Printing daemon: done
depmod: WARNING: could not open /lib/modules/4.15.0-62-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-62-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-20-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-20-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-34-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-34-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-36-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-36-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-30-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-30-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-58-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-58-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-33-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-33-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-60-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-60-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-55-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-55-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-32-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-32-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-29-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-29-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-38-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-38-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-23-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-23-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-22-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-22-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-24-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-24-generic/modules.builtin: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-64-generic/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.15.0-64-generic/modules.builtin: No such file or directory
The removal of VMware Tools 10.2.0 build-7259539 for Linux completed
successfully.
Installing VMware Tools.
In which directory do you want to install the binary files?
[/usr/bin]
INPUT: [/usr/bin] default
What is the directory that contains the init directories (rc0.d/ to rc6.d/)?
[/etc]
INPUT: [/etc] default
What is the directory that contains the init scripts?
[/etc/init.d]
INPUT: [/etc/init.d] default
In which directory do you want to install the daemon files?
[/usr/sbin]
INPUT: [/usr/sbin] default
In which directory do you want to install the library files?
[/usr/lib/vmware-tools]
INPUT: [/usr/lib/vmware-tools] default
The path "/usr/lib/vmware-tools" does not exist currently. This program is
going to create it, including needed parent directories. Is this what you want?
[yes]
INPUT: [yes] default
In which directory do you want to install the documentation files?
[/usr/share/doc/vmware-tools]
INPUT: [/usr/share/doc/vmware-tools] default
The path "/usr/share/doc/vmware-tools" does not exist currently. This program
is going to create it, including needed parent directories. Is this what you
want? [yes]
INPUT: [yes] default
The installation of VMware Tools 10.3.10 build-13959562 for Linux completed
successfully. You can decide to remove this software from your system at any
time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".
Before running VMware Tools for the first time, you need to configure it by
invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want
this program to invoke the command for you now? [yes]
INPUT: [yes] default
You have chosen to install VMware Tools on top of an open-vm-tools package.
You will now be given the option to replace some commands provided by
open-vm-tools. Please note that if you replace any commands at this time and
later remove VMware Tools, it may be necessary to re-install the open-vm-tools.
WARNING: It appears your system is missing the required /usr/bin/vmhgfs-fuse
Initializing...
Making sure services for VMware Tools are stopped.
Stopping VMware Tools services in the virtual machine:
VMware User Agent (vmware-user): done
Unmounting HGFS shares: done
Guest filesystem driver: done
The module vmci has already been installed on this system by another installer
or package and will not be modified by this installer.
The module vsock has already been installed on this system by another installer
or package and will not be modified by this installer.
The module vmxnet3 has already been installed on this system by another
installer or package and will not be modified by this installer.
The module pvscsi has already been installed on this system by another
installer or package and will not be modified by this installer.
The module vmmemctl has already been installed on this system by another
installer or package and will not be modified by this installer.
The VMware Host-Guest Filesystem allows for shared folders between the host OS
and the guest OS in a Fusion or Workstation virtual environment. Do you wish
to enable this feature? [yes]
INPUT: [yes] default
The vmxnet driver is no longer supported on kernels 3.3 and greater. Please
upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)
Skipping configuring automatic kernel modules as no drivers were installed by
this installer.
Skipping rebuilding initrd boot image for kernel as no drivers to be included
in boot image were installed by this installer.
The configuration of VMware Tools 10.3.10 build-13959562 for Linux for this
running kernel completed successfully.
Found VMware Tools CDROM mounted at /media/user/VMware Tools. Ejecting device
/dev/sr0 ...
Found VMware Tools CDROM mounted at /mnt/cdrom. Ejecting device /dev/sr0 ...
Enjoy,
--the VMware team
I encounter this error:
The path /usr/src/linux/include is not an existing directory.
Hi there are still issues as listed below. Please advise
ronald@ronald-virtual-machine:~/Desktop/vmware tools/vmware-tools-distrib$ sudo ./vmware-install.pl
[sudo] password for ronald:
A previous installation of VMware Tools has been detected.
The previous installation was made by the tar installer (version 4).
Keeping the tar4 installer database format.
You have a version of VMware Tools installed. Continuing this install will
first uninstall the currently installed version.
Do you wish to continue? (yes/no) [yes]
Error: Unable to execute "/usr/bin/vmware-uninstall-tools.pl.
Uninstall failed. Please correct the failure and re run the install.
Execution aborted.
ronald@ronald-virtual-machine:~/Desktop/vmware tools/vmware-tools-distrib$ `chmod +x /usr/bin/vmware-uninstall-tools.pl`
chmod: cannot access `/usr/bin/vmware-uninstall-tools.pl': No such file or directory
jobin
26.6k16 gold badges99 silver badges116 bronze badges
asked May 14, 2011 at 9:59
0
This also happened to me when I interrupted vmware tools upgrade.
it seems, the first thing the upgrade does is delete all files in the system. the uninstall script being the first one and that’s why you can’t find it.
I don’t understand why the installation gets interrupted+ if the uninstall script is not found (for me, that’s just a bad decision), but the mounted device comes with its own script which you can use to delete everything.
a simple
locate vmware-uninstall
outputed its location and for me it was in
/home/my_username/Desktop/vmware-tools-distrib/bin/vmware-uninstall-tools.pl
For you, the only difference should be ronald instead of *my_username*.
Hope that helps.
answered Nov 22, 2012 at 8:42
RorchackhRorchackh
2112 silver badges5 bronze badges
Run sudo rm -R /etc/vmware OR sudo rm -R /etc/vmware-tools
this will remove settings and you can install new one.
answered Jun 20, 2013 at 7:35
Hojat TaheriHojat Taheri
5,1996 gold badges20 silver badges26 bronze badges
1
you should install the header first
apt-get install linux-headers-2.6.10-5-386(name of your kernel)
and then enter on the vmware installation:
/usr/src/linux-headers-2.6.10-5-386/include
It should help
Jorge Castro
69.9k123 gold badges461 silver badges652 bronze badges
answered May 2, 2011 at 7:03
It appears that vmware is trying to uninstall the older version before installing the newer one, but is failing to do so.
-
I would manually uninstall the old version of vmware tools by typing the following command into the terminal:
sudo apt-get remove vmware
Note: the word «vmware» is just a guess as to what the name of this package is. If this gives you an error like «Unable to locate package» then try changing the word vmware to whatever you think the package name is.
- Once vmware is unstalled, try installing the newer package.
Jorge Castro
69.9k123 gold badges461 silver badges652 bronze badges
answered May 14, 2011 at 23:47
What worked for me was the last answer provided in this thread by Amir Arian — so simple and yet I could not find it easily elsewhere.
If you followed VMware instructions, you extracted the VMware tools to /tmp. So, you should have /tmp/vmware-tools-distrib. Inside that you have a bin directory and there is the vmware-uninstall-tools.pl file.
cp /tmp/vmware-tools-distrib/bin/vmware-uninstall-tools.pl /usr/bin/
Then run the installer once more:
/tmp/vmware-tools-distrib/vmware-install.pl
It will come back with an error that might look like this:
"Can't exec "/etc/vmware-caf/pme/install/preupgrade.sh": No such file or directory at /usr/bin/vmware-uninstall-tools.pl line 4115."
However, the installer will keep working and eventually proceed to the installation phase.
answered Aug 11, 2016 at 15:16
I solved this same problem doing fixes below. I would summarize issue as aborting a vmware-install when kernel headers not found. Pressing Ctrl-C during vmware-install can cause the «Error: Unable to execute «/usr/bin/vmware-uninstall-tools.pl.» in several cases in general.
To install the kernel headers needed by vmware tools run uname -r (to get kernel name) and apt-get below. Might end up needing to do this even after a ‘sudo apt-get install build-essentials’ when you update to a leading edge kernel via ‘sudo apt-get dist-upgrade’ or manually. I added build-essential to apt-get because you always need it for vmware tools.
$ uname -r
3.5.0-46-generic
$sudo apt-get install linux-headers-3.5.0-46-generic build-essential
To correct «Error: Unable to execute «/usr/bin/vmware-uninstall-tools.pl.» do a sudo copy of the vmware-uninstall-tools.pl from the new vmware tools you want to install to the location it is looking for it (typically /usr/bin)
As an example, I usually open a terminal and change directory to /tmp then click on VMware menu Manage then option «Reinstall VMware Tools…» then (once VMware mounts its CDROM of latest tools) copy tar from read-only CDROM to /tmp as below (based on a version 9.6.1-1378637)
$ cd /tmp
$ cp /media/my_username/VMware Tools/VMwareTools-9.6.1-1378637.tar.gz .
$ tar -xzf VMwareTools-9.6.1-1378637.tar.gz
$ cd vmware-tools-distrib
$ cp bin/vmware-uninstall-tools.pl /usr/bin/
$ sudo ./vmware-install.pl
answered Mar 1, 2014 at 20:52
The vmware install script checks if the package is present on your installation. The solution is to purge the package:
sudo dpkg --purge open-vm-tools
answered Jan 30, 2016 at 18:02
copy uninstall script from vmware-tools-distrib/bin/ to /usr/bin as following command:
cp path_to_extracted_vmware-tools_dir/bin/vmware-uninstall-tools.pl /usr/bin/.
then run install script again.
Jorge Castro
69.9k123 gold badges461 silver badges652 bronze badges
answered May 21, 2011 at 8:38
This was caused by me killing the install (CNTRL C) because I forgot to add -d to automate the install with defaults. The initial run of the script creates the /etc/vmware-tools folder, because that exists the script thinks vmware-tools is already installed.
Simple answer is:
sudo rm -R /etc/vmware-tools
then re-run the installation script.
answered Jan 31, 2017 at 13:08
I ran into this when I upgrade the version of VMWare on my host, and followed its instructions for updating the client.
After I’d mounted the virtual CD image, untarred and ran the installed, I saw the message:
The installer has detected an existing installation of open-vm-tools packages on this system and will not attempt to remove and replace these user-space applications. It is recommended to use the open-vm-tools packages provided by the operating system. If you do not want to use the existing installation of open-vm-tools packages and use VMware Tools, you must uninstall the open-vm-tools packages and re-run this installer. The packages that need to be removed are:
open-vm-tools
Packages must be removed with the —purge option.
From this it is clear what muast be done to remove them:
sudo apt-get remove —purge open-vm-tools
I did that, and re-ran the installer. And this time I got:
open-vm-tools packages are available from the OS vendor and VMware recommends using open-vm-tools packages. See http://kb.vmware.com/kb/2073803 for more
information.
Do you still want to proceed with this installation? [no] no
So I gave up on installing the client software from the virtual ISO in the host, and just ran
sudo apt-get install open-vm-tools
IOW, the right answer for this issue isn’t to find a way to work around installing the vm tools from the host ISO, but to not install the vm tools from the host ISO, but to update the open-vm-tools package, instead.
answered Jul 20, 2019 at 13:25
check
Best Answer
pure capsaicin
VMware Expert
-
check
360
Best Answers -
thumb_up
998
Helpful Votes
End the tools
Choose edit on the VM, select to mount an ISO from datastore, choose vmimages folder, then windows.iso
Run it in manually
Was this post helpful?
thumb_up
thumb_down
View Best Answer in replies below
6 Replies
-
pure capsaicin
VMware Expert
-
check
360
Best Answers -
thumb_up
998
Helpful Votes
Thats no issue.
press ok, go in to the VM and install the tools manually. REboot and it should be good to go
Was this post helpful?
thumb_up
thumb_down
-
check
-
I’ve tried that already. What happens is after I hit OK, it goes to a «Initiated VMware Tools Installer Mount» Task, then gets stuck there. If I go back into the Guest menu (where the Install/Upgrade VMware Tools selection was to initiate it) the selection has changed to «End VMware Tools Install» and it stays there until I click on it and then it goes back to «Install/upgrade…»
Was this post helpful?
thumb_up
thumb_down
-
pure capsaicin
VMware Expert
-
check
360
Best Answers -
thumb_up
998
Helpful Votes
End the tools
Choose edit on the VM, select to mount an ISO from datastore, choose vmimages folder, then windows.iso
Run it in manually
Was this post helpful?
thumb_up
thumb_down
-
check
-
Excellent! Thanks Rod-IT! It worked. That was exactly the guidance I needed.
Thanks again!
Seth
Was this post helpful?
thumb_up
thumb_down
-
pure capsaicin
VMware Expert
-
check
360
Best Answers -
thumb_up
998
Helpful Votes
Be sure to mark best answer
Was this post helpful?
thumb_up
thumb_down
-
check
-
Done. Thanks again!
Was this post helpful?
thumb_up
thumb_down