Every time I run Vmware, I get this error: Error While powering on: The VMware Authorization Service is not running

Question

Error While powering on: The VMware Authorization Service is not running.

To fix this error, I go to:

"Start / Control Panel / Administrative Tools / Services, clicked on VMware Authorization Service in the list & click the Start link on the left."

But I have to do this every time I want to use the Vitual Machine.

Does anyone know a permanent solution?

score 47 · Accepted Answer · answered Jan 28 '13 at 10:06

47

go to Start > Control Panel > Administrative Tools > Services double click on VMware Authorization Service a window will open.

It will look something like this

enter image description here

In that window select Automatic from the drop-down menu near to Startup Type:. Then click on the OK button to save the change.

answered Jan 28 '13 at 10:06

Shineeth Hamza

@user177931 I think the right stack for these kind of questions are http://superuser.com/ . Next time if u have any OS related question please ask in http://superuser.com/ – Shineeth Hamza Jan 28 '13 at 10:12
1

Hi, that did'nt work i still have to go into services and restart it :( – AndroidAL Jan 31 '13 at 09:33
right below there is link `Help me to configure service start option`. click on the link and follow the documentation. If it doesn't help you, let me know – Shineeth Hamza Jan 31 '13 at 09:49
Hi again, that does'nt work for me. – AndroidAL Feb 13 '13 at 16:45
After Changing Type to Manual . I had to "Start" the service to get rid of the error – DB Prasad Feb 08 '14 at 21:19
@DeenbandhuPrasad You should set `Startup Type` to `Automatic` Not `Manual`. – Shineeth Hamza Feb 10 '14 at 03:54
While my error message did not provided any clue, [VMware Player – “Error while powering on: Internal error"], starting VMWARE Authorization Service quickly solved my issue. Thanks to you and Google (for pointing out this page as a good solution) – Julio Nobre Aug 03 '15 at 10:53

score 27 · Answer 2 · answered Apr 28 '13 at 16:58

27

I resolved this by starting VMware Workstation as Administrator.

answered Apr 28 '13 at 16:58

2 Answers2