Problem solved. For some reason there was not read rights for the C:\Program Files \google\Chrome\Application\2.0.171.0 folder for the normal user account, even though read&execute rights were ok for C:\Program Files \google\Chrome\Application\ folder.
Can not explain why this happened, but the browser starts and works now correctly. On Mar 24, 11:22 am, Mikko <[email protected]> wrote: > Hi, > > I upgraded my Chrome to use dev-channel 2.0.170.0, resulting a > successful upgrade. Previously I was using 2.0.169.1 or 2.0.168.0 (I > don't exactly remember if I upgraded to 169.1 or not). > > Now, for some reason the Chrome no longer starts with my normal user > profile on Vista32. I have Admin user account as well which I use to > install programs, and when I start Chrome with that user account it > works nicely, but not on my normal restricted user account which I use > for all the normal work. > > It looks like the problem could be in the user profile files. Perhaps > some backwards compatibility broke in the upgrade, or some other > regression, as the normal release channel build was working normally. > > I would like to try to reset the user profile files of the chrome, to > start it clean. I tried to rename / move the \Users\username\AppData > \Local\Google\Chrome\User Data\Default folder, actually the whole .. > \Local\Google\Chrome folder, but no luck. > > Any ideas how to reset the user profile files, or troubleshoot this > further? --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
