I am currently facing an issue related to the MSI installer for Google Chrome. The application is not updating, uninstalling, or reinstalling due to a missing uninstaller source file: C:\WINDOWS\Installer\XXXXXXXX.MSI To resolve this, I have identified two potential methods:
Using Microsoft Program Install and Uninstall Troubleshooter (MicrosoftProgram_Install_and_Uninstall.meta.diagcab
)
Manually deleting specific registry entries:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products
→ Google Chrome folder
`HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall` → Google Chrome folder
`HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products` → Google Chrome folder
However, both methods present challenges:
- The first method is not feasible for over 700 endpoint users.
The second method is restricted by the InfoSec team, which does not permit registry deletion or the use of third-party tools.
Could you please suggest any alternative solutions or best practices to resolve this issue at scale?I am currently facing an issue related to the MSI installer for Google Chrome. The application is not updating, uninstalling, or reinstalling due to a missing uninstaller source file:
C:\WINDOWS\Installer\XXXXXXXX.MSI
To resolve this, I have identified two potential methods:
Using Microsoft Program Install and Uninstall Troubleshooter (MicrosoftProgram_Install_and_Uninstall.meta.diagcab
)
Manually deleting specific registry entries:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products
→ Google Chrome folder
`HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall` → Google Chrome folder
`HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products` → Google Chrome folder
However, both methods present challenges:
The first method is not feasible for over 700 endpoint users.
The second method is restricted by the InfoSec team, which does not permit registry deletion or the use of third-party tools.
Could you please suggest any alternative solutions or best practices to resolve this issue at scale?