AutoPatcher Forum

klymax, James: i believe that i've tracked the issue with WU related to IE8. they said that they choose to ignore the compatibility mode, i don't. the funny part is that one guy said that in 2 machines, it worked fine without the compatibility mode and at another 2, don't. probably the issue be related to ms mirrors out-of-date. it may happen for some time, at least

edit:
> redirected me to Microsoft Update (MU)
that happened to me when installing msn 2009. at my 2nd machine, i've installed msn 2009 with the module that i did for this one, choosing just the things that i know that are required. that machine is still running windows update

[]s

do yours wanna the good news? iecompat.dll, that comes with ie8 xp is 8.0.6001.18702. the KB968220, that has an update for ie8, has 2 versions for this very same file. one at SP3GDR folder, with the version 8.0.6001.18761 and another one, at SP3QFE folder, with version 8.0.6001.22850. can someone explain why one kb with 2 versions of the same dll? it should not be the exact same thing?

[]s

They mention both here.. one for server?

http://support.microsoft.com/kb/968220

This is actually quite a complicated issue. The following explanation is the (over-)simplified version:

Many, many publicly available Hotfixes have both a GDR and a QFE branch. If both are available, the GDR branch is normally used. Systems that already have private QFE fixes applied (through a custom support agreement with Microsoft) will apply the QFE branch.

Sometimes only the QFE branch is put in a public Hotfix, because of bugs in Microsoft's hotfix installer.

--

James, on Mar 23 2009, 06:45 PM, said:

Solved! With the final version of IE8 RTW, this happens only on a particular VM image.

On "real" hardware an error message still appears in the log file (ie8.log) but IE8 installs OK. Look for the line:

IECUSTOM: Unwriteable key HKCR\Interface\{34A715A0-6587-11D0-924A-0020AFC7AC4D}

in ie8.log. There will be more than one line, but they are all related to this Registry key and its children.

For those few people still affected, Microsoft have a Fix it solution for IE8 installation problems.
See http://support.microsoft.com/kb/949220. Click on the Fix it button to have Microsoft automatically correct the problem.

--

oh boy... IE8 is now at WU. at 20/April, it will be at automatic updates for IE6 and IE7 running Windows XP, Vista, Server 2003 and Server 2008. for those that runs WSUS, IE8 will arrive at July.

and still, most of the online banks that i know are unable to run properly with IE8. at least, firefox works...

[]s

And there's also a problem with IE 8 if you run Spybot Search and Destroy, or SpywareBlaster.

Both Spybot Search and Destroy and SpywareBlaster have been regularly reported/mentioned as causes for IE 8 being slow. There seems to be a conflict between these applications' restricted-zones lists and IE 8's SmartScreen security function.

--

This is news to me that logitech software doesn't like IE8. Go figure....I have the logitech wave keyboard+mouse and it works fine with IE7, FF3, Opera with no problem but trying to use IE8 just stops working and closes suddenly...and this is supposly the public release. Looks like they need to do some more homework on IE8 again. That so typical of M$ put out products and fail to test but let the endusers do the testing for your products.

TechSwap, that is why we are holding ie8. some scripts already have it, but ie7 wasn't removed yet due the issues that ie8 has. after all, this all is ms fault. they spare years with that faulty html, but they spare so mouth time that the faulty version becomes the default. now, to fix it...

[]s