VMware Communities
munrobasher
Enthusiast
Enthusiast
Jump to solution

Problems upgrading to v12.0.1

I'm getting multiple errors attempting to upgrade from v12.0.0 to v12.0.1 on Windows 8 x64. The first error during the upgrade is this:It sshot-9.png

It then rolls back. When I try to install the upgrade again, I get a different error message:

sshot-11.png

I'm just going to try rebooting and trying again.

Reply
0 Kudos
1 Solution

Accepted Solutions
Susie201110141
VMware Employee
VMware Employee
Jump to solution

Thanks for asking!

This issue has a workaround and could you check following method?

VMware Workstation 12 Pro Release NotesRe: Problems upgrading to v12.0.1

A Workstation 12 Pro installation might fail with an error message about privileges
  During installation, Workstation 12 Pro might issue the following error message as the installation fails:

Service 'VMware Authorization Service' (VMAuthdService) failed to start. Verify that you have sufficient privileges to start system services.

Workaround:

  1. Cancel the Workstation 12 Pro installation.
  2. Delete all files under the %TEMP% directory.
  3. Reboot the host.
  4. Install Workstation 12 Pro again.

View solution in original post

Reply
0 Kudos
9 Replies
munrobasher
Enthusiast
Enthusiast
Jump to solution

Okay, it installed after reboot but now getting error with shared VMs:

sshot-12.png

VMwareHostd (VMware Workstation Server) service isn't running which might explain this error. It's start-up mode is set to manual but I'm unable to manually restart it.

Another reboot is on the way... never had problems like this upgrading VMware Workstation...

Reply
0 Kudos
munrobasher
Enthusiast
Enthusiast
Jump to solution

Nope, now it a completely unstable set-up and unable to start shared VMs as it can't connect to the VMware workstation server and trying to manually start it ends up with errors like this in the event log. Fortunately, I image my Dev PC frequently using Macrium Reflect so can quickly restore to it's original state.

Log Name:      System

Source:        Service Control Manager

Date:          02/11/2015 18:26:15

Event ID:      7032

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      --DELETED--

Description:

The Service Control Manager tried to take a corrective action (Run the configured recovery program) after the unexpected termination of the VMware Workstation Server service, but this action failed with the following error:

3 is not a valid Win32 application.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />

    <EventID Qualifiers="49152">7032</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8080000000000000</Keywords>

    <TimeCreated SystemTime="2015-11-02T18:26:15.616223000Z" />

    <EventRecordID>5713</EventRecordID>

    <Correlation />

    <Execution ProcessID="748" ThreadID="3844" />

    <Channel>System</Channel>

    <Computer>Gandalf.middle-earth.co.uk</Computer>

    <Security />

  </System>

  <EventData>

    <Data Name="param1">3</Data>

    <Data Name="param2">Run the configured recovery program</Data>

    <Data Name="param3">VMware Workstation Server</Data>

    <Data Name="param4">%%193</Data>

  </EventData>

</Event>

Reply
0 Kudos
munrobasher
Enthusiast
Enthusiast
Jump to solution

Has anyone else here tried installing v12.0.1?? I've rolled back to earlier image, uninstalled VMware workstation v12.0.0 (completely inc. settings and license) and then installed v12.0.1. Same problem with VMware authorization service failing to start. I didn't reboot in-between uninstalling but will try that now.

Cheers, Rob.

Reply
0 Kudos
munrobasher
Enthusiast
Enthusiast
Jump to solution

Have given up on v12.0.1 and gone back to v12.0.0 even after doing the following, the workstation server service still fails to run so shared VMs are broken:

  1. Uninstall v12.0.0
  2. Check not VMware services left (there weren't)
  3. Reboot - without this step, authorization service fails to install at all
  4. Install v12.0.1 - installs cleanly
  5. Reboot - just in case

So despite a clean install, the VMware Workstation Server service (VMwareHostd) is a) set to manual and b) can't be manually started.

NOTE: in v12.0.0, the service is set to automatic.

So will skip this version and wait for v12.0.2


Reply
0 Kudos
Susie201110141
VMware Employee
VMware Employee
Jump to solution

Thanks for asking!

This issue has a workaround and could you check following method?

VMware Workstation 12 Pro Release NotesRe: Problems upgrading to v12.0.1

A Workstation 12 Pro installation might fail with an error message about privileges
  During installation, Workstation 12 Pro might issue the following error message as the installation fails:

Service 'VMware Authorization Service' (VMAuthdService) failed to start. Verify that you have sufficient privileges to start system services.

Workaround:

  1. Cancel the Workstation 12 Pro installation.
  2. Delete all files under the %TEMP% directory.
  3. Reboot the host.
  4. Install Workstation 12 Pro again.
Reply
0 Kudos
jbudreau
VMware Employee
VMware Employee
Jump to solution

This "VMware Authorization" error has been an elusive one for many releases. It's been really difficult to find a system state that reproduces the error. Usually a reboot allows the next run of the installer to work.

It would be a great help if you could run the 12.0.1 installer, and when it crashes attach all the %TEMP%\vm*.log files to this thread.

Thanks!

Reply
0 Kudos
munrobasher
Enthusiast
Enthusiast
Jump to solution

I'll try deleting the contents of temp folder over the next few days.

Cheers, Rob.

Reply
0 Kudos
munrobasher
Enthusiast
Enthusiast
Jump to solution

Bizarrely, I tried this again today and it installed without a hiccup...

Cheers, Rob.

Reply
0 Kudos
munrobasher
Enthusiast
Enthusiast
Jump to solution

I'm marking the answer above as correct so this thread can be closed off except I didn't have to use the workaround suggested. When I came back to this issue, v12.0.1 installed flawlessly and the VMware server is running fine. Auto-starting VMs are also working fine.

Haven't a clue therefore what caused the original problem as it does seem to be transient.

Cheers, Rob.

Reply
0 Kudos