I can confirm that this has happened to me on Server 2008, as well.  Re-running 
ChromeSetup.exe (build 0.2.149.27 (1583)) as administrator allows the install to 
complete.

I can confirm this also. The main problem is that administrator cannot install 
Chrome system-wide and I can't use it under unprivileged account.

it also need to bypass the firewall i think google has to remove that to make its 
browser proper google must to provide just a simple single exe file if you have then 
u can install it on ur machine. I dont think other validation is needed for that bcz 
its free.

Same for me. 

And for me. Running Windows 2008 server and google gears fails to install because of 
a system policy. Have tried the fix for adding a software policy (as per this link: http://www.venkat.org/2008/09/installing-google-chrome-on-windows.html) but still no 
joy and can only enjoy Chrome when logged on as the Administrator which isn't ideal.

I've managed to install now and it seems to work. If you go to 
c:\users\<user>\AppData\Local\Google\Update\Download there will be a series of 
folders. Check in these until you find 'chrome_installer.exe'. Run this and this 
will then complete the install process where chrome will run and you'll get the 
chrome shortcut on the desktop plus everything else.

I installed Google Gears directly from http://gears.google.com first though. I'm not 
sure if this needs to be done or not and would be interested to hear from anyone who 
didn't perform this step first to see if this is actually required or not.

Same problem installing under Server 2003, SP2.

Running 'chrome_installer.exe' in the Download subfolder completed the installation
(as per oakman).  I didn't install gears separately and it seems to work just fine.

FYI, installing Gears separately is unnecessary. When you do that you're installing 
Gears for IE and Firefox on Windows, not Chrome.

Mmm, this might be something like what is discussed in this forum:

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=590630&SiteID=17

(No comment was entered for this change.)

I agree. This installation needs a rework. I'm seeing the same problems on an XP Pro
SP3 system - install chrome (beta) as administrator. Then I can't run it as anything
other than administrator, because the executables are installed stupidly in the
profile directory of administrator and are thus unreachable via limited users - which
is what I normally run as.

Why on earth haven't google used a normal installer like they did for Google Earth?

Mike

As a limited user on XP Pro you need to install the application as that user & you 
don't need administrator rights (or power user) to do that, I think.

Google Chrome is a user application, the user installs it & it cannot affect system.  
I guess the advantage is that it makes it very easy to install (widely). It will 
almost certainly change the security landscape, for better or for worse.

Note that it won't run under runas, which could be a pain:

http://code.google.com/p/chromium/issues/detail?id=1470
 
http://groups.google.com/group/chromium-
dev/browse_thread/thread/568bf0c33f072049/dce43ea33781875f

(No comment was entered for this change.)

(No comment was entered for this change.)

This problem also looks like was because of MSI Gears installer. It should be gone in 
the latest releases of Chrome. Closing this bug. If you still have a problem please 
file a new report.

this issue is not solved!?&*!*/?