Shoutbox

Two days ago when I went to start MSN Live Messenger I had multiple requests for me to add them to my contact list (at least 10) As I didn't know any of them I added them to my ignore and blocked list. The next time I tried to start MSN Live Messenger it wouldn't start and I got a "Windows Live Messenger has encountered an error and needs to close....etc." error window. The error signature is
AppName: msnmsgr.exe      AppVer: 14.0.8117.416     AppStamp:4bc935af
ModName: wldcore.dll      ModVer: 14.0.8117.416      ModStamp:4bc93503
fDebug: 0       Offset: 00002ee5
and I have sent the error report to Microsoft
I have no idea if the smam requests have anything to do with the other error or if this is just a coincidence.
Today a friend told me he had the same thing happen to him. Has anyone else encountered a similar situation and if so what is the solution. I did remove MSN Live Messenger and installed again but with the same end result.
Thanks for any help or advice.
Wayne

Hi camerashy44.

I posted the solution to someone with the same problem last month. Here it is:

quote:

---

Originally posted by Windows Live Cattleya B.
Hi,

This could be caused by third party programs or a spyware. To fix this error, try the steps from this link. If you are using Windows 7, try the steps for Windows Vista.

http://messenger-support.spaces.live.com/blog/cns...8B853F!15940.entry

Let us know if you have other questions.

Thanks,

Cat B.

---

And lastly, a few pointers:
- The correct name is Windows Live Messenger, not MSN Live Messenger.
- This topic should be in the Windows Live Messenger support forum, not Messenger Plus! Live.
- Please search before posting.

This problem is caused (as far as I know) by a software update corrupting the profile picture.

This is what you need to do:

Click on "Start > Run".  Type "regedit", and click on ok.
Then start navigating the tree structure on the left hand side to "HKEY_CURRENT_USER\Software\Microsoft\MSNMessenger\PerPassportSettings\{numeric string here}"
 
find the value thatstarts with "UTL"
Backup the {ID} key by go to File –> Export –> Then save the registry file.
 
After backing up, delete the UTL value, and restart your computer

MSN will now start but you will need to put up another display picture.

Thanks yellowcat, that fixed a very annoying problem!  I actually just renamed the "UTL" key to "UTL_old", and restarted Messenger.  A little less work than exporting a reg file.

quote:

---

Originally posted by beastie
Thanks yellowcat, that fixed a very annoying problem!  I actually just renamed the "UTL" key to "UTL_old", and restarted Messenger.  A little less work than exporting a reg file.

---

Now you have a completely useless key in your registry though.

quote:

---

Originally posted by Lou

Now you have a completely useless key in your registry though.

---

It's not the only one, for sure.  Ever done a registry clean-up?  Thousands of unused or orphaned keys.  One useless key won't make a difference.  Besides, I deleted it after I was sure things were working again.

Thanks to Chris4 I have solved the problem....still don't know what caused it but it's fixed.
Thanks again Chris4

spoke too soon...got messenger working for a few hours and now I have the same error screen....

1. Open the Registry Editor, by clicking Start (Windows Logo Pearl button), and then type regedit then press Enter. (If you’re on Windows XP, click on Start -> Run.)

2. Navigate to: HKEY_CURRENT_USER\Software\Microsoft\MSNMessenger\PerPassportSettings

3. Look in each passport folder (if more than one) and locate the "UTL" string containing your email address. Delete it.

4. Close the Windows Registry Editor, and reboot your computer.

Source: Windows Live Solution Center

Chris4,
Messenger keeps failing and creating the same error message. If I go in to the registry and remove the UTL string it works again.....at least for a while .... it has failed once today but has worked since.
Weird that this issue just seemed to start out of nowhere  and that I know of at least one other who is having the same problem.