On Thu, Apr 18, 2013 at 10:36 AM, Maglinger, Paul <[email protected]> wrote: > Based on previous experience I > prompted removed it and therefore found the issue with Outlook. Since then > several others here have done the same and had the same issue. The > uninstall should be cleaner than it is.
This is a problem with the way Windows handles "default browser". Whenever the default browser is uninstalled, the file associations and scheme handlers gets all horked up. It's not specific to Chrome; any browser will cause this. Thank Microsoft for trying to cram MSIE down everyone's throat in the 90s; we're still paying for that decision. Which is not to say that bundling unrelated products isn't evil, too. If the Adobe/Google thing you describe hadn't bundled Chrome that way, you wouldn't have had to deal with this in the first place. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
