1

Hi it's been few days having different Google Video Support Pluggin Installer tasks running

It happens the same this folk described here: v78 of Chrome, Win 10, Every few hours a new instance of the video plugin installer exe kicks off and runs in parallel with the other(s) in place. Each instance takes ~ half a core and there is also always one MsiExec that terminates (similar usage) when the process is manually killed in task manager. The processes originate from \users\\appdata\local\google\update\install{GUID} - deleting the directories / files does no good, the updater downloads it after a few hours and tries again.

Video plugin installer is v 19.9.2600.0, 10,692,592 bytes

I'd like a way to stop this automated install or have it succeed. It seems I can do neither right now.

Any solutions to this in place?

Thank you in advance!

M C G
  • 11
  • 2
  • That installer MSI, is it somewhere to download? Would like to find some details such as product code to check my own system. – Stein Åsmul Dec 01 '19 at 22:45

1 Answers1

0

Quick Questions: 1) Are you behind an internet proxy server? 2) What is your security tool / malware suite / anti-virus? Can you temporarily disable it whilst the installation finishes? 3) Have a look in the "Deployment Mnemonic" section here? (for various causes of deployment failure). 4) You can try to log in as another user and install fresh - see if that works. If it does, then you need a Chrome profile cleanup? 5) There is always the reboot. Always try that first to get it out of the way as the "one-size-doesn't-fit-anyone-at-all-really fix".

Technical: If I were to guess the problem is a custom action in the MSI that gets stuck "somehow". How many msiexec.exe entries are in the tast list and what context are they in? (user, system). There can be many msiexec.exe processes. Below is information on how to debug custom action failures (and other failures) by log analysis.

Logging: If this really is an MSI installer (Windows Installer), then you can try to enable MSI logging policy to create a log file for all MSI installations that run by following the instructions in the section "Globally for all setups on a machine" here. You will then find a log file in the TEMP folder after the installer has run (whenever that might be). Look for *.log files with a random name. Just sort the folder by change date to see the most recent files.

Open Temp folder: Windows Key > Tap R > Type: %TEMP% > Press: Enter.

Debugging: You can search the log for "value 3" first to find errors (see Rob Mensching's explanation in that link). You can find more information on interpreting MSI log files in the section "Interpreting MSI Log Files" here: Enable installation logs for MSI installer without any command line arguments

Stein Åsmul
  • 39,960
  • 25
  • 91
  • 164