quote:
Originally posted by egw1
See this link here and you will understand what is going on. There is a bug with this messenger version and it is very frustrating.
http://windowslivehelp.com/thread.aspx?threadid=9...e1290ab4cdd&page=1
What is said there: a local problem (contacts cache becomes corrupt due to some reason
(of which one of the reasons was removing some DLLs and/or tampering with the previous version of the Messenger program to circumvent the mandatory update)) and also some possible misinterpretations of people on how these different contact lists work, are exactly the same as what I've been saying since a long time and which was questionned and said to be untrue. But those causes are two of the 'standard' causes, and that thread confirms that now (I must admit, before, I hadn't a public source to back me up though).
PS: They don't say "it is a bug" though! It is said it is "a problem" with the "last version". There is a small difference. It means people experience the problems when using the last version. But in fact, there is only one version, so of course people will experience it in "
the last version". Aka they wont experience it in any previous version because such a previous version wouldn't work anymore. So, in essence, what is said and how you should interpret it is: "
there is a problem", if you catch my drift. But of course we all already there is a problem... so, yeah...
Anyways and however, these days, another major issue is the new version of the protocol and an upcoming change in the internal relationships between the various contact lists. The Messenger program is still the same as before, but the protocol and some other, but very important internal server-side stuff in regards to how the various contact lists work with eachother, is changing to prepare for the upcomming new Messenger version. But I can't/shouldn't really say more about that though... And because of that almost everybody is now experiencing problems with the Reverse List.
But, after reading that thread, it seems to me that the support people are not quite up to date yet with their information (the support people don't always have all the information either of course; they give support and can only work with the info which is given to them from 'upperhand'. They even said so themselfs in that thread).
So, all in all, yes, that thread explains a few things of what could be the cause. But this is nothing new to the threads in this forum about this subject because those causes have been listed and explained before in some of the threads here. Nevertheless, thanks for linking to that thread on the Windows Live Solution Center. It will be interesting to see where it goes from here and what the support peepz have to say about it.
/ 
