![]() ![]() ![]() *Someone identifying themselves as Rob Egan, commented on the prior posting that his problem also started "after running the portable version of chrome." Also, someone from Google was going to contact the folks at. Going forward, Google is looking into revising their logic to make Chrome more resilient to this sort of registry corruption. Every OS user gets their own bookmarks, extensions, themes and the like.Ī system wide installation of Chrome is also supported on OS X. The only thing that's shared though, is the browser code. For instructions, see Install Chrome for all user accounts. However, the more normal mode of operation is also supported. If Windows user2 later installs Chrome, their copy is totally independent of user1's copy.īy and large, this strikes me as a good thing. As a result, Windows user1 can install Chrome and Windows user2 won't see it. I mention this because regular Chrome works a bit differently from the majority of Windows software, in that it installs itself on a per-user basis rather than system-wide. Every Windows system I work on has an Administrative user (MichaelAdmin for example) and a restricted user (such as MichaelRestricted) with the latter being used almost all the time. Most Windows users probably use a single Windows account all the time. So, for example, Windows user1 can have a normal copy of Chrome and Windows user2 can run an ancient edition of Portable Chrome without causing a problem. One piece of good news is that the registry conflict is limited to a single Windows user. The Defensive Computing lesson here is clear, don't run both the portable and normally installed Chrome on the same system. I didn't suspect Portable Chrome because for many years, I have happily used the portable version of Firefox, alongside a normally installed copy of the browser (the only limitation being that they can't run concurrently). It needs to be manually updated **, which, because it's a bit of a pain, means that I typically have a somewhat recent version hanging around, but hardly ever, is it the most recent. Portable Chrome is the only application I've come across at, that does not self-update in a manner consistent with its non-portable sibling. But, in my case, the portable copy of the browser was a couple releases old. Had the portable version of Chrome been the same version/release as the normally installed copy, there would not have been a problem, even with its writing to the registry. Not only should it not write to the registry at all, it also should not have updated registry keys used by another application. Long story short, Portable Chrome was writing its version number into a location in the registry owned by Google's Chrome. Portable Chrome was not on my suspect list because of what I said earlier, portable applications are not supposed to update the Windows registry. I had used the portable version of Chrome. Then, I mentioned something, just in passing, that turned out to be critical. I was forced to think of everything that was slightly out of the mainstream. He was thorough, collecting data and asking questions about the system with the problem. The cause was either sun spots, or there was something a tad out of the ordinary about my PC. After all, Chrome works fine on millions of Windows 7 machines. We went back and forth trying to figure out what was different about my computer. ![]() Nonetheless, I was lucky enough to be put in contact with someone at Google who works on the Chrome browser. Beats me how, stats show that my mother and I are pretty much the only ones reading this blog (Defensive Computing is boring, I get it). The prior blog got the attention of the right people at Google. A big reason that installed Windows software can't be backed up is that it updates the registry, something portable software does not do. And this, in turn, led to the critical issue (not that I knew it at the time). ![]() This gripe led me to praise portable Windows software, such as the applications offered at which can be backed up. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |