Replies

More of the scare tactic being fostered by Microsoft. The author says “A successful infection on an XP system could easily spread to other machines.” If the other machines are Win 7 or Win 8 machines, shouldn’t they be less vulnerable? And both Win 7 and Win 8.x, despite it’s inclusion of MSE are delivered naked and vulnerable. A dual layer of protection, i.e. antivirus and antimalware is needed, and the layer of protection to an XP machine should keep it safe.

“JoeP517
If by Preparedness Tool you mean KB2670838 that should be run before IE10 is installed not after.”

Thanks Joe. I guess I have to be more specific in my language. I ran KB2670838 prior to the install, as was/is indicated in the KB article. After the “mis-behavior” of the first install I ran it again which verified that the needed updates were in place and wrote nothing to the drive. I then ran it again after the uninstall of IE 10 to insure that nothing needed was removed. Therefore, it was needed and used for the initial install, not needed for the subsequent but unsuccessful re-install.

And the event logs are not informative, including the Application and Service Internet Explorer sub-log as well as the Windows Application, Setup and System logs. No problems cited, errors or warnings concerning IE. No forwarded events. The install and uninstall appear problem free. But as I said, IE 10 won’t run and on uninstalling it IE 9 64 bit works fine, 32 bit is non-functional. This is clearly demonstrated by running iexplore.exe from the appropriate directories. The x86 version hourglasses for a few seconds and then nothing.

Thanks for the reply. I believe you’ve misread my post but I also omitted something. IE 9 64 bit is working fine. Prior to the failed IE 10 install and uninstall IE 9 32 bit and 64 bit ran fine. Now only 64 bit works. And, most importantly, I am looking to solve the IE 10 issue.

Your are going to need to add the DWORD key to the list you mention here. I was experiencing this same issue where it would hang on shut down. I’m running Outlook 2007 in Windows XP.

I added “NoService to Data” with a value of 1 to the list of what you have mentioned and then tried launching Outlook. Once it was fully launched, I shut it down and I have to say, this is the first time in a while it went completely closed on its own almost as soon as I finished clicking the X (I usually watch the system tray for the Outlook icon to go away).

See if that works for you.

BTW: @JohnBF – thanks for the info!

This cured the problem for me. Thank you. But I believe you need to remove the spaces from the new DWORD NoService to Data so that it reads NoServicetoData.

Thank you all for your replies, but as I stated in the original post, I’ve run the official MS trouble tree and I’ve researched this to death but haven’t found a solution. If you click on the link that was included in “MaBelleMichelle Error 800488eb Here is your error message addressed” you’ll see that it’s been addressed but not solved.

“Windows Live Corrine V.”, a member of the Live Team, posted this response on December 27th, 2010 (partial quote) “The error 800488eb is a known issue on Windows Live Messenger and is being investigated on. For you to be able to communicate with your friends, you can sign in to Web Messenger or downgrade your Messenger version.”

Yes, you can use Web Messenger, with no camera or audio support, but downgrading doesn’t work. It is obvious from just doing a Google on the error that thousands are having the same problem. As I use this to communicate with my son who is on duty in Afghanistan, I’ve switched to Skype, which works just fine. But I don’t consider that a solution as Messenger is still broken. Two months after a quasi-official recognition that there is a problem it still is not fixed.

Also noticed that in a POP3 environment using Gmail, the SPA box was checked after the 12/14 update, thereby disabling Gmail, which requires SPA to be turned off. It took awhile to figure that one out. I’ve seen it on about a dozen Vista and Win 7 machines running Outlook 2007.

I’ll add my vote for TeamViewer 5. It’s solid as a rock, autonegotiates your router and/or firewall and is absolutley seamless. You can also run it as a quasi-portable app, leaving a zero footprint in the registry. No tweaking is needed. Just run it on each end and it’s like your sitting at the client.