Messages

Just wondering if you guys are planning to add this one? I can see a poll exists for a 'new application': https://ideas.patchmypc.com/ideas/PATCHMYPC-I-1284

This version of the Chrome installer seems to be clashing with RDS's Windows Installer Coordinator. On RDS servers, the install starts and then gets stuck. I'm yet to see issues on non-RDS servers (which lack the Windows Installer Coordinator).

When I disable Windows Installer Coordinator (either before the install or while the installer is 'stuck'), the installer more-or-less immediately resumes. I suspect this is a bug/feature in the new Chrome Installer. We'll try using the pre/post script to work around this for now but a bugreport to Google may be necessary.

Possible that this will also happen to Edge and other Chromium based browsers as they're based on the same code.

Can enable and disable the WIC using:
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\TSAppSrv\TSMSI" -Name "enable" -Value 0
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\TSAppSrv\TSMSI" -Name "enable" -Value 1

Are there any known issues with Google Chrome 88.0.4324.190 (x64)? I'm seeing clients having difficulty installing all updates in the last 24 hours. On a few machines that I've looked into, there's a pattern emerging, Chrome is the first PatchMyPC update to attempt installation and fails.

From: PatchMyPC-ScriptRunner.log
An error occurred: Process must exit before requested information can be determined.
Void EnsureState(State)

Subsequent MSI installs don't run because another installation is already running:
From: PatchMyPC-ScriptRunner.log
MsiExec is already running (1618).

Going the keep digging..

That new version has fixed our issue. Thanks for your help.

Thanks for the update Omar. We'll wait for that then.

Hi Cody, just wondering if there's any update on this? I was going to test deploying the application (rather than the update) to those machines that need to updated as I can add the flag to that. Also, would an MST file be appropriate to add the flag to MSP, not something I've done before.

Ah ok no worries . Please could you post back here once done and I'll re-publish the updates?

I can't update the command line options for those updates, I can update the applications. Is that expected?

When do you think you'll have things updated your side?

Ah that makes sense, thanks. I'll give it a go and report back.

Most of our machines (servers) seem to be failing with this update. They're updating from 20.013.20074.

Attached a snippet from windowsupdate.log, main part is: transaction error = 0x8024200b, MSI result = 0x80070643, MSI action = InstallWebResources

On a few machines I found that installation when I was logged in seems to work fine, but if no one is logged in (which is the case when our servers do maintenance), the update fails.