So, I just reloaded the laptop, and installed Google’s Chrome browser. (I’d rather not, but being in the web development world it’s best to have a variety of browsers installed.)
I installed under the local user, then I joined my corporate domain. When I logged on as a domain user, I couldn’t find the Chrome executable. Looked in C:\Program Files, then searched the C: drive. Nothing. WTF? Where did Chrome go?
So I went over to my desktop to see what my shortcut was pointing at. Ah. The answer.
C:\Users\[UserName]\AppData\Local\Google\Chrome\Application\chrome.exe
Again. WTF?
Apparently Chrome installs itself to the user’s AppData folder (which is hidden – thus not searched – by default). After reading a bit online it seems that it installs this way so users without Admin privileges can install the application.
Great for people in the corporate environment who want to get around IT, not great for those IT departments. Also not OK for people who set up, say, their parents, with non-admin access to their own PCs so nothing gets “accidentally” installed resulting in a long-distance service call.
I had no idea you could just bypass the admin requirement by installing to a different location. Not cool.
This install scheme means that if you and your wife share a computer, but have unique logons, each of you would have your own version of Chrome installed. So you’d each have to update your instances separately.
There may be some merits to “user-based” application installs, but I’d rather not have Google make that decision for me, without my knowlegde or consent. But I suppose that’s their style, isn’t it.
“Hey baby, we’re not evil! Trust us!”

Subscribe / RSS