Hi,
I'm working with vmWare Workstation on Tuxedo laptop (Linux OS)
After updating the kernel vmWare Workstation don't work on my maschine.
I've tryed to update to the new Version with
sudo bash VMware-Workstation-Full-17.5.0-22583795.x86_64.bundle
Extracting VMware Installer...done.
Uninstalling VMware Workstation 17.0.2
Uninstalling VMware Workstation 17.0.2
Deconfiguring...
after this the script stopps.
I've tryed to unistall the tools manually with
sudo vmware-installer -u vmware-workstation --console
this also don't work and vmWare Player is still installed.
What do I wrong or how could I find a logfile or details why the installation fails?
Thanks in advance
Kind regards
Dirk
P.S. I have a license from my company account eglv.de
In general, I've found it more reliable to uninstall the prior version before installing the new one.
Furthermore, I've found it is generally better to uninstall with the old version's installer.
This is what I did to upgrade the other day:
$ ./VMware-Workstation-Full-17.0.0-20800274.x86_64.bundle --uninstall-product vmware-workstation
then:
$ ./VMware-Workstation-Full-17.5.0-22583795.x86_64.bundle --install-bundle VMware-Workstation-Full-17.5.0-22583795.x86_64.bundle
Clearly, your versions may vary.
Hi and thanks for supporting me
that does not work for me, same result, here the output:
sudo bash ./VMware-Workstation-Full-17.0.2-21581411.x86_64.bundle --uninstall-product vmware-workstation
Extracting VMware Installer...done.
All configuration information is about to be removed. Do you wish to
keep your configuration files? You can also input 'quit' or 'q' to
cancel uninstallation. [yes]:
Uninstalling VMware Workstation 17.0.2
Deconfiguring...All configuration information is about to be removed. Do you wish to
keep your configuration files? You can also input 'quit' or 'q' to ] 1%
cancel uninstallation. [yes]:
Uninstalling VMware Workstation 17.0.2
Deconfiguring....
after the second time Deconfituring the script stops without any reason??
Sorry, I don't know anything more about the internals of the installer, so can't be of more help there.
<ignore> I hate to say this, but when that has happened to me in the past, I uninstalled by brute force. I basically searched for all the locations where there were vmware files, and manually deleted them. As I didn't know how to tell where the files were, I searched for any files with expressions like `# find / -iname "*vm*" 2>/dev/null` and then noted directories, etc. and forcibly deleted them being very careful to avoid removing unrelated files, configuration files, and the VM's themselves. If I wasn't sure, I moved or renamed them in a way that I'd not forget how to put them back if something broke. Clearly, its more complicated than one command; I can't say I recommend this as it is easy to break a system. I was able to do it, and have a couple of times over the years. In my case, it was a personal system, so playing fast and loose wasn't really a huge risk; I keep my data on separate disks from the OS.</ignore>
I had a very similar looking problem on OpenSUSE Tumbleweed . Check /var/log/vmware-installer
In my case there was this error message:
"Exception: VMIS:[Errno 2] No such file or directory: path('/etc/security/limits.conf')
and the workaround was to create the missing file with touch
so at the moment I have no solution, what I found in the /var/log/vmware-installer is
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2621: ordinal not in range(128)
A search in google does not lead to an answer, (I should check the passwd file for user with non ascii character)
In my case no such user?
Then I found a post that I have to manually uninstall everything, what I have planned for next week, strange
https://kb.vmware.com/s/article/38
We have a second maschine (identical to mine) that we could update without problems
Interesting. I have experienced "UnicodeEncodeError: 'ascii' codec can't encode character '\u2018' in position 35387: ordinal not in range(128)" during install.
@Dirk9 We have tried the same on Ubuntu 22 and Rhel 9 hosts. WE did not see any issue.
After giving write access to the bundle file of Workstation 17.5 bundle file,try executing below command-
sudo ./VMware-Workstation-Full-17.5.0-22583795.x86_64.bundle
