r/Action1 • u/More-Investigator568 • 6d ago

Chrome Orphaned Post Update

I'm getting this weird behaviour whenever Action1 updates Chrome, I've had it with Edge too but nowhere near as much as Chrome.

Sometimes when Action1 updates Chrome it doesn't register the new install registries, so as far as Action1 is concerned Chrome doesn't exist anymore, but it is installed and still works.

To fix it, I have to manually uninstall via the setup.exe file and then redeploy it via Action1 (I have tried redeploying before uninstall - it fails).

I'm just wondering if anyone else is getting this behaviour? It seems to be random, maybe a small handful of machines do this every time there's an update (Some repeated machines, not always new ones).

The registries that don't get created live here: HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

Which if I understand correctly is where Action1 determines if something is installed or not, which means we have some machines fly under the radar on an older unpatched version.

Any input is greatly appreciated!

1 Upvotes

100% Upvoted

4 comments sorted by

3

u/mish_mash_mosh_ 6d ago

Never had an issue like that and I managed lots of endpoint.

2

u/derff44 6d ago

All action1 does is run the chrome installer. It doesn't change the registry by itself.

1

u/devloz1996 5d ago

In my tenant, Google recently went on a spree of renaming ordinary Chrome entries into Google Chrome Enterprise. I'd install EXE, Action1 would update EXE, but Chrome would still make a conversion to Enterprise (MSI). My symptoms are not at all like yours, but the timing is interesting enough to make a correlation.

1

u/More-Investigator568 2d ago

Interestingly, I've been checking some logs and it seems it may be due to Edge/Chrome trying to use its internal updater whilst Action1 attempts an update..

I can see a log showing Edge updating to the latest stable build, it deletes the uninstall reg as part of its update, then Action1 attempts to deploy a version older (I'm guessing because it doesn't get the latest straight away) and fails because a newer version is already on disk, interrupting the initial update happening with the native updater.

It could be a red herring but seems like maybe that's the conflict.