VMware Communities
randomuser2
Contributor
Contributor

Can't install VMWare Workstation 17.5 Player

I downloaded the installer for VMWare Workstation 17.5.0 Player (VMware-player-full-17.5.0-22583795.exe), and verified the MD5 checksum, which matched. When I run it as administrator, I get the following error after pressing the first "Next" button:

 

"The Windows Installer service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. Contact your support personnel for assistance."

 

I have never had a problem with the Windows Installer before and am still able to install other programs fine. I have attempted to restart the Windows Installer service through services.msc, as well as restarting my PC. I checked for Windows updates and upgraded to the latest version (Windows 11 Pro Version 10.0.22621 Build 22621). I am not running Windows in safe mode and I still get the error every time and am unsure what to do next.

I have also attached the vmmsi.log

0 Kudos
18 Replies
pcgeek2009
Hot Shot
Hot Shot

Try right-clicking on the installer and selection "Run As Administrator" I have seen this work on installing programs before that error otherwise. It is like UAC causes some kind of issue. 

0 Kudos
randomuser2
Contributor
Contributor

As I stated in my post, I have tried running it as administrator, but still getting the same error.

0 Kudos
pcgeek2009
Hot Shot
Hot Shot

My apologies. I did not catch that when I read it. 

0 Kudos
AbbedSedkaoui
Enthusiast
Enthusiast

Hi,

Take a look at the install log located in:

%LocalAppData%\Temp\vmmsi.log

You can use a tool like cmtrace to watch the log live after running the installer as admin.

Be aware that pending reboot (from previous install or uninstall) prevent the reuse of windows installer.

https://github.com/MicrosoftDocs/win32/blob/docs/desktop-src/Msi/msisystemrebootpending.md

 

0 Kudos
randomuser2
Contributor
Contributor

I had a look through the log, but I'm not really sure what I'm looking for. If anyone could have a look at this, it would be appreciated.

0 Kudos
AbbedSedkaoui
Enthusiast
Enthusiast

The log give the error code with text message:

Error 1719. The Windows Installer Service vould not be accessed.png

"Error 1719. The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. Contact your support personnel for assistance."

this lead to VMware KB https://kb.vmware.com/s/article/1031032

to resolve the issue by re-registering the service.

Also if a previous install failed to uninstall, there a VMware KB https://kb.vmware.com/s/article/1308

to "Cleaning up after an incomplete uninstallation on a Windows host (1308)" with a section "Manually cleaning a Windows system".

0 Kudos
randomuser2
Contributor
Contributor

I had already tried re-registering msiexec.exe and also found no WOW64 key in HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\Services\msiserver. I have also never installed a VMWare product before.

0 Kudos
AbbedSedkaoui
Enthusiast
Enthusiast

There used to be an effective tool to clean Windows Installer failed install https://en.wikipedia.org/wiki/Windows_Installer_CleanUp_Utility

It is now replaced by this troubleshooter https://support.microsoft.com/en-us/help/17588/fix-problems-that-block-programs-from-being-installed...

 

0 Kudos
randomuser2
Contributor
Contributor

It just gives me "Troubleshooting couldn't identify the problem" and the installation is still giving the same error

0 Kudos
AbbedSedkaoui
Enthusiast
Enthusiast

It's worth checking if there are not pending rename operations after a reboot following these steps:

Check the following registry key and clean any entries in the key that you find:

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

https://answers.microsoft.com/en-us/windows/forum/all/error-1719-the-windows-installer-service-could...

 

Before launching cmd as admin and then the troubleshooter or the installer,

verify that Windows Installer service is stopped

and that msiexec.exe is not running process in taskmgr.

From the troubleshooter select uninstall and select "Not Listed" then enter the product code {99A6B581-0FA3-4E1B-BD84-E796FE26E41D} which is at the begining of the vmmsi.log.

0 Kudos
randomuser2
Contributor
Contributor

HKEY_LOCAL_MACHINE \System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations did not exist, so I assume that's fine.

As for the troubleshooter, assuming you're still referring to this one (https://support.microsoft.com/en-us/help/17588/fix-problems-that-block-programs-from-being-installed... there is no option for uninstall, instead only a button for next, followed by "Troubleshooting couldn't identify the problem".

I also tried installing some previous versions of VMWare Workstation (17.0.2 and 16.2.5) but still the same error on both.

0 Kudos
AbbedSedkaoui
Enthusiast
Enthusiast

In regedit.exe navigate to the Key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager ,

on the right panel the Value name is PendingFileRenameOperations,

and inside it the Data to be deleted.

For the troubleshooter yes once you selected 'Not Listed" you have to click next to proceed.

0 Kudos
randomuser2
Contributor
Contributor

The registry key does not exist 

Screenshot 2023-12-25 123909.png

The troubleshooter does not have a 'Not Listed' option. Once I open it all I see is this screen:

Screenshot 2023-12-25 124111.png

After clicking next I get this:

Screenshot 2023-12-25 124226.png

0 Kudos
AbbedSedkaoui
Enthusiast
Enthusiast

For the pending filename operations registry there might be none at the moment.

For the troubleshooter, i don't have the bottom warning and the direct links is https://download.microsoft.com/download/7/E/9/7E9188C0-2511-4B01-8B4E-0A641EC2F600/MicrosoftProgram_...

0 Kudos
randomuser2
Contributor
Contributor

Following the link you posted is the exact same program I have downloaded, with no different behavior.

0 Kudos
AbbedSedkaoui
Enthusiast
Enthusiast

Ok there deprecation notice with the alerting 'In-Product Message' at the bottom of this page for the troubleshooters,
what i don't get is that i have the build 22h2 as you and there an important note saying that it would work without warning on 22h2 and older.
https://support.microsoft.com/en-us/windows/deprecation-of-microsoft-support-diagnostic-tool-msdt-an...

After i click next a detection screen appear and i 'm presented with this screen:

after problem detection screen - troubleshooter.png

0 Kudos
randomuser2
Contributor
Contributor

Are you also running Windows 11 Build 22621.2861?

0 Kudos
AbbedSedkaoui
Enthusiast
Enthusiast

Earlier than that: 22621.1848

0 Kudos