chrome://components

I've been watching through months using Chrome, components don't update automatically themselves just by simply opening Chrome or updating to a new Chrome version.

Aren't those components supposed to be transparently updated without user intervention?

Besides, some of them won't even update at all, their version remains ZEROs.

 

For example "Origin Trials" is only updated after a specific flag has been enabled - chrome://flags/#enable-origin-trials
This "feature" makes use of the infrastructure for component updates, therefore it is listed in about:components

I'm not sure in which intervals it checks for updates, but sometimes i have to click on "Check for update" to have a current version for some components (for example the Flash component)
And some components don't receive regular updates, so you don't see them regularily updated.
But theoretically they should be automatically updated

There is also a group policy setting: "Enables component updates in Google Chrome". If set to false, it blocks components (not all) from updating.

 

@mood

Wow! I wonder how much time you spend investigating in detail, knowing each and every feature in-depth of so many programs and their behavior. Thanks for your hard work. It's amazing

 

Yes. I've experienced this same nuisance.

Alright, I agree.

Yes they should but they don't. Perhaps, now having second thoughts, due to I spend most of my computer time in shadow mode (Shadow Defender), components get updated in the background so when I reboot the machine if they got updated, at restart they're gone, obviously.

 

I think this is very important:

Ref: https://getadmx.com/?Category=Chrome&Policy=Google.Policies.Chrome::ComponentUpdatesEnabled

So basically when you install Windows, next Chrome, next the policy template OR not, Google Chrome should update automatically and transparently in the background.

I'll keep an eye on it and shadow mode sessions.

 

I'll do my best

Each component is saved in a subdirectory of: %LOCALAPPDATA%\Google\Chrome\User Data\
You'll notice a component-update if a directory has been modified.

For example "Signed Tree Heads" has been updated to 547
It is located in the directory: CertificateTransparency and a subdirectory "547" was created yesterday.
Old versions are automatically deleted after some time, "546" was there some hours ago but it is now gone.

 

@mood Many thanks.

 

Might be a sidetrack but:

Does anyone know how to prevent specific components updating or remove those components entirely?

 

So is it a good idea to manually update these components? Is that what you guys do? So far, I have only been manually updating Flash Player component. Your input is appreciated.

 

Yes, it's what I exactly do so far.

 

Ha ha, this component updater is "sleeping". First time I have seen that terminology.

 

I just check and mine updated to V 734.

I wonder what that does?

 

Per Google, something to do with SSL certificates. Mine has now updated to 734 as well.

Check out Origin Trials - Version: 0.0.0.0
Status - Update error

 

Got the same error.

Perhaps a remain from former functions?

 

You can attempt an experiment and try to enable the flag "Original Trials" (see below)
I guess the component is then available and updateable.

 

I don't like the word 'experiments'.

 

Didn't work @mood Thanks anyway.

 

Ok, it was just a guess