For whatever reason, there seems to be no forum for Google ChromePortable, so here goes:
ChromePortable extensions do auto-update. This is unexpected for a portable app as it will trigger warning signals in an enterprise environment. Please disable this "feature" in ChromePortable. Thanks.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Why would it trigger warnings? Mozilla Firefox's extensions have always auto-updated in corporate environments without issue.
Sometimes, the impossible can become possible, if you're awesome!
Because of the update URLs specific to the particular extensions installed, maybe?
If your corporate environment is sniffing on these URLs, it is likely use of Google Chrome is prohibited. In which case, Google Chrome Portable should not be used in that environment. Being able to use your preferred browser is not worth losing your job over.
If that is not the case, you should determine what software is alerting and let your IT team know so they can turn off the alert.
Sometimes, the impossible can become possible, if you're awesome!
There is a difference between "prohibited" and "tolerated". My corporate environment runs a security tool that seems to work by getting a list of the "top n" URLs accessed by users withing a certain time frame and disabling access to some of these URLs based on criteria that I can only guess. So now you have the reason why I do not want extension update URLs to be accessed every time I launch ChromePortable. Otherwise I would just install the regular Chrome browser.
But of course, I always appreciate it when other people tell me what is best for me and what I need and don't need. Thanks.
I wasn't trying to tell you what is best for you
Just pointing out that using portable software may not be the best idea in your situation if it is prohibited. Some people get fired for using unauthorized software. It depends on the company.
It makes sense for most users, so we wouldn't disable it by default. If you'd like to disable it in your copy, you are free to do so. If Chrome supports disabling it, that is. From a quick web search, it would appear they've made it next to impossible for an individual end user. In that case, you're likely better either getting IT to install the group policy setups that disable it or using a browser that lets you fully control it like Firefox.
Sometimes, the impossible can become possible, if you're awesome!
I don't see why would that be a problem.
Unless you want to update your extensions.
Previously known as kAlug.