1.

Solve : More reasons to postpone that upgrade to IE 8?

Answer» http://windowssecrets.com/2009/04/09/02-WGA-blocks-some-updates-on-legit-Windows-PCs/?n=known1
(scroll down a little)

We also received bushels of e-mails from readers who agree with Mark Joseph Edwards' recommendation in his April 2 Top Story that you wait before switching from Internet Explorer 7 to the new version 8. Several people who had already taken the IE 8 plunge explained why they reverted to the earlier release. For Gene Goldenfeld, the problem was a conflict with one of his security apps:

* "Soon after installing the public release of IE 8, I noticed that it was very slow to start. I've since discovered that it's not just my XP SP3 machine alone. It seems there's a conflict between IE 8 and some resident (real-time) antispyware applications that centers around these applications' restricted-zones lists and IE 8's SmartScreen security function.

"Spybot Search and Destroy and SpywareBlaster are the ones commonly mentioned, but I use SuperAntiSpyware Pro and my zones list is short. That leaves [as the cause] an add-on conflict, which I didn't check. There are some workarounds proposed until MS fixes the problem, but the easiest one — and the one I chose for now — is to go back to IE 7. That BROUGHT IE back up to speed."

Dave Laljee found the source of his IE 8 conflict, but he rolled back to the previous release anyway:

* "Saw Mark Joseph Edwards' article in the latest newsletter and thought you'd like to hear another reason for not rushing into IE 8 (though, after uninstalling it, I discovered a workaround). I installed IE 8 the other WEEK, and at first things seemed OK — until attempting to add a C++ function within Visual Studio 2008 Pro using a wizard. This resulted in a script error.

"I quickly uninstalled back to IE 7 and rebooted. The add function, etc., worked fine in VS 2008 again. A week later, I was checking the Visual C++ Team Blog and found this blog POST [with the workaround].

That solves the problem, but you would've thought they'd have caught this one before release!"

It seems about the only thing Microsoft is catching lately is some well-deserved flak.I reverted simply because it busted my winamp lyrics plugin.

Basically it broke every program that used the internet browser control... except somehow MS programs...Quote from: Broni on April 10, 2009, 06:47:14 PM
http://windowssecrets.com/2009/04/09/02-WGA-blocks-some-updates-on-legit-Windows-PCs/?n=known1
(scroll down a little)

We also received bushels of e-mails from readers who agree with Mark Joseph Edwards' recommendation in his April 2 Top Story that you wait before switching from Internet Explorer 7 to the new version 8. Several people who had already taken the IE 8 plunge explained why they reverted to the earlier release. For Gene Goldenfeld, the problem was a conflict with one of his security apps:

* "Soon after installing the public release of IE 8, I noticed that it was very slow to start. I've since discovered that it's not just my XP SP3 machine alone. It seems there's a conflict between IE 8 and some resident (real-time) antispyware applications that centers around these applications' restricted-zones lists and IE 8's SmartScreen security function.

"Spybot Search and Destroy and SpywareBlaster are the ones commonly mentioned, but I use SuperAntiSpyware Pro and my zones list is short. That leaves [as the cause] an add-on conflict, which I didn't check. There are some workarounds proposed until MS fixes the problem, but the easiest one — and the one I chose for now — is to go back to IE 7. That brought IE back up to speed."

Dave Laljee found the source of his IE 8 conflict, but he rolled back to the previous release anyway:

* "Saw Mark Joseph Edwards' article in the latest newsletter and thought you'd like to hear another reason for not rushing into IE 8 (though, after uninstalling it, I discovered a workaround). I installed IE 8 the other week, and at first things seemed OK — until attempting to add a C++ function within Visual Studio 2008 Pro using a wizard. This resulted in a script error.

"I quickly uninstalled back to IE 7 and rebooted. The add function, etc., worked fine in VS 2008 again. A week later, I was checking the Visual C++ Team Blog and found this blog post [with the workaround].

That solves the problem, but you would've thought they'd have caught this one before release!"

It seems about the only thing Microsoft is catching lately is some well-deserved flak.

Too late for me...it doesn't slow down my computer, I don't even use it...My mom uses it on my computer, even though I'm always telling her to use Firefox instead.well ie8's not problematic to me, it's just i've left the untabbed ie world too long to go back.been runnin IE 8 for about 3 weeks and have not seen any PROBLEMS wit it.Quote from: x2543 on April 17, 2009, 09:40:27 PM
well ie8's not problematic to me, it's just i've left the untabbed ie world too long to go back.
Go back to what? IE 7 is tabbed.Quote from: x2543 on April 17, 2009, 09:40:27 PM
well ie8's not problematic to me, it's just i've left the untabbed ie world too long to go back.
IE7 has tabs. So does firefox.Quote from: Helpmeh on April 18, 2009, 06:26:05 PM
IE7 has tabs. So does firefox.

i meant that I've been away from IE6 when there was no tabs, I upgraded to Ie7 and Ie8 only for security purposes and firefox stays my way most of the time, google chrome i use now and then as well but that's that....Quote from: x2543 on April 17, 2009, 09:40:27 PM
well ie8's not problematic to me, it's just i've left the untabbed ie world too long to go back.

You've been gone from that world for a long time now.Yeah, I have noticed a few bugs with IE8 still. I am too lazy to go back though. I use FF most of the time though.


Discussion

No Comment Found