Category Archives: Messenger Tools

Messenger Reviver 2 temporary download

Update:
Both Google and Microsoft unblocked the original Reviver links from their respective browser detection engines within 12 and 3 hours respectfully.

Although frustrating for the need to continually stay on top of these false positives, I do applaud them both for being quick and relatively painless to resolve the situation.

I have returned all the links, with the exception of this page, to the originals.


 

Here is a temporary link to download Messenger Reviver 2

Download Messenger Reviver 2

It seems someone doesn’t like the idea of Messenger Reviver and has reported all my links as malware.

2015-12-16_16-07-24

I suspect this may be related to McAfee being slow about removing a recent false positive.  Having these false positives removed takes up time in my life every week, but the antivirus vendors have always removed Reviver without question, although naturally they take their time about doing it.

I find the best way to check software (including Messenger Reviver) is to use virustotal.com.  The current analysis reveals that almost every vendor agrees it’s clean.

In the past, I have had infrequent threatening comments directed at me, specifically from those who trust their antivirus software without question and claim that I am harming their computer.  I have had my registrar falsely accuse of me of distributing malware, giving me a 24 hour warning to “remove it” or risk losing my entire account.  In all instances in these situations, after reviewing the real facts, these people stand down.

Ignoring anything else, just thinking logically, why would I, someone who has been assisting people with Messenger problems for for nearly 15 years, run a blog for 10 years, with comments, forum, live chat on a variety Messenger related topics, only to trick a few people into installing malware now.  Why would I ruin my reputation like that?  It just doesn’t make any sense.

Messenger Reviver does not do anything other than what it says it does.  It does not report any statistical data or personal data about yourself or your computer, it does not install anything other than Messenger, it does not contain ads, or contain any income-generating mechanism.  Messenger Reviver loses me time and money and it is simply a work of love.

Which is exactly why the icon for Reviver is Messenger with a heart.
reviver2.png

Thanks everyone for your support.

Butterfly Messenger

It’s no small thing to say that the reaction to Windows Live Messenger 2009 and related clients that use the older Messenger protocol has been pretty intense.  Regardless if you’re using Windows XP, you have a favourite feature that’s missing in the 2012 version, or you simply do not want to use Skype, it seems everyone is looking for another option to choose from.

Butterfly Messenger

Butterfly Messenger is an improved working version of the client used to demonstrate MSNPSharp.   It supports the same protocol version as Windows Live Messenger 2012 (MSNP21), and has the a basic Messenger feature set.

The current release is an alpha version of Butterfly Messenger intended to be used to collect feedback on bugs, features and other changes.  However, it is relatively stable and usable.

Butterfly Messenger

System Requirements

Butterfly Messenger currently requires Windows XP or above with at least the .NET Framework 2.0 or above installed.

Although MSNPSharp was deliberately written to support Mono (on other platforms), the client presently does not run on Mono (but probably works on WINE), hopefully this will be addressed later for Linux and/or OS X compatibility.

Download and installation

You can now download the third alpha release of Butterfly Messenger.  Due to the early nature of the project, it does not presently have an installer and you will need to extract the files to a folder of your choice and run it from there.  Butterfly Messenger makes use of the Segoe UI font (like Messenger).  If you do not have the Segoe UI font installed right now, you can install it from the Messenger 2009 files.

Feedback and bugs

Please feel free to leave quick comments here on this post, but if you wish to go in depth, you can make use of the Butterfly Messenger category on the forum.

Known issues

  • Depending on the situation, brand new conversation windows may blink even if they’re in focus.  If you start typing a reply, they should stop blinking.
  • Flickering in the contact list.
  • Custom emoticons will appear, but the current conversation window does not support animated GIFs.  Animated GIF display pictures work though.
  • You cannot rename contacts.

Open Source

Butterfly Messenger is open source software and based on the MSNPSharp project code.  A repository will be set up shortly once more details about the project have been finalized.

Oct 10 2015 0.1.2.0
  • Further nameserver exception fix
Sep 23 2015 0.1.1.0
  • Fixes Nameserver exception trying to connect to 25.127.129.101 by changing server hostname to the same one used for Reviver
Mar 25 2015 0.1.0.0
  • First alpha release of Butterfly Messenger

Adium Messenger Reviver

This page remains here for archival reasons.  As of March 12th 2015, the last of the servers accepting sign-ins from Adium have gone offline.  To use the Messenger service on the Mac, you will need to use Skype, the web-based Outlook.com client, or Windows Live Messenger 2012 in a Windows virtual machine.

adiumreviver

As there’s been some requests for this, I put together a simple dmg which lets you copy the newly patched libpurple to the correct Adium (/Applications/Adium.app/Contents/Frameworks/libpurple.framework/Versions/Current) folder.  Hopefully Adium is updated soon so this won’t be needed.

Update: In addition to the above, due to changes on the Messenger servers, you will now need to make a small adjustment to make Adium work.  Choose the Adium menu, choose Preferences, double-click the MSN account, choose the Options category and change the Login Server to be msn.messengergeek.com and click OK.  This should be included in a future Adium Reviver version.

The post, Most third-party Messenger clients have gone offline temporarily has more info about the change made.

Additionally, you can also revive the official Messenger:mac client.

Known issues

  • If you receive a message that the “libpurple folder” requires an administrator password, you probably don’t have Adium or the right version of Adium installed.
  • On some accounts you might not be able to see your full contact list, this should soon be resolved in other clients and hopefully fixed in Adium too.

Messenger Reviver 2:mac

Messenger Reviver 2:mac

This page remains here for archival reasons.  As of March 12th 2015, the last of the servers accepting sign-ins from Messenger:Mac have gone offline.  To use the Messenger service on the Mac, you will need to use Skype, the web-based Outlook.com client, or Windows Live Messenger 2012 in a Windows virtual machine.


Starting November 13th, 2014, Messenger:mac clients are no longer able to sign in to the Messenger service and you will receive the following error:

Sign in to Microsoft Messenger failed because the service is not responding.  The service is not available or you may not be connected to the Internet.

Messenger:mac failure

As the underlying problem is similar to the issues from earlier this week, using the same technique used by the third-party clients and for Windows Live Messenger 2009, we can revive Messenger:mac.

Using Messenger Reviver 2:mac
To revive Messenger:mac, download the Messenger Reviver 2 dmg and open it from the Downloads folder.  Then right-click on the Messenger Reviver 2 mac icon and choose Open.
Messenger Reviver 2: mac opening

If you receive the “unidentified developer” warning message choose Open when asked.   Next, you may get a message reminding you that you’re about to install software, click Continue.  You can then click Continue to the Introduction screen, then the Install button, type in your password, and finally click the Install Software button.  After Reviver has completed, Messenger:mac should re-open and you should be able to sign in.

Important note: Unlike the Windows version, Messenger Reviver 2:mac at this time is not able to automatically download and install Messenger:mac.  If you do not already have it installed, you can install it from c|net Download.com.


Known issues and workarounds
When you sign into Messenger:mac after using Reviver:mac, you most likely will see various contact list addition requests from your contact list.  This is a side effect of tricking the server, and can either be ignored or dismissed.  Unfortunately, they will return again when you sign in again.  This issue is being seen in various third party clients as well.

In addition to this, even though contacts appear on your contact list, you might receive a message “Do you want to accept a message from an unknown sender”.  Click the Accept button and you can proceed with the conversation.

Lastly, on some accounts you might not appear online to your contacts.  Regrettably, this is a result of the same issues above.   You can workaround this problem by signing in on another client first (including logging into your Microsoft account at Outlook.com) and then signing into Messenger:mac.  The other client will put you online and Messenger:mac will take over your Messenger session.

System Requirements
A compatible version of OS X running Messenger:mac 8.0.1

Use Messenger Reviver 2 to bring back Messenger and beat Skype

Messenger Reviver 2

Download Messenger Reviver 2
Version 2.4.8.47
SHA-1: 57C9BD1C8DA9482179D3F4623021AD350CF1B22B
SHA-256: 4F8FBD96FEDFD64C54F92E906AE55CC0C80640391A4AF0653B6144922F427CCC

March 12, 2015
Now Windows Live Messenger 2012 only
With the removal of the last servers supporting the older version of the Messenger protocol, versions of Messenger prior to Windows Live Messenger 2012 will no longer work.

If you’re using Windows XP, Mac OS X, Linux, or any other non-Microsoft Messenger client, you will need to either use Skype or the web-based Messenger client in Outlook.com.

Windows Live Messenger 2012 current issues:

  • When you sign in you will briefly see a message indicating that your e-mail address is not verified. This started on on March 5th. It can be ignored.
  • Hyperlinks will need to be copy/pasted to a browser as they presently don’t show up as a hyperlink.

Messenger Reviver 2 automatically installs, repairs and/or modifies Windows Live Messenger 2012, 2011, 2009, and 2008 as well as Windows Messenger to continue signing in despite being blocked by Microsoft.

Reviver 2 supports modifying all language versions and can automatically install either 2009 or 2011/2012 versions in 47 different languages.

You will receive one of the following messages if you’re being forced to upgrade to Skype:
A newer version is available. You must install the newer version in order to continue. Would you like to do this now?
A newer version has been downloaded and is available. You must install this newer version in order to continue. Would you like to do this now?

Update Forced

To bypass the forced upgrade, download my Messenger Reviver 2 utility and run the application. As this requires changes to Messenger you may receive a message asking you to allow Reviver to make changes to your computer.

Reviver will automatically attempt to detect if Messenger is still installed, which versions are eligible for modification and if you need to run a repair or new installation to bring Messenger back (if Skype has removed it).

Download Messenger Reviver 2

Also available: Messenger Reviver 2 zipped if you are experiencing problems with running Reviver.

Requirements
Windows Vista, Windows 7, Windows 8, Windows 8.1, Windows 10

Messenger Reviver 2

To revive Messenger, click Start and the process will automatically modify Messenger and restart it.

If Windows Live Essentials is not installed, you will presented with options to either install Messenger 2009 or 2012 in the language of your choosing. Reviver will attempt to guess which language you prefer based on your prior Windows and Essentials language settings.

Additionally if Essentials is still installed, but Skype has removed it, you will be offered to repair your Essentials installation.

revivernewinstall Reviver Repair

Advanced
Advanced options If you wish to do a manual re-install or repair, you can select these options by clicking the Advanced button and choosing the function you would like.

If you are attempting to revive Windows Messenger on Windows XP and do not have Windows Live Messenger already installed, use the Patch Messenger option in this menu to revive it without further Live Essentials installation.

Easter Eggs
As Messenger Reviver 2 will probably be my last exclusive Messenger project, I have added a few small Easter eggs into the application for fun.

Animated MSN butterfly
MSN Butterfly When you open Reviver, you’ll find an animated MSN butterfly in the main window. This is the original butterfly that flew around from MSN Messenger 5.0. Based on highly advanced software engineering, the butterfly will fly around, flaps its wings or just sit quietly. If you click the butterfly when it’s not busy, it will react accordingly.

Messenger spinner
signinani If you click the About button, you’ll find the original Messenger signing in spinning animation in the top-left hand corner.


The MSN sound
Back in 1996, MSN had a sound they used for their advertising which accompanied the various letters of M-S-N. I was fairly fond of it, and I’ve included it in Reviver. Single-click the above mentioned spinner to initiate the sound and watch the letters light up.

There’s one more small addition, but I’ll let you find that one yourself 🙂

If you need help…
Please leave a comment here, visit the forum, the live chat, or contact me directly.

Concise version history (full history)

Mar 20 2017 2.4.8.47
  • Support for Windows 10 15063
  • Includes support for Windows 10 update KB4013198 15086.839
  • Includes support for Windows 10 update KB4013429 14393.953
  • Includes support for Windows 10 update KB4012606 10240.17319
  • Includes support for Windows 10 15048
May 10 2016 2.4.8.0
  • Support for Windows 10 14342
  • Starting to remove old 2009 code and user interface
Feb 12 2016 2.4.7.0
  • Patches Messenger to a new Messenger server host as the existing one was resulting in “can’t connect” (error 80072efd) messages in some locales
Jan 27 2016 2.4.6.3
  • Support for Windows 10 10586.71-10586.494
  • Support for Windows 10 14251
Oct 3 2015 2.4.5.4
  • Fix for Windows 10 Cumulative Update KB3093266 (was causing 8004882a/800488fe errors)
Aug 10 2015 2.4.5.0
  • Fix for Windows 10 32-bit versions
  • Support for Windows 10 10162
  • Better Windows 10 detection
  • Better handling of pending reboots
Jul 29 2015 2.4.4.0
  • Fix for Windows 10 (10240) and the 8004882a error, workaround no longer needed
Mar 21 2015 2.4.3.0
  • Fixes for installing Messenger 2012 on 64-bit Vista and full Windows Server 2008 support
Mar 17 2015 2.4.2.0
  • Windows Vista support for installing/reviving Windows Live Messenger 2012 and the other 2012 Essentials
Mar 12 2015 2.4.1.0
  • Automatically brings up upgrade window if you don’t have 2012 installed
  • Installation of versions other than 2012 is disabled by default
Dec 20 2014 2.4.0.0
  • Patches Windows Live Messenger 2011 to use the correct Messenger servers
  • Patches Windows Messenger (all versions) to use the correct Messenger servers
  • New support for Windows Messenger 4.7.3000 (Windows XP SP2) and Windows Messenger 5.1.0715
  • Bug when detecting if Live Messenger 2008 has been re-revived fixed
  • Automatically enables TLS support (as now required for Messenger) if it has been turned off
Dec 5 2014 2.3.5.0
  • Patches Windows Live Messenger 2008 and Windows Live Messenger 2009 to force them to use the correct Messenger servers
  • Fixed a bug when upgrading to Messenger 2012 on Windows Server when the .NET Framework 3.x isn’t installed
Nov 13 2014 2.3.0.0
  • Fixes both Windows Live Messenger 2008 and Windows Live Messenger 2009 (solves error code 85ae0010 sign in issue)
Apr 16 2014 2.2.5.0
  • Support for new Messenger 2012 16.4.3528.0331
Feb 19 2014 2.2.4.0
  • Support for new Messenger 2012 16.4.3522.0110
Sept 09 2013 2.2.3.0
  • Messenger 2011/2012 has been blocked from being installed on Windows 8.1 due to a compatibility problem with Windows 8.1 I’ve yet been able to fix.
    (This version has been withdrawn as Microsoft has fixed the error in update KB2903939)
May 13 2013 2.2.2.0
  • Support for new Messenger 2012 16.4.3508.0205
May 07 2013 2.2.1.0
  • Changes to the detection of Messenger to allow weird modified Program
    Files folder configurations on 64-bit Windows
  • Fixed a rare crash that would happen on new Messenger installs on XP
May 04 2013 2.2.0.0
  • Now scans all running applications for Messenger file in use
  • Also supports patching the file and rebooting for the change to take effect
  • Added some code to avoid broken Windows Installers
Apr 25 2013 2.1.0.0
  • Added support for Windows Live Messenger 2008 (8.5.1302.1018)
  • More aggressive in shutting down services that might hold on to the file, hopefully should resolve some of the “waiting” issues
Apr 25 2013 2.0.1.0
  • Changed how XP clients work as Reviver was trying to patch Windows Messenger and required advanced settings to install Live Messenger again, it should now be automatic on XP
Apr 24 2013 2.0.0.1
  • Switching the self-extractor to Microsoft’s iexpress to solve some issues, this should prevent the application from not exiting when it’s done its work and hopefully better with security software
Apr 23 2013 2.0.0.0
  • First release of Messenger Reviver 2

Installing Windows Live Mesh 2011 with Windows Essentials 2012

48_edit Yesterday Microsoft released Windows Essentials 2012 which among other things, removes Windows Live Mesh for SkyDrive (which is barely a comparable product).  But unlike the 2011 and 2009 versions of the Essentials, thankfully you can actually install Live Mesh on your existing 2012 installation.

To make this easy, I’ve written a small tool called Live Mesh Installer.Live Mesh Installer

Download Live Mesh Installer

Getting started with Live Mesh Installer

To get started, download the Live Mesh Installer, choose Run if possible or download and open the zip file yourself.  Next, just run the LiveMeshInstaller.exe inside the zip file and choose Yes when prompted for administrator rights.

Finally choose the language version you prefer from the list and then select the Begin button.  The Installer will then download the Windows Live Essentials 2011 web installer and automatically install Windows Live Mesh.  Please note that installation will take some time as it will need to download, extract and install Live Mesh.  When it is complete, Live Mesh will start automatically.

Options

If you prefer to see what’s happening with the installation, uncheck the ‘Hide installation wizard’ option before you begin.  When the Windows Live Essentials setup begins, you will be prompted to either install all the products or choose the ones you prefer.  Only Live Mesh will be installed on either option (unless you choose others specifically in the choose screen).

Final notes

Unfortunately as Windows Essentials 2012 is hardcoded to remove Live Mesh, any upgrades or changes you make to your Windows Essentials 2012 installation will result in Live Mesh being removed again.  If this happens, just re-run the tool and install it again.  Hopefully this won’t happen too often.

Version history
09/01/2012 1.1.1.0 Fixed Italian not showing in the list
08/19/2012 1.1.0.0 Added the remaining languages
08/08/2012 1.0.0.0 First release of Live Mesh Installer

How to disable Messenger (Messaging) in Outlook.com

Last week, Microsoft announced (yet another) rebrand of Hotmail to Outlook.com.  It has received plenty of favourable reviews and praise but one feature is extremely annoying – and that is, like the Windows 8 Metro Windows 8-style UI Messaging application, it automatically logs you into Messenger and connected services (Facebook Chat) when you sign in, with no ability to log off instant messaging except for setting your status to “invisible”.  (Side note: Windows 8 Messaging now thankfully has a global off switch added into its settings since the Release Preview.)

I’m sure there are people who don’t mind this – perhaps they don’t use instant messaging or they keep webmail open all the time anyway (in fact you get a small bonus feature if you do).  I personally use the actual Outlook desktop application and only use webmail when I’m away from my own PC, so I’m not too keen to be speaking of people when I’m just trying to quickly access my email from other locations.

So I looked for a way to disable this from happening and after rummaging through the options unsuccessfully, some searches to see if anyone else had already figured it out, I started looking through the code, and found the key: geo.messenger.services.live.com geo.gateway.messenger.live.com (changed December 2012).

So to disable Outlook.com’s Messaging feature, all one has to do is block this host and the easiest way to do this is to add it to your hosts file.  If you’re not sure how to do this or want to save time, I’ve made a quick tool for Windows users below which you can easily run to automatically add (or remove) blocking this host.  To make this change yourself manually, you find yourself on a machine without administrator rights, or you use another operating system, see Other Options below.

Download the Disable Outlook.com Messaging tool

Using the tool

To start, download the Disable Outlook.com Messaging tool, open the zip file, and run the application inside.  You’ll be prompted for administrator rights so the tool can make modifications to your hosts file, and then you’ll receive a message indicating the change has been made.  Please note you’ll need to restart your browser to see the change.

To remove the entry in the hosts file, run the tool again, the messenger entry will be removed and you’ll receive a message notifying you as such.

If required, you can use the /q command line parameter to avoid seeing the notification messages that the change has been added or removed.

After the change

Once the hosts file entry has been added, when you click Messaging in Outlook.com, you will see an attempt to sign in but it never will be successful.  With the new Messaging pane added in 2014, you will also need to collapse the Messaging pane by clicking on it:
Clicking the Messaging pane to collapse it

Other options

If you wish to add the entry to the hosts file yourself and use Windows, press the Start button (if you use Windows XP, click the Run option) and type:

notepad %systemroot%\system32\drivers\etc\hosts

then press Ctrl-Shift-Enter to start Notepad with administrator rights.  Once Notepad starts, add the following line:

0.0.0.0 geo.gateway.messenger.live.com

Then close Notepad and save.  Now just restart your browser to see the change.

If you’re on a Windows machine without the ability to get administrator rights, such as a work setup or library and there is an available version of Internet Explorer available, commenter qiang reminded me that you can use the Restricted Sites zone to block specific hosts like this one.  To do so, after starting Internet Explorer, press the Alt key on the keyboard to bring up the menu bar, choose Tools, then Internet Options, then the Security tab, choose Restricted sites and finally press the Sites button.  In the ‘Add this website to the zone:’ box, type geo.gateway.messenger.live.com and choose Add.  Then click Close, and OK in the remaining open options windows.  If outlook.com is already open, sign out outlook.com and sign back in to see the change.

If you’re using another operating system, the How-To Geek has tutorials for both Ubuntu Linux and OS X (the Windows one is missing the fact you need to start Notepad in Administrator mode if you’re following this guide).

Additionally, you could use firewall software to block outgoing connects to this hosts.  Unfortunately the built-in Windows firewall only supports IP addresses and since these can change, it isn’t too useful for the purposes of blocking this.

Final notes

As modifying the hosts file requires administrator rights, this probably won’t be successful on machines you might use when you’re out and about.  Of course, the best solution would be for Microsoft to add this feature into Outlook.com itself and in fact, the web messenger in Hotmail initially didn’t allow you to log out either but the feature was added later on.  I certainly have no idea why is was deemed unimportant to be included in the current release of Outlook.com and it seems many of you agree with me.

Use Messenger Reviver to bypass the Windows Live Messenger 2009 forced upgrade

UPDATE (4/23/2013): Use Messenger Reviver 2 instead to bypass the forced upgrade to Skype.

Microsoft today started forcing upgrades to Windows Live Messenger 2011 on Windows 7.  Unfortunately the 2011 version drops several key features, adds several annoying features, and is not that impressive of an upgrade.  Certainly many just prefer to use Live Messenger 2009 and now you can (again).

You will receive one of the following messages if you’re being forced to upgrade:
A newer version is available.  You must install the newer version in order to continue.  Would you like to do this now?
A newer version has been downloaded and is available.  You must install this newer version in order to continue.  Would you like to do this now?

updateforced

To bypass the forced upgrade for Windows Live Messenger 2009, download my Messenger Reviver utility below, open the MessengerReviver.exe file contained within the zip file and click Start.  Messenger should automatically exit and then restart normally.  You should then be allowed to sign in again.

MessengerReviver

Download Messenger Reviver

Replaced by Messenger Reviver 2

Note that Messenger Reviver requires administrative rights and you will be prompted to authorize if you have UAC engaged.

Requirements
Windows XP, Windows Vista, Windows 7 (any edition of these)
.NET Framework 2.0 or higher (already included with Windows Vista and Windows 7)
Windows Live Messenger 2009 14.0.8089.726 or 14.0.8117.416

Frequently asked questions
Does it work with other modifications to Messenger?
Yes, Messenger Reviver will not remove any changes you’ve made to Messenger. However, if you use such a tool later, you may need to re-run the reviver afterwards.

I am receiving a “Updating Messenger failed” message, how can I fix this?
Although Reviver does several checks and offers solutions to some obvious problems, if Messenger has been heavily modified by other tools, it may not be possible to apply Messenger Reviver.  Instead, you may need to repair your Messenger files.  Assuming you are using the last version of Messenger 2009, click Start, then Run, enter the following and click OK:
msiexec /fa {B57EAFF2-D6EE-4C6C-9175-ED9F17BFC1BC}

After the Windows Installer completes its work, try using Messenger Reviver again.

A different solution
If you encounter additional problems or don’t like the idea of someone else tweaking with Messenger, another solution to getting signed in again is setting the Windows Live Messenger shortcut into Windows XP compatibility mode.  To do this, locate the Windows Live Messenger shortcut on the start menu, right-click the shortcut, choose Properties, then choose the Compatibility tab, choose Windows XP (Service Pack 3) and then click OK.  If Messenger is already running, restart it and you should now be able to sign in.  Unfortunately by using this compatibility solution, Messenger will change its behaviour as it would operate under Windows XP (for example, a notification area icon with status instead of in the taskbar, and so on).  Additionally, some features in Messenger may not work properly since it assumes you’re on Windows XP (for example, Remote Assistance).  Messenger Reviver does not have these limitations and I don’t personally recommend using the compatibility technique if you don’t have to.

Version history
06/19/2012 1.2.0.0 First release of Messenger Reviver (this is version 1.2 as it is based on the original Link Reviver code)

Messenger Link Reviver for Windows Live Messenger 2009

Recently, Microsoft disabled web links in Windows Live Messenger 2009 citing it to be a temporary measure to a malicious worm.  Therefore links now appear as just text and need to be copy/pasted to your browser manually.  One can debate the effectiveness of this action as Messenger already had the ability to simply not deliver links meeting a certain criteria, but it seems they’ve given up on this original functionality and now rely on the SmartScreen link redirector exclusively in Windows Live Messenger 2011.

Windows Live Messenger 2011 isn’t for everyone though.  You’re certainly out of luck if you use Windows XP, Messenger Plus Live, or want to use features missing in 2011 such as handwriting or webcam.

So for those who wish to use Windows Live Messenger 2009 and still have the ability to click on links, I give you Messenger Link Reviver.

How to use Messenger Link Reviver

Update 6/20/2012: Messenger Link Reviver has been replaced with Messenger Reviver.  Please use this instead.
Download the Messenger Link Reviver zip file
and run the application.  Click Start to apply the Reviver changes and Messenger will automatically restart.  You should now be able to click on links again.

Note that you’ll be prompted to elevate to administrator permissions if you’re using Windows Vista or Windows 7 with UAC on.

Requirements
Windows XP, Windows Vista, Windows 7 (any edition of these)
.NET Framework 2.0 or higher (already included with Windows Vista and Windows 7)
Windows Live Messenger 2009 14.0.8089.726 or 14.0.8117.416

Frequently asked questions
Does it work with modifiers to Messenger?
Yes, Messenger Link Reviver will not remove any changes you’ve made to Messenger.  However, if you use a tool which does so, you may need to re-run the reviver after making any changes.

I get a “.NET Framework Initialization Error” or “The application failed to initialize properly (0xc0000135). Click on OK to terminate the application” when I run Messenger link Reviver.
You’ll need to install at least the 2.0 .NET Framework on your machine.

Version history
01/14/2011  1.1.0.0 Allows continued sign in after CVR (forced) update
11/21/2010  1.0.0.0  Initial release

Just a quick note that Spaces will be shutting down soon, so this blog will be moving.  More on where you’ll be able to find the blog later.

The blog has now moved and as such, new advertising has appeared.  If you see a download link or image below this line, it is not the download link for Link Reviver.  The download link is above.

Solving Messenger install, reinstall and uninstall issues with ZapMessenger

For users of Windows Live Messenger 2011 and 2012:
Please note that ZapMessenger 1.0 is not compatible with Windows Live Messenger (or Essentials) 2011 or 2012.  No damage will result if you have tried to do use the utility, but due to a substantial change in how Messenger installs itself, ZapMessenger will not work.  An updated version is almost ready, but I am looking for testers who can directly report back on if it was successful in solving their problem.  If you’re interested in helping out, please leave a comment below!

A regular issue faced is the dreaded “Another version of the product is already installed”, “Your computer has a newer version of MSN Messenger than the one you are trying to install”, ““Your computer has a newer version of Windows Live Messenger than the one you are trying to install”, “The feature you are trying to use is on a network resource that is unavailable” and similar messages.

Additionally, in some cases the installer can’t be found in the Control Panel’s Programs applet or has become damaged with a  Catastrophic failure (0x8000ffff) error or the Windows Installer is prompting for a missing .msi file which you can’t find anymore.

There are fixes for all these problems, but they’re complicated and can be frustrating to some people.

The fix
With all this in mind, I developed ZapMessenger – the one step tool to completely remove Windows Live Messenger, MSN Messenger and Windows Messenger 5.x.  The first thing ZapMessenger will do is attempt to cleanly uninstall Messenger normally and if that fails for any reason, it will forcibly remove Messenger from the Windows Installer engine allowing you to reinstall at your leisure without hindrance.

How to use
To use ZapMessenger, just download the zip and run the executable.  No installation is required.   Please note that the .NET Framework 2.0 or above is required, which you can install from Microsoft if you don’t already have it.  The Framework has been on Windows Update for quite some time and is included in Vista by default, so more than likely it is already installed.

Common questions
Will this remove any of my personal customizations – emoticons, display pictures, etc.?
No, currently ZapMessenger deals with the application itself – your personal data will remain and won’t be touched.  I am considering adding this an option to future releases for those looking to do a complete “clean” install.

I get a “.NET Framework Initialization Error” or “The application failed to initialize properly (0xc0000135). Click on OK to terminate the application” when I run ZapMessenger
You’ll need to install at least the 2.0 .NET Framework on your machine.

Version history
11/19/2008  1.0.0.0 Initial release