Status: Untriaged Owner: ---- CC: da...@chromium.org, kuch...@chromium.org, c...@chromium.org Labels: Type-Feature Pri-2 OS-All Area-Installer
New issue 7077 by hu...@chromium.org: Ability to notify/repair a badly corrupted installation http://code.google.com/p/chromium/issues/detail?id=7077 If the user's installation is corrupted in a bad way, e.g. the version key in registry exists but the file payload is gone, there is no easy way for user to fix until a higher version of chrome available. All first install/update will just silently exits. If this is an update, this behavior is probably ok. But if this is a first install, then the user is clueless on what happens. Not sure what is the best way to do here. We could consider some UI message if same or higher version is detected during first install. But in most cases, if same or higher version does indeed exists, silent completion might have better user experience. Or we can have a force-install option somehow? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
