Actual versions of chrome and firefox appear disconnected from versions shown in Chocolately
I have a Windows Server 2019 machine with Chocolately, chrome and firefox installed. Currently when I run the command 'choco outdated' I see this:
Firefox|88.0.1|94.0.1|false GoogleChrome|90.0.4430.212|95.0.4638.69|false
However if I inspect my installed apps, I see that chrome is fully up to date, and firefox has version 92.0. Furthermore if I run the command 'choco upgrade firefox' it runs successfully, but if I open firefox and check it's version it still shows 92.0.
Why is there a disconnect between these version, is chocolately managing fully separate installations of these applications?
edit. Running uninstall commands for those packages and reinstalling them does make everything sync up again, but I have no way of knowing if they'll stay synced or not.
Posted Nov 9, 2021, 8:15 PM UTC · edited
Some browsers, and other apps, update themselves.
Chocolatey only knows what package version was last installed using chocolatey. It knows nothing about versions installed outside of chocolatey
Chocolatey will download and try to install the latest packaged version, even if it is already installed. Which is usually fairly harmless.
Just do a
Or
Don't uninstall it.
You can also pin the versions to not worry about updating them or it showing them as outdated. I don’t worry about chrome or Firefox when I install them with Chocolatey and pin them so I don’t get warnings.
I usually put the -y last and when I first looked at your comment I thought you were doing a “y’all” command and though “what the crap is this? Southern Silicon Valley at work here I guess”.
Chocolatey Pro and Chocolatey For Business will notice that a package managed by Chocolatey has been upgraded. It's called the automatic synch.
This doesn't really account for the fact that when I attempted to upgrade firefox with chocolately it didn't actually work. After running the upgrade command I opened firefox and it was still the old version?