But sometimes, simplicity is exactly what you want. There’s no denying that Google Chrome is beautiful, and it’s fast, too. It’s full of nice touches, like the ability to drag tabs into new windows and a status bar that gets out of your way when it’s not needed. All style, little substance, and great attention to detail: if only it were grossly overpriced, I’d swear it was an Apple product.
I really don’t recommend Chrome for most people: there are just too many problems and shortcomings. It feels like a proof of concept, not an finished product. Overall market share would seem to agree with me. But for those who have been won over by Google’s elegant design, or for those who like to run a variety of browsers, you’re going to get a nasty little surprise when you try Chrome on Windows 7:
The Program Compatibility Assistant does a very good job of warning users when there is a problem. When is says “This program has known compatibility issues”, it’s a good idea to listen. Sometimes the problems are minor and easily ignored. Sometimes the problems will destroy your system. But the problems are always there.
In this case, nothing will break your system. But Chrome won’t work. Instead, it displays a snarky “Aw, Snap!” error message when you try to browse to a site and notes that “Something went wrong while displaying this webpage.” If you massage it a bit, you can get other types of errors and crashes, but it still won’t work.
Now, I know Google likes simplicity, but when things go sour, simplicity is a horrible idea. Not only does Google Chrome fuck up, but it doesn't even have the courtesy to explain what happened. If you loan a friend your car for the weekend, you want him to take care of all the little details for you. You don’t need to hear about exactly what routes he drove, where he bought gas, and so on. But if he returns your car as a mangled heap of steel and blood, you damn well want a bit more of an explanation than “Something went wrong” and a cutesy sad face.
I have plenty more I could rant about, but perhaps for now I’ll just shut the hell up and tell you how to fix this. It’s simple, really: you just have to run chrome.exe like this:
Note that the only space is before the first hyphen; this is one argument, not three. I’m assuming this argument tells Chrome to run plug-ins – such as Adobe Flash – in the same process as the browser. This is not a great design as far as security is concerned, so hopefully Google will fix this soon.
This helps on the command line, but to actually make Chrome work when you start it normally, you’ll have to change the properties of its shortcut. Right click on the Google Chrome link on your desktop or Start menu and click Properties. For the taskbar shortcut, right-clicking opens a jump list; just right-click on the Google Chrome link in that jump list to find your Properties option. Then, add “ -in-process-plugins” to the end of the text in the Target textbox. You’ll have to do this for each shortcut.
When you run Chrome, you’ll still get the compatibility warning. In fact, you’ll get the warning each time you open a new tab in Chrome. To get rid of this warning, just check the “Don’t show this message again” checkbox and click “Run Program”.
If you want Chrome to work as your default browser, you have even more work to do. It looks like some people have had limited success by following the instructions at http://www.sevenforums.com/software/930-chrome-chromium-windows-7-64bit.html, but not without problems. Also, Google Chrome installs on a per-user basis, and this is a per-machine fix, so if you use multiple profiles, things will get messy. Really, I strongly recommend against using Chrome as your default browser.
You might also have trouble getting Flash to work. If so, browse to http://get.adobe.com/flashplayer/ and follow the instructions there. The installation is a bit wonky; you may have better luck you if save the Flash setup file, close Chrome, and then run the setup file you just downloaded.
Or, you could ignore all this bullshit and just click Internet Explorer.