My article about solving error 80048820 has ranked highly in search engines right from the week I posted it, as a result a lot of people have been referring to it and commenting on it. A few of the comments are people reporting they found another way to solve it, the big one is changing a setting in their router settings.
The first one is posted by S t r e t c H, he gives the steps involved in changing the MTU (maximum transmission unit) size in his NETGEAR wireless router to a value of 1400. This setting can be found in most routers (I think?), usually under WAN settings.
Shane also reports doing the same thing on his DLINK wireless router fixed this problem. Same with he next commenter, Robyn.
So, if you have been constantly getting this error for a while and you know how to change this setting on your setup, give it a try and see if it works. I would like to get some feedback on whether it works or not for those who do try, so I can post some more specific instructions for others.
A ranty article at The Inquirer has caused bit of a stir over the past few days, the author writes about his experience with Windows Messenger and MSN Messenger which his kids use. If you have ever been frustrated with Windows Messenger, hopefully you will understand his frustration too.
There are two main problems here: confusion with Windows Messenger vs. MSN Messenger, and Windows Messenger being not so easy to silence. Take a look at my post about the differences between Windows Messenger and MSN Messenger and hopefully see why both exist. For silencing Windows Messenger, I refer back to my article on the Windows Messenger and MSN Messenger API confusion:
Don’t uninstall Windows Messenger
No matter how annoying Windows Messenger may be, do not remove it as it is a Windows component and can cause problems further down the line. Instead, just turn it off. Open it up and go into options, turn off the following two options:
- Run Windows Messenger when Windows Starts
- Allow Windows Messenger to run in the background
For the most part, Windows Messenger won’t annoy you again.
I see bad experiences like this all the time with Windows Messenger, but not so much with MSN Messenger. MSN Messenger is a lot easier to get rid of, users instinctly go to Add or Remove Programs and the deed is quickly done. With Windows Messenger, it is under Add/Remove Windows Components and only removes shortcuts from the start menu. It even states this in the description. If you’re going to do this, also uncheck the two options beforehand as above.
Perhaps this could be easily solved by having that option “Run Windows Messenger when Windows Starts” off by default and let the user decide during install. I hope to soon see some improvements in this area with Windows Live Messenger.
I didn’t post about this here, but the Messenger team were looking for people who got error 80048883 during sign in with the latest build of MSN Messenger 7.5. They quickly got their people and have come up with a solution.
Leah has posted the following to her Messenger blog:
If you are using MSN Messenger 7.5, please follow the steps below:
- Go to http://clientconfig.passport.net/ppcrlconfig.bin
- Download that file
- Rename it to ppcrlconfig.dll
- Drop it in C:\Documents and Settings\[Windows USER]\Application Data\Microsoft\IdentityCRL\
- Attempt to sign in again.
- If you can’t get to http://clientconfig.passport.net/ppcrlconfig.bin, then email txtest_johnweis@msn.com
There are also some steps for Windows Live Messenger, but they are the generic troubleshooting steps and is very long, view the post to see them.
Over at the Microsoft forums, a user has posted for helping regarding installation error 1635. Another user has responded saying MSN support told them to use the Windows Installer CleanUp Utility, other users have tried it with successful results and even with errors 1601 and 1603.
Sounds obvious doesn’t it? Most steps for resolving installation errors for MSN Messenger involve deleting files, modifying the registry, etc. This program simply removes all Windows Installer information for the application (leaving behind all the program files, which are fine), allowing you to run the MSN Messenger installer again cleanly, as if it is not currently installed.
Just a couple of days ago I got an update prompt while using 7.5.0311 and thought build 322 was being deployed. Sure enough, a post on the Messenger Support Space has appeared about it and claims to have fixed the dreaded 80048820 error which made an appearance with MSN Messenger 7.5
If you haven’t been prompted to update (which is likely if you can’t sign in…), go grab it from the MSN Messenger Web site and see if that darn error has disappeared.
