It is dangerous to be sincere unless you are also stupid - George Bernard Shaw
WEB AND SOFTWARE giant Google released, without much fanfare, an update for its Chrome browser that fixes "confirmed security vulnerabilities " among other bugs including a Javascript error on Facebook.
If you download the browser today, you will automatically get the latest version. But if you downloaded it at the time it was released, you might not get this update correctly installed. The solution is to download and install it again. Some users have been complaining the initial Chrome release doesn't check for updates, but that was blamed on Vista and disabling UAC.
Google
lets us know of a new version available
We don't run Vista here, only XP SP2 yet while Chrome notified us today of a new version available, we were unable to make it install. It either stalled while showing an "installing new version" dialogue or ended with some obscure error message.
The
new version never installed, so we had to download it again and reinstall on top
of the existing one
In the end we chose the sane approach and downloaded and installed it again. To save you the hassle of using the small Google installer that just serves the purpose of hiding you the URL of the full version (a nasty practice once introduced by AOL with its Netscape 8 browser until users chastised the firm so much that they eventually began advertising the "full installer" download URLs). That is, before they lost interest in having their own browser and killed it altogether. Google might be wise not to mimic AOL's steps in any way.
The
new version
So in order to save you time and hassle here we provide you with the direct download URLs for Google Chrome build 149.29 which replaces the initial release 149.27 made available last week: find the chrome_installer.exe over here and the Google Gears msi there.
Remember it's a beta, so bugs are expected. We also expect the automatic notification, the download and installation of updates going forward will work correctly in this build. Nevertheless, all users interested in helping stamp out further bugs are encouraged to submit bug reports over here. ยต
Mine updated without issues.
It does not happen too often that a federal agency advises against the use of a software product by a major company, but the Federal Office for Security in Information Technology has done exactly that. The message is simple: do not use Google Chrome. Insecure, privacy nightmare.

http://www.tagesschau.de/wirtschaft/google144.html
Did it take out the biggest bug of all?

ActiveX

For those who do not understand why ActiveX sucks, there are multiple reasons, but one of which is the security model, and part of that is Authenticode. People who are far smarter than I am say it is dumb and stupid. But Bob Atkinson says that a broken screen saver is more important than security at Microsoft when he designed Authenticode. And that it why it sucks, because we're still stuck with that piece of crap.

http://catless.ncl.ac.uk/php/risks/search.php?query=authenticode
I can't seem to find a changelog anywhere for the new version. How do you know what they fixed with this build?
Adblock is still not working.
(And I'm still waiting for Mosaic dagnabit!)
Most users still can't scroll up with the mouse wheel.
I'm using XP Pro SP3 on a LAN behind a NAT router.

0.2.149.29 (build 1798) still thinks its update server is broken.

"Update server not available (error:3)"

and no, its not a firewall issue.