Glam Prestige Journal

Bright entertainment trends with youth appeal.

Running VMware WS 10 on Windows 7. EASY-installed Ubuntu desktop 12.04 64-bit. Windows Task Manager seems to say VMware is running 32 bit, but I have a FreeBSD 64-bit guest running, and a Windows 8 64-bit guest running as well. Any pointers or clues will be most appreciated.

2

4 Answers

This issue can occur when the VMware Authorization service is not running or when the service does not have administrator rights.

To resolve this issue, start the service and ensure that it does have administrator rights.

To start the VMware Authorization service or to check whether it's running: Login to the Windows operating system as the Administrator. Click Start and then type Run. If you are unable to find the Run option, refer to Microsoft article What happened to the Run command? Type services.msc and click OK. Scroll down the list and locate that the VMware Authorization service. Click Start the service, unless the service is already is showing a status of Started.

3

In case the VMWare Auth service is running and you are still getting this error, follow the given steps,

  1. Close VMWare
  2. Stop any VMWare processes (from Task Manager)
  3. Delete the .vmem file
  4. Re-start the VM and it would work fine

Hope it helps

2

You may discover that the option to start the Vmware Authorisation Service has been disabled and the option to start it has been greyed out.

In that case, right click the service, followed by Properties. Change the Startup Type to your desired status (eg. Automatic (Delayed Start)), then click Apply, followed by Start.

You can also just run Workstation as an Administrator if you want.

Right-click VMware Workstation in the Start Menu Icon or on the Desktop Shortcut Icon, followed by "Run as administrator".

4

In my case I am running VMWare workstation V.10 on Windows server 2008 R2. I had to remove my server from domain and VMware started giving "Internal Error" while starting guest machines. I have tried couple of work-a-rounds.

finally Re-installing VMWare with repair option resolved the issue