VMware Workstation 9.0 restarts my PC trying to turn on a virtual machine

Similar Questions

• the request to turn off this virtual machine failed because the corresponding vmware tools script didn't run successfully

  using vmware fusion 2.0.5

  the request to turn off this virtual machine failed because the corresponding vmware tools script didn't run successfully

  now vmware cant off power

  is vmware tools script to run when windows is running

  If I power off (mac - force quit) now... what happens

  VMware Fusion 2.x...

  VMware Fusion (menu bar) > help > VMware Fusion help > running VMware Fusion and Virtual Machines > Shutting Down a virtual machine operating system

  VMware Fusion (menu bar) > help > VMware Fusion help > running VMware Fusion and Virtual Machines > Options for VMware Fusion food orders

  VMware Fusion (menu bar) > help > VMware Fusion help > running VMware Fusion and Virtual Machines > orders of switching power supply from the default Options

  ==========

  Note: It's like pulling the plug of the wall on a physical computer. Whatever this is not saved will be lost and there is always the possibility of corrupting the file system where preforming a hard stop! (Even if you have no choice but to do.)

  VMware Fusion menu bar > VM > press the option key and select Power Off

  By pressing the keys alt/option "Shutdown called" changes to "Power Off".

  Note: It also changes orders of "Suspend comments" and "Restart Guest' too.

  Or if this does not work then...

  On the library Virtual Machine ctrl - click on the target of the Virtual Machine and select Show in Finder and delete the .vmss file, the ctrl + click the target package of Virtual Machine, and then after the merger closed. Note: All that was not justified for the suspended state will be lost by deleting the .vmss file. Note: However: you have no other choice if the Virtual Machine does not suspend/resume/stop/start correctly.

• VMWare Workstation fail to restart after suspend

  I'm using VMWare Workstation 7.1.1 build 282343 on a laptop Windows 7 Ultimate x 64 (8 GB). I run my VMS machines from a disk external eSata. My VMs are all Windows Server 2008 x 64. When I finished work I suspend the virtual machine, stop VMWare Workstation, then disconnect the eSata drive. It is, whenever I just restarted the VM, I get a message that is not possible to restore and I give myself the opportunity to "get rid" or retry - retry fails, so I have to throw. It's embarrassing because it then takes a boot for a long time the virtual machine from scratch.

  Any ideas how to solve this problem?

  disable USB-support for this virtual machine and start again

• Cannot turn on the virtual machine in VMware workstation

  Hello

  I have windows 2008 stocked VM of windows 4.1.Inside ESX VM 2008 I installed VMware workstation and created the virtual machine in vmware workstation. When I have tride to power on the VM iam getting error below. Please help me.

  "Running vmware workstation in a virutal machine requires external thr virtual machine is configured to run the vmware esx host operation system.you may not power on a vierutal machine until the external virtual machine is reconfigured.

  Thank you

  Victor

  This is the VM vmx nested - you must add this line to the external virtual machine - one who runs in ESXi

• WinRunner license with VMware Workstation

  Evaluate us VMware Workstation 10.0 and we try to install Winrunner on a virtual machine but the Winrunner trying to get out to the network on the virtual machine to find the license competition, every time, we have created (OS Win 7), installation is suspended. The error indicates the installation Winrunner is unable to find the license on the network.

  Verified that the network is in place and works very well. Check that the license exists on the network (installed on another computer to test using a ghost image). Anyone got any ideas on why installing Winrunner can not find the license?

  Concerning

  Your guest VM is configured to use NAT or Bridged network mode?  Not sure if it would be serious, but it is possible - if it's NAT - the license service is unable to return to the virtual machine.

• What permissions are required for access to VMware Workstation?

  I need to provide access to a few virtual machines in our environment vSphere for a user through VMware Workstation 9.0.2 but questions.

  There are 3 virtual machines in a folder under models and virtual computers that this user needs access base (start, stop, console). I first tried assigning the role of user (sample) of the virtual machine to the user on the folder that contains these VMs (with spread), but trying to access one of them workstation as long as this user, I get the error was refused permission to perform this operation. I even tried to assign the role of administrator for this user on this issue and received the same error.

  Then, I assigned the user (sample) of the virtual machine and then later the role of the administrator directly to the virtual machines, but when you try to connect through my computer I get this error with or the other role (I have attached the log file, it refers):

  

  After clicking on OK, workstation breaks down, and then I get this error:

  

  The only way I could successfully get this user access is by adding the user to the local Administrators group vCenter Server, but after doing this, the user has full access to all virtual machines. I should also mention that Im able to access the virtual machine with the basic functions assigned via vSphere client to web without problem with permissions above affected as this user.

  Does anyone know what is required to provide access by workstation I'm looking for?

  Thank you!

  Figured it out!

  First, for each virtual machine that you want to grant access, to add the user/group with the assigned role, you want to give them. An additional step required for access to the workstation is, for each host you granted access to the virtual machines are on, you must also add the user/group and assign the read-only role, making sure to uncheck propagate to child objects.

  So it's similar to the thread above, but avoids having to explicitly revoke access to each another VM on the host. So now, when I log in as a user with that I was testing, I can connect to vCenter via my computer, only to see the VMs Ive applied custom roles to and, especially, can connect to them without problem!

  Also, it seems that even if work stations invite you to assign read-only permissions to the host is not actually do something.

  Thanks a bunch for all the help everyone... especially ShadyMalatawey. If I would not have seen this prompt in my computer to apply the permission he would have had much more time to understand.

• 64-bit Linux does not work on VMware Workstation 8

  I'm running an installation entirely under license of VMware Workstation 8.0.2. This forum works on a Lenovo Thinkpad T420 with 8 GB of RAM and a 160 GB SSD, so what matters. The T420 has an Intel Core i7 2.8 GHz processor. It's running Windows 7 Enterprise SP1 for 64-bit.

  When I try to create a virtual machine on this machine to run RHEL 5 in 64-bit mode, I get the following error when trying to turn on the virtual machine:

  

  When I click on the link on VMware.com, I get a utility to check the CPU on my machine. When I run this utility, it shows that my CPU is fine for the performance of the VMS 64-bit. Go figure.

  Also, I rebooted and explored the BIOS. Didn't see anything obvious here to turn on to enable this.

  Bottom line: I need to create a VM Linux 64-bit on this puppy, and he won't. Any ideas anyone?

  Welcome to the community,

  Please check the settings of the BIOS again. I'm not familiar with Lenovo systems, but "virtualization technology (VT - x)" as well as "No. Execute Disable" settings are generally in the part of the security of the configuration of the BIOS. Two of them must be enabled. After you change the any of these settings, you will need to equip completely from the cycle of the system (a simple reboot may not be enough).

  If you can't find the settings, please report (attach) the latest vmware.log file of the virtual machine file to see what VMware Workstation detects.

  André

• Fatal error of VMware Workstation

  Hello

  I have serious problems with VMware Workstation (version 9.02) and unique virtual machine to Windows 8. VMware Workstation is installed x 64 host Windows 8. This unique virtual machine crashes randomly with the following error message:

  

  I have other virtual machines also but I have no problems with them. First of all, I thought it was a physical disk error and I moved this virtual machine to another drive, but it did not help. I reinstalled VMware Tools and even created a new virtual machine and cloned this issue with Acronis Backup & Restore machine for this. This due to the machine crashes with the same error, but every time you start so things went even worse.

  Any ideas what to do with it?

  I attach a log file.

  Post edited by: Demuz

  I updated to VMware Workstation 10 and reinstalled the whole problematic virtual machine from scratch, but it still crashed at random several times a day with the same error.

  But now things look well so far.

  Yesterday, I changed a setting. I unchecked "Accelerate 3D Graphics" settings of the virtual machine (under the display settings). After that, the virtual machine crashed 0 times and I've been using a whole day! I have Nvidia display with the latest adapter drivers Win 8.1 x 64 installed on the host machine. I think drivers Nvidia has something to do with this virtual machine crashing, maybe...

  I started to suspect the display driver Nvidia after seeing this nvd3dumpx.dll appears more than once in the log file (this is VMware Workstation logfile ater the crash):

  2013-10 - 07T 18: 14:03.625 + 03:00 | vthread-14 | I120: backtrace [00] framework 0x1004ee48 IP 0x7ff8c64db9af params 0 x 1 0 0 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x006da9af]

  2013-10 - 07T 18: 14:03.626 + 03:00 | vthread-14 | I120: backtrace [01] framework 0x1004eea0 IP 0x7ff8c655ee5c params 0xf2c680 0 0x116d5ee0 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0075de5c]

  2013-10 - 07T 18: 14:03.627 + 03:00 | vthread-14 | I120: backtrace [02] frame IP 0x7ff8c649c5f8 params 0 x 1 0x1004f6c0 0 0x7ff800000000 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0069b5f8]

  2013-10 - 07T 18: 14:03.627 + 03:00 | vthread-14 | I120: backtrace [03] framework 0x1004f6f0 IP 0x7ff8c649860d params 0xf2f280 0 0 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0069760d]

  2013-10 - 07T 18: 14:03.628 + 03:00 | vthread-14 | I120: backtrace [04] framework 0x1004f720 IP 0x7ff8c64b7f43 params 0xf2f280 0 0 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x006b6f43]

  2013-10 - 07T 18: 14:03.628 + 03:00 | vthread-14 | I120: backtrace [05] framework 0x1004f750 IP 0x7ff8c673c2cf params 0x7ff800000000 0 0 0 QueryOglResource + 0x1d5c2f [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0093b2cf]

  2013-10 - 07T 18: 14:03.628 + 03:00 | vthread-14 | I120: backtrace [06] frame IP 0x7ff8c673c51a params 0 0x1004f780 0 0 0 QueryOglResource + 0x1d5e7a [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0093b51a]

  2013-10 - 07T 18: 14:03.630 + 03:00 | vthread-14 | I120: backtrace [07] frame IP 0x7ff8df941611 params 0 0x1004f788 0 0 0 BaseThreadInitThunk + 0x000d [C:\Windows\system32\KERNEL32. [DLL base 0x7ff8df940000 0x0001: 0 x 00000611]

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: backtrace [08] frame IP 0x7ff8e08664ad params 0 0x1004f7b8 0 0 0 RtlUserThreadStart + 0x001d [C:\Windows\SYSTEM32\ntdll.dll base 0x7ff8e07f0000 0x0001: 0x000754ad]

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: Msg_Post: error

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: fatal error [msg.log.error.unrecoverable] VMware Workstation: (vthread-14)

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120 + Exception 0xc0000005 (access violation) occurred.

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: [msg.panic.haveLog], a log file is available in "F:\VMware\Virtual Machines\vmware.log".

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: [msg.panic.requestSupport.withoutLog] you can ask support.

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: [msg.panic.requestSupport.vmSupport.windowsOrLinux]

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120 + to collect data to be submitted to VMware support, choose "Collect load data" in the Help menu.

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120 + you can also run the script 'vm-support' in the folder my computer directly.

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: [msg.panic.response] we will respond on the basis of your entitlement to support.

• Impossible to remove or reinstall VMware Workstation 6.5

  Hello!

  I bought an AcerM7220 with OS Vista Home Premium 64-bit i7 last week

  I install VMware Workstation 6.5

  and I install Windows server 2003 and virtual machines

  It worked perfectly

  the next when I reopen it system there an error and automatically fix the system of system restore

  but records VMware Workstation 6.5 was on the system a shortcut on the desktop

  can't open an error come saying "Unable to enable FIPS mode, check your installation"

  And when try to uninstall and reinstall again an error that says

  "Setup has detected that VMware Workstation is already installed on this machine." Please uninstall this product via the control panel and try again.

  but the Control Panel programs and features, I can't see Uninstalling VMware Workstation 6.5.

  Can some Please Help me! One

  I had the same problem, I used CCleaner and this error message appeared and I was able to reinstall.

• Is there a binary 64 bit VMware Workstation v6.5.1?

  I know that VMware v6.5.1 supports 64-bit operating systems, but VMware itself has a 64-bit binary or 32-bit only?

  Also, it works very well under Vista x 64?

  Yes, VMware Workstation 6.5.1 runs great on Vista x 64 SP1.

  On Vista x 64 host, VMware Workstation GUI application is 32-bit, but if you start a virtual machine, you will notice that the process vmware - vmx.exe is 64-bit.

• 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.

• 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

• VMWare Workstation 8 and 9

  I can install Workstation 8 and 9 on the same PC (Windows XP SP3 home edition).

  Reason:

  I have a VM that work perfectly on Workstation 8 and I buy upgrade and update Workstation 8 to 9 of the workstation to create a new Virtual Machine with Windows 8.

  This new machine works fine, but the old machine did not start with the following message:

  "This virtual machine policies are too old to be run by this version of VMware Workstation. Contact your system administrator. »

  I use all of the solutions found on the community, but all have failed and is important for me to use this old virtual machine.

  Thank you.

  Hello

  You can install only one version of workstation on your computer.

  Have you tried to create a new virtual machine in the workstation 9 and configure it to use the old existing VMDK from the virtual machine to see if it boots?

  Concerning

• How to run VMWare workstation as a service?

  Hello

  I installed VMware Workstation 7 (latest version) and created a virtual machine. The problem is that once I have disconnected the host, the virtual machine stops!

  Is there a setting to prevent this? It should be able to run VMWare Workstation as a service.

  Thank you

  M.R.

  Running a process that wasn't supposed to be run as a service was taken over ad nauseam on Internet Google is your friend.

  Although it is possible to start the process as a service, however unless you use a program that can well handle the cessation of treatment and or restart the messages from the host and transmit them to the virtual machine, then it does not really work as a true service since it will not be the appropriate communication channels to activate the Virtual Machine to make a correct and controlled stop when the host is restarted or shutdown and that can damage the Virtual Machine.  If you plan to run a VM as a Service under VMware Workstation then I offer so you have good backups (which we should have anyway) and make sure you have access to working distance before running it as a service you can do a controlled stop on the VM before the reboot or shutdown of the host if you have not a utility appropriate to deal with it properly and safely.

  Another option is to use VMware Server, but keep in mind it seems to be the end of life and not maintained more.

• Determine the version number and compilation of VMwareTools for VMware Workstation 7.0.1 build 227600

  I installed VMware Workstation 7.0.1 build 227600 on a Windows 7 64-bit machine.  Update the VMware Tools using the compiler, one of the instructions is:

  CP /mnt/cdrom/VMwareTools-x.x.x-xxxx.tar.gz /tmp/

  How can I determine the values of x in this case? When I tried the following command:

  CP /mnt/cdrom/VMwareTools-7.0.1-227600.tar.gz /tmp/

  I received the following error message:

  CP: cannot start ' / mnt/cdrom/VMwareTools-7.0.1-227600.tar.gz':

  No such file or directory

  The GuestOS I tried to run is:

  Release of centOS 5.2 (Final)

  I always use AutoComplete with tab to get the name of the file.

  Type:

  CP/mnt/cdrom/VM, and then press your tab key. He must complete the rest automatically.

  Then complete the order with the part of tmp folder location.

  Rick Blythe

  Social media specialist

  VMware Inc.

  http://Twitter.com/vmwarecares

  http://Twitter.com/vmwarekb