VMware tools install fails - Centos 6.2 on VMware Workstation 8

Similar Questions

• VMware Workstation 12.1.1 Pro is unable to install the network grows on CentOS 6.8 host

  Just upgraded my 6.7 CentOS Server (where the VMware Workstation 12.1.1 worked fine) to 6.8.

  After a reboot, VMware has done, it is usual thing where she wanted to reinstall its readers. He doesn't have to install the network component. Here are my logs:

  2016-05-28T18:21:09.477-07:00| vthread-4| I125: Log for VMware Workstation pid=27658 version=12.1.1 build=build-3770994 option=Release
  2016-05-28T18:21:09.477-07:00| vthread-4| I125: The process is 64-bit.
  2016-05-28T18:21:09.477-07:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8
  2016-05-28T18:21:09.477-07:00| vthread-4| I125: Host is Linux 2.6.32-642.el6.x86_64 CentOS release 6.8 (Final)
  2016-05-28T18:21:09.476-07:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.
  2016-05-28T18:21:09.476-07:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
  2016-05-28T18:21:09.476-07:00| vthread-4| I125: DictionaryLoad: Cannot open file "/home/sa_schewee/.vmware/config": No such file or directory.
  2016-05-28T18:21:09.476-07:00| vthread-4| I125: PREF Optional preferences file not found at /home/sa_schewee/.vmware/config. Using default values.
  2016-05-28T18:21:09.501-07:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-27658.log
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: Obtaining info using the running kernel.
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: Created new pathsHash.
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.518-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.518-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.587-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
  2016-05-28T18:21:09.587-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Read 12201 symbol versions
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmmon module.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmnet module.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmblock module.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmci module.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vsock module.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Setting vsock to depend on vmci.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Invoking modinfo on "vmmon".
  2016-05-28T18:21:09.600-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
  2016-05-28T18:21:09.600-07:00| vthread-4| I125: Invoking modinfo on "vmnet".
  2016-05-28T18:21:09.601-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
  2016-05-28T18:21:09.601-07:00| vthread-4| I125: Invoking modinfo on "vmblock".
  2016-05-28T18:21:09.603-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
  2016-05-28T18:21:09.603-07:00| vthread-4| I125: Invoking modinfo on "vmci".
  2016-05-28T18:21:09.605-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
  2016-05-28T18:21:09.605-07:00| vthread-4| I125: Invoking modinfo on "vsock".
  2016-05-28T18:21:09.607-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
  2016-05-28T18:21:09.618-07:00| vthread-4| I125: to be installed: vmnet status: 0
  2016-05-28T18:21:09.624-07:00| vthread-4| I125: Obtaining info using the running kernel.
  2016-05-28T18:21:09.624-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
  2016-05-28T18:21:09.624-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.624-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.624-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.632-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.632-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.701-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
  2016-05-28T18:21:09.702-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: Read 12201 symbol versions
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/2.6.32-642.el6.x86_64/build/include
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: Update kernel header path to /lib/modules/2.6.32-642.el6.x86_64/build/include
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.719-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.719-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.720-07:00| vthread-4| I125: Found compiler at "/usr/bin/gcc"
  2016-05-28T18:21:09.724-07:00| vthread-4| I125: Got gcc version "4.4.7".
  2016-05-28T18:21:09.724-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
  2016-05-28T18:21:09.724-07:00| vthread-4| I125: Using user supplied compiler "/usr/bin/gcc".
  2016-05-28T18:21:09.727-07:00| vthread-4| I125: Got gcc version "4.4.7".
  2016-05-28T18:21:09.727-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: No matching PBM set was found for kernel "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.737-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.737-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.738-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
  2016-05-28T18:21:09.738-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.738-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.738-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.746-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.746-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.746-07:00| vthread-4| I125: Using temp dir "/tmp".
  2016-05-28T18:21:09.747-07:00| vthread-4| I125: Obtaining info using the running kernel.
  2016-05-28T18:21:09.747-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
  2016-05-28T18:21:09.747-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.747-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.747-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.755-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.755-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.825-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
  2016-05-28T18:21:09.825-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
  2016-05-28T18:21:09.834-07:00| vthread-4| I125: Read 12201 symbol versions
  2016-05-28T18:21:09.834-07:00| vthread-4| I125: Invoking modinfo on "vmnet".
  2016-05-28T18:21:09.836-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
  2016-05-28T18:21:10.081-07:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/2.6.32-642.el6.x86_64/misc/vmnet.ko".
  2016-05-28T18:21:10.081-07:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".
  2016-05-28T18:21:10.087-07:00| vthread-4| I125: Successfully extracted the vmnet source.
  2016-05-28T18:21:10.087-07:00| vthread-4| I125: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-tH7bci/vmnet-only auto-build HEADER_DIR=/lib/modules/2.6.32-642.el6.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"
  2016-05-28T18:21:11.063-07:00| vthread-4| W115: Failed to build vmnet.  Failed to execute the build command.
  
  
  

  Hi, I faced the same problem, and now I have corrected this issue.

  He was vmnet.ko, at least for me.

  Here's how to solve,

  You can find the latest vmnet.ko of /lib/modules/~previous_kernel_version~/misc/vmnet.ko

  Copy vmnet.ko into your current/lib/modules/your_current_version/misc folder.

  And then run vmware, if you fail at the first, please run again.

  If so, you can run vmwre!

  I hope this will help you.

  Good day.

• VMware Tools update fails

  When I run a virtual machine, I get a popup telling me that a new version of VMware Tools (version 8.8.2) is available.  If I click to download, update the product for awhile then stops with an error box saying that there was a problem updating the component.

  As far as I can tell, I have VMware Tools installed 8.8.2.  How can I remove this popup?

  Running VMware on Linux CentOS 5.8 8.0.3.

  With the machine off, go in the Edition-> Preferences-> updates and and uncheck the two boxes «»  That should do it.

• 12.0.0 Workstation install fails on Ubuntu Linux 16.04 (4.4.0 - 28 generic) [service failing vmmon; updated vmware kernel module]

  Hi guys,.

  I'm really excited to go with VMware Workstation on a new install of Ubuntu (16.04).  Planning watch GNS3 VMs and vagabond for Docker VMs integration among other things.  Since the two vmware workstation and linux/ubuntu are mature, I really expected that I would have any problem with the installation.

  I was a bit dismayed when the 12 workstation installation failed on a new installation of 16.04.  It seems that the VMware Kernel Module Updater step and specifically the Virtual Machine Monitor is the problem.

  Can someone help with the steps required for a successful installation of 12 Workstation on Ubuntu 16.04 please?

  Details of my attempt and a quick fix to follow.

  Please help, thanks!

  Greg

  Hi there =)

  Just for brevity, the "Monitor" is in fact what we call the hypervisor itself. We call the LCD screens "poster".

  So it's probably an incompatibility of which is just to be around the GPU kernel module, but it could have been any kernel module.

  Thanks for sharing your success!

• VMware Workstation 11 crashes after installing VMware tools

  As the title suggests, VMware Workstation 11 crashes after installing VMware Tools with a guest Windows 7 x 64. I am running VMware on a host Windows 7 x 64. It happens every time I try to install the guest operating system. Attached to this post are all the newspapers that I could find that I thought would help solve the problem.

  
  

  Thank you

  Wila

  Hello again,

  Maybe the following post helps (where you installed Visual Studio)

  How to troubleshoot Workstation (vmui) - Access Violation Crash? How to troubleshoot Workstation Crash (vmui) - Access Violation? How to troubleshoot Workstation Crash (vmui) - Access Violation?

  --

  Wil

  As you may already know, VMware has just released a major update for 11 workstation (including VMware tools updated). Workstation now works almost perfectly. I don't have accidents since then. This means that I have was right in my post above. This is indeed nothing more than a BETA version of VMware buggy, lazy, masked as a "final". Wow, it looks like that a respectable company like this would not resort to such unethical practices. I mean that you would expect this kind of crap of a company like Electronic Arts, but VMware? Come on guys, you're better than this!

• Failed installation of VMware Workstation 9 on new install of win 7

  I looked at the discussion of installation has failed VMware Workstation 9, verified that I am administrator, cleaned folder and looked at the registry and I'm still having problems.  The name of the account used is not Admin/Admin or anything close.

  This is a new installation today of windows 7 with all updates applied.  Avast is my anti-virus software.  The behavior does not change with it running or disabled.

  I think that the problem to be that KLM/Sofware/VMware Inc. does not appear.  I checked that I can create keys.

  "In my installs I've seen: message" failure of the MSI MSI "and once"the MSI MSI failed. "  Authorization of VMware (VMAuthService) failed to start service.

  Here are the logs from my last install.

  Can someone provide me with more information about the problem and how to get this installed?

  Thank you

  Finally got this resolved after many setup logs sent to VMware.  I came across the registry problems and VMAuthdServices fail to start due to software AV.

  In short, following http://kb.vmware.com/kb/1031302 (KB1031302) is important as well as some comments from howellrj.  Here's what I did in detail and why during my various tests of installation:

  http://KB.VMware.com/kb/1031302

  1 I used the only account on the system, which did not have a name as owner, admin, administrator, which has administrator privileges

  2 wiped % TEMP % whenever I made an attempt to install

  3 MS KB 942288 not recommended for Win7 so I jumped

  4 no earlier version of VMware Workstation has been installed on the system, so I jumped

  5 ran http://support.microsoft.com/kb/2438651/en-us (MS KB2438651) whenever I made an attempt to install.  He has never found anything wrong

  6 was not running WinXP so I jumped

  7 has made run msconfig to disable all services and should follow https://support3.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=1334 (Avast KB1334) to disable Avast self protection mode.  Even with Avast protection auto mode disabled and all the disabled Avast shields were always running and prevent.  The only way to clear the checkpoint was to remove Avast completely.

  8 I ran sfc/scannow before each installation to be sure.  No problems have ever been found.

  So, here is what I did to get the software installed successfully:

  An item copied to my system

  1 AV Installer on my system

  2 use FixIt of MS KB 2438651

  Disconnected the network B

  C restart the system with network not connected

  D removed Avast

  E to restart the system with network not connected

  1 erase TEMP

  2 Ran FixIt utility of MS KB 2438651

  3 ran sfc/scannow

  F install VMware Workstation

  G restart the system

  H check VMware Workstation starts

  I install Avast

  J stop the system

  K connecting to the network

  L reboot the system with connected network

  M update Avast

  N reconfigure Avast

• Stop virtual machines with or without VMware tools installed

  So after a power failure major where I work has taken place where the batteries of the UPS only ran about 10 minutes and the emergency generator didn't kick in, I was put in charge of writing a script that starts to stop the virtual machines and servers in a given cluster. Now that I am relatively new to the environment here, so I don't know if all the virtual machines have the tools are installed. I want to cover all bases and the virtual machines that do not have the tools installed. My script done now is it initiates closing the comments on all the virtual machines and check every 10 seconds to 120 seconds for virtual machines go offline if after 120 seconds, there are even virtual machines online, it issues a shutdown command on all servers that have not stopped. Now, he'll catch all the virtual machines, but I don't want the machine have to wait 2 minutes before totality if it can be avoided (remember that this script will be executed when the data center goes to the power of the UPS for every watt account to keep critical systems online). the script throws an error when it cannot stop because no tool is installed, so I thought I could use a try/catch block to catch the error and send just a detroit of turning control of these VMs off. I tried to do, but without success.

  Is it possible that I can either catch the error, or a stop all virtual machines that do not have the tools installed?

  Attached is my code, maybe you can spot what can I do to stop the virtual machines without tools within the do / while loop when errors occur first.

  Add-PSSnapin VMware.VimAutomation.Core
  $server = $args [0]
  $cluster = $args [1]
  SE connect-VIServer-Server $server
  $counter = 0
  {}
  If (Get-Cluster-name $cluster | get - vm | where {$_.powerstate - eq 'receiving'}) {}
  If ($counter - eq 0) {}
  Get-Cluster-name $cluster | get - vm | where {$_.powerstate - eq "receptor"} | stop-VMGuest-confirm: $false
  }
  Write-Host "VMs are on waiting" (120-$counter)"seconds"
  $counter = $counter + 10
  Sleep 10
  }
  }
  While ($counter - 110)-or ((Get-VMHost |)) Get - VM | where {$_.powerstate - eq "receptor"}) .count)-No 0
  If ($counter = 120) {}
  Write-Host "certain virtual machines did not not stop properly, tension now.
  Get-Cluster-name $cluster | get - vm | where {$_.powerstate - eq "receptor"} | Stop-VM-confirm: $false
  }
  Write-Host "Putting servers into maintenance mode."
  Get-cluster-name $cluster | Get-vmhost | where {$_.state - eq 'connected'} | Game-VMHost-State "Maintenance".
  Sleep 10
  Write-Host "stop servers."
  Get-cluster-name $cluster | Get-vmhost | where {$_.state - eq 'Maintenance'} | Stop-VMHost-confirm: $false
  Disconnect-VIServer-confirm: $false

  Try something like this

  $vm = Get-VM
  $vm | where {$_.Guest.State -eq "Running"} | Shutdown-VMGuest -Confirm:$false $vm | where {$_.Guest.State -eq "NotRunning"} | Stop-VM -Confirm:$false
  

  Virtual machines running VMware tools will get a judgment of comments, while the virtual machines that do not have the VMware tools running, will get a poweroff.

• Can how fast I get a virtual network adapter on a computer server VMware vmware tools installed w/o?

  Hello

  I use a custom Linux VM on a Linux VMware Server host. That my Linux VM is on measurement, I don't want to install VMware tools on my virtual machine. My question is without VMware tools installed on my virtual machine, is it possible for my virtual machine to connect at gigabit speeds. My server host has a gigabit network connection.

  Thank you

  Varun

  without vmware-tools, make sure you that you use the E1000 nic in the comments and not the obsolete AMD

  Check with the vmx file and make sure that you have

  ethernet0.virtualDev = "e1000".

  ___________________________________

  VMX-settings- Workstation FAQ -[MOA-liveCD | http://sanbarrow.com/moa241.html]- VM-infirmary

• VMware Workstation 10.0.1 and Windows 7 VM crash on CentOS 6.5 host

  Just upgraded to 6.5 CentOS 64-bit (2.6.32 - 431.el6.x86_64). After the updates and reboot I launched VMware Workstation 10.0.1 as I normally and began my OpenVPN (Wheezy Debian) VM with all the problems. I then started my Windows 7 64-bit VM and the entire army what OS hangs and I have to reboot using the reset button.

  I was able to reproduce twice in a row. The Windows 7 VM seems to start fine and then when I type my credentials in and it starts to load the office which is when everything goes south and the host completely freezes.

  The Windows 7 VM has nothing too complicated installed in it. Some Epson software to start uTorrent and printer in network at startup. Steam does as well, but it is not auto-login or do anything really.

  I just did some testing of synthetic load and covered all 8 cores (much more than the usual load) up to 24 GB, 32 GB of RAM and 50% of CPU on the host computer and things remained stable. I thought that a second question could be RAM related because after a soft on boot the Windows 7 VM running I am to about 7 GB of RAM used on the host computer and from the WIndows 7 VM would put me over 8 GB, which resembled a number of nice where things might go wrong If it is RAM related.

  Log files:

  kdump(1): https://Paste.Fizi.ca/?f5c7c3e6945f8ce4#hPoN0VUJbPKA07hbDPWuE1D0e9FC7Ss8RNvF5Qv7yy0=

  vmware - 0.log: https://Paste.Fizi.ca/?05d42cd929bb5237#Zgbtlm7R+bZEHEOs5uSyA6Xin6FOOflWYWvNnHnxksM=

  Any ideas?

  Looks like I need to learn how to use the forum search tool.

  It is a dupe of VMware Workstation - 10.0.1 fails after the software update from RedHat-6.

• VMWare Workstation 12 and 18 of Linux Mint (Ubuntu 16.04) and vmware tools or open-vmware-tools

  I created a new virtual machine using VMWare Workstation 12.1.1 build-3770994 with a guest OS from Linux Mint 18 (which is built on top of Ubuntu 16.04). I have two monitors on my system, the two 2560 x 1440. I am unable to get this virtual machine Linux Mint 18 to cover all of my two monitors when I disable "Accelerate 3D graphics" in my vm settings, I get an error. I have another Linux Mint 17 VM running on the same VMWare Workstation 12 on the same host machine from Windows 10 and it is able to expand on my two monitors very well with "Accelerate 3D graphics" disabled, but he does not open-vmware-tools.

  I have read instructions telling me to install open-vm-Tools-Office in this guest operating system of Linux Mint 18. I did it. Then I restart the guest operating system. When starting, I can click on 'Enter full screen mode' in my menu of VMWare Workstation, and the guest OS has a monitor as expected. When I then click on "Cycle multiple monitors", I get the following error. "The virtual machine could not be changed to the selected screen layout. If you add a monitor to the host computer, you must turn off and turn on the virtual machine to use this monitor. »

  

  I can optimize my VM to automatic adjustment, only one of my two screens, but not both. I tried to uninstall and reinstall open-vm-tools, open-vm-tools-desktop and restart. I tried to use /vmware-tools-distrib/vmware-install.pl's original vmware tools and who does not work either.

  In my vmware.log, I get these two lines that occur when I get the above error.

  2016 07-12 T 15: 43:19.068 - 06:00 | MKS | I125: ToolsSetDisplayTopology: send rpcMsg = 1 DisplayTopology_Set, 0 0 2560 1440

  2016 07-12 T 15: 43:24.768 - 06:00 | MKS | I125: ToolsSetDisplayTopology: rpcMsg sending = DisplayTopology_Set 2, 0 0 2560 1440, 2560 0 2560 1440

  2016 07-12 T 15: 43:24.853 - 06:00 | vCPU-1 | I125: TOOLS of the call to DisplayTopology_Set failed.

  When I activate "Accelerate 3D graphics" with the configuration described above, I am able to use both of my monitors. Why is this the case?

  I think remember having to disable "Accelerate 3D graphics" in my Linux Mint 17 comments vm because it would crash randomly. I try to run this VM Linux Mint 18 with 3D acceleration and see if it crashes, but why is there a difference with spanning multiple monitors?

  Thank you.

  I didn't experience this problem for a few weeks. I don't have a definitive answer to my original problem.

  I installed Mate instead of cinnamon 3 to my MINT 18. Then, I created a new VM with Ubuntu Gnome 3 16.04 running as the OF. I did have problems with both approaches. I also tried using Firefox as my main browser instead of Chrome, as I read that Chrome can have problems of memory. It could be a combination of several of these changes that have allowed me to work without problems.

  Knowing what I know now, I think the move away from cinnamon 3 is what seems to have fixed my problems. I can certainly say that you use Firefox consumes less memory, as I can monitor the monitor system under Ubuntu. Chrome would eventually eat all my system memory, that I could see. The extent of the why? I'm not sure at this point.

• VMware Workstation 10.0.5 MSI failed

  I'm upgrading to VMware Workstation 10.0.5 since 10.0.4. The upgrade process has deleted 10.0.4, but when trying to install v10.0.5 I get an error:

  The MSI 'C:\Users\Ethan\AppData\Local\Temp\VMware_1422579427\vmwareworkstation_x64.msi' failed.
  

  I did the following with no fruit:

  1. Monitoring of VMware KB 1031302 and 1308 KB
  2. Copy the "C:\Users\Ethan\AppData\Local\Temp\VMware_*\" directory to another location of the command execution

     msiexec.exe /i vmwareworkstation_x64.msi EULAS_AGREED=1
     

     However, I got a different error:

     Failed to install the hcmon driver.
     
  3. Ran CCleaner registry cleaner
  4. Tried to (re) install VMware 10.0.4, however I still had the impossible "msi" error

  I found two newspapers, which are listed below. I have searched without finding a solution, any help would be greatly appreciated!

  Hi etnguyen03etnguyen03,.

  Here are 3 useful links when Workstation Setup error occurs on Windows.

  It will be useful.

  VMware KB: Cleaning after incomplete uninstall on a Windows host

  VMware KB: Troubleshooting a MSI error when a VMware product or installation of tools

  Need to reinstall Windows Installer in Windows 7 - Microsoft Community

  Given that you've tried the KB 1031302 and 1308 KB, the third link may be more useful.

  According to the answer in the third link:

  Please clean the related keys under: HKEY_LOCAL_MACHINE \Software\Microsoft\Windows\CurrentVersion\Installer\InProgress

  Check the following registry key and clean all entries in the key, you will find:

  HKEY_LOCAL_MACHINE \System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

  Thank you!

• System analysis tool update fails with error 0x800704c7

  After having the problem that Windows Update crashes on 'check updates', I followed the recommendations on http://windows.microsoft.com/en-ca/windows7/what-is-the-system-update-readiness-tool, installed the preparation tool system update, but unfortunately after several hours, it failed with error 0x800704c7. What can I do now?

  I'm on a Toshiba PC with Windows 7 professional service Pack 1 32-bit.

  If looking for updates to hang on a current installation,

  Be sure and go to uninstall a program and see which Microsoft Net framework you have installed.

  4.5.2 is more consistent to have installed,

  https://www.Microsoft.com/en-US/Download/details.aspx?ID=42642

  Switch your windows update setting to never check the updates temporarily

  Restart the machine

  You can try and install the latest client update manually let your update settings to never check for updates until you install it.

  https://support.Microsoft.com/en-us/KB/3138612

  Then you download this from your download folder run from there.

  https://TechNet.Microsoft.com/library/security/MS16-039?f=255&MSPPError=-2147217396

  Download the x 86 for 32-bit or x 64 for 64-bit

  Install it and restart when prompted too after he did a search of stand-alone for updates that should not

  take too long, it took all of 5 seconds, '' If '' windows update settings are turned on forever check

  updates before running from the downloads folder.

  Once it installs and restarts

  You can reset your updates affecting everything you had before default =...

  Then check the updates manually.

  I think that the solution came from Softpedia and Joel_CS posted on this thread,

  http://News.Softpedia.com/news/Windows-Update-hanging-when-downloading-April-12-patches-502886.shtml

  You must scroll down for Joel SC post threads, it is the last answer on this page,

  http://answers.Microsoft.com/en-us/Windows/Forum/Windows_7-update/Windows-Update-hangs/dbd539c3-bfc6-42DF-a6ff-0e55ef7938eb?page=6

• Core upgraded to 4.0 on Centos 7 VMWare Workstation 11 won't build the virtual network device

  As shown in the topic, I have manually compiled kernel 4.0 for my installation of CentOS 7. After the installation of the kernel (in rpm mode, followed the instructions here: How to compile a Kernel - The Way CentOS ) installed all 3 rpm, kernel, kernel-headers and kernel-devel and then tried to start my installation of workstation with it leads to having to re - build the components (as usual)

  It does not, when it came to the compilation of the network management module. See attached log file that it generated.

  I also tried to uninstall, downloaded VMware-Workstation-Full - 11.1.0 - 2496824.x86_64.bundle and re-installed with the same result.

  Any help would be appreciated!

  aaand..., I fixed my only problem!

  Credit:

  https://wiki.archlinux.org/index.php/VMware

  just applied the 3.19 patch and He-voila!

• Installation of VMWare Workstation 11.1.0 on Win 8.1 is THAT MSI will fail with the error "could not write value vmware - tray.exe for \software\microsoft\windows'currentversion\run-cles.

  Hi all

  The MSI failed with the error message as "could not write value vmware - tray.exe in \SOFTWARE\Microsoft\Windows'CurrentVersion\Run key.  Make sure you have fufficient access to that key, or contact your support staff' while trying to install vmware workstation 11.1.0 in windows 8.1.
  I tried to call the installer with run as administrator but it does not help, please suggest me overcome this error.

  Hi Vincentand welcome to the VMware communities!

  This error indicates that you have some security software (antivirus or antimalware software) that protects the part of the registry.  Can you try to temporarily disable all security software on your host computer and see if the installation can move forward?

  See you soon,.

  --

  Darius

• Any Installation of Vmware Workstation failed in my machine, why? See the details

  

  Hey guys, I'm trying to install vmware workstation 11,10 even though 9, but unfortunately it shows this kind of error every time.

  then I try to install from appdata/local/temp, but it shows the error of capture4... I tried many things to fix this... but I failed...

  So guys help me please install... sorely lacking...

  is my laptop config: core i5 - 3230M, ram - 4 GB os-win7 64 bit sp1...

  need help please...

  Welcome to the community,

  the problem is probably caused by the apostrophe in the name of the folder of the user. Try at each logon with a different user (temporary) account, or change the temp/tmp environment variable to point to a different directory (existing), for example, "C:\TEMP".

  André