mynetx

Been trying Messenger 2010? Problems might come up. (Update)

You have been trying Messenger 2010 recently after downloading and installing the leaked Milestone 2 beta 15.2.2583.119? You might get problems when you want to go back to Messenger 2009.

The problem – compatibility flags

When you use Messenger 2010 for the first time, it seems that your Windows Live ID gets some special flags in your profile data. Even if you remove Windows Live Wave 4 completely, you might see that your contacts cannot send you nudges or files. Instead, they might get the following message: “You cannot send a Nudge to your contact because he or she is using an older version of Messenger” or similar.

A possible solution

Currently, I only know of a solution that might work. There is no guarantee.

Attention: The price is that you lose all local Messenger settings.

  1. Close all Windows Live programs.
  2. Right-click your taskbar, and choose Task manager.
  3. Click any process called msnmsgr.exe, wlcomm.exe, wlmail.exe, sync.exe, writer.exe, and End process.
  4. Download and run the tool ZapMessenger by MVP Jonathan Kay.
  5. Retry to install Windows Live 2009 from download.live.com.

Update: The problem was server-side and has now been fixed. Thanks for your patience!

4 comments

  1. Hi Klaus,
    The solution you have provided doesn’t work since the problem is actually on the Windows Live servers. Thousands of people experienced the same issue with their account after trying Windows Live Messenger 2010 Beta. If you sign into Messenger with the corrupted account on another computer, the problem still persists – so this is really a server-side problem. There is an active thread in the Windows Live Solution Center with this topic, you can find it here: http://www.windowslivehelp.com/thread.aspx?threadid=f6634364-9366-4975-bfd7-b4a7253afa86 . The Experts of Windows Live at Microsoft are investigating the issue with the help of the users and log files we provided.

  2. Although you say the problem has been fixed because it was a server problem, I still get the same problem!!

Comments are closed.