Vista - 8000ffff Live Messenger 2009 & Windows 7

I am getting an error 8000ffff when trying to sign in with Live Messenger
2009. I have uninstalled it and re-installed it and all of it's components
multiple times. That is complicated by the fact I'm running Windows 7.
The problem is unrelated to Windows 7 but troubleshooting is more complex
due to small differences between Windows 7 and Vista.

OS: Windows 7(Evaluation Copy Build 7100)
Live Messenger 2009(Build 14.0.8089.726)
Problem: When attempting to sign on with any Windows Live ID I get 'Error
code: 8000ffff'
Current Date: 11/26/2009

Update:
I've continued uninstalling and reinstalling. Restarting between each cycle
and running Revo Uninstaller and CCleaner multiple times. I've almost ready
to give up on ever using Live Messenger. Does anyone care about this product
anymore?

I am getting the same profile here mate. Have you tried it through other user accounts? That works for me, although i tried this through a local profile and it worked. Just wont work through roaming profiles :/

problem*** lol

A few suggestions

http://taurarian.mvps.org/WU_Vista/8000ffff.htm

The discussion shown here suggests that this problem is due to the Office XP
SP3 update:

http://www.microsoft.com/communities...f957de147c&p=1

You might see if the following search yields anything relevant to your
situation:

http://www.google.com/search?sourcei...icrosoft%2ecom

MS offers 2 resolutions for the 8000FFFF error. PABear has posted one.
The other is: http://support.microsoft.com/kb/949104

Other than that, an in place upgrade or a format/reinstall are the only
methods left to resolve the error.

Also, from KB958690:
http://support.microsoft.com/kb/958690


There is, for example, at least one "hotfix" for a similar problem (error is
not identical) in Windows 2000. So, a lot would depend on what version of
Windows you're running.

"Error when you download updates using Windows Update or Microsoft Update:
8000FFFF
http://support.microsoft.com/kb/946414

However, there is a very good chance are that you are seeing the affects of
a hijackware infection.

1. See if you can download/run the MSRT manually:
http://www.microsoft.com/security/ma...e/default.mspx

2. Run this online scan (in safe mode w/networking, if need be):
http://onecare.live.com/site/en-us/center/howsafe.htm

3. Run a thorough check for hijackware, including posting the requested
logs in an appropriate forum, not here.

Checking for/Help with Hijackware
http://aumha.net/viewtopic.php?f=30&t=4075
http://mvps.org/winhelp2002/unwanted.htm
http://inetexplorer.mvps.org/data/prevention.htm
http://inetexplorer.mvps.org/tshoot.html
http://www.mvps.org/sramesh2k/Malware_Defence.htm
http://www.elephantboycomputers.com/...moving_Malware

**Seek expert assistance in
http://spywarehammer.com/simplemachi...php?board=10.0,
http://forums.spybot.info/forumdisplay.php?f=22,
http://aumha.net/viewforum.php?f=30, or other appropriate forums.**

If the procedures look too complex - and there is no shame in admitting this
isn't your cup of tea - take the machine to a local, reputable and
independent (i.e., not BigBoxStoreUSA) computer repair shop.
=====================
Start a free Windows Update support incident request:
https://support.microsoft.com/oas/de...spx?gprid=6527

Support for Windows Update:
http://support.microsoft.com/gp/wusupport

For home users, no-charge support is available by calling 1-866-PCSAFETY in
the United States and in Canada or by contacting your local Microsoft
subsidiary. There is no-charge for support calls that are associated with
security updates.



--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"BrianKotarski" <BrianKotarski@newsgroup> wrote in message
news:397D54E4-CDC5-477C-B604-6D0AD8E79396@newsgroup

Hello everyone. I found the problem - I had Windows Live Messenger installed on the server (Windows Server 2008) also, which for some reason was conflicting, causing this error. Removed Windows Live Messenger from the server, and it works fine.

I am going to upgrade to Windows Server 2008 R2 x64 tomorrow. Will see if it's OK after this.