Feeds

Nuking MS Messenger

In spite of Billg

  • alert
  • submit to reddit

New hybrid storage solutions

We've been blessed with scores of memos from readers offering numerous tips for nuking Microsoft Messenger, since we reported that an update which MS is touting as 'critical' sneakily re-installs it.

First, if you're sure you'll never use it, you can take the flamethrower approach and delete the entire Messenger directory (C:\Program Files\Messenger). The problem here is that some future MS 'upgrade' may well re-create the directory for you. You know how helpful MS likes to be.

Next, you might try re-naming the executable, msmsgs.exe to, say, msmsgs.bak, and then re-creating the executable with a blank file. This might (or might not) trick upgrade packages into assuming that your irritating little Messenger is up to snuff.

Another method is to open Start/Run, and type in:
RunDll32 advpack.dll,LaunchINFSection %windir%\INF\msmsgs.inf,BLC.Remove

The following only applies to XP-Pro:

If you only want to stop it running and prefer to leave it on the machine in case you ever decide to use it, you can go to Start/Run and enter gpedit.msc. Then go to: Computer Configuration/Administrative Template/Windows Components/Windows Messenger/ "Do not allow Windows Messenger to be run" and choose "Enabled".

For XP Home Edition users, MS recommends the following rather complicated routine, which will persuade most users to delete the Messenger directory instead, we're sure. We quote:

1.. Start Registry Editor (Regedit.exe).

2.. Locate and click the following registry key:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft

3.. On the Edit menu, point to New, click Key, and then type Messenger for the name of the new registry key.

4.. Locate and click the following registry key:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Messenger

5.. On the On the Edit menu, point to New, click Key, and then type Client for the name of the new registry key.

6.. Locate and click the following registry key:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Messenger\Client

7.. On the Edit menu, point to New, click DWORD Value, and then type PreventRun for the name of the new DWORD value.

8.. Right-click the PreventRun value that you created, click Modify, type 1 in the Value data box, and then click OK.

And we'll note that you should always back-up your registry before hacking it, even with instructions from Redmond.

I haven't had a chance to thank everyone individually for their contributions, but believe me, if I missed you I'm nonetheless grateful for the effort, and El Reg's beloved readers will no doubt appreciate it just as much.

Hats off -- you know who you are. ®

Security for virtualized datacentres

More from The Register

next story
Not appy with your Chromebook? Well now it can run Android apps
Google offers beta of tricky OS-inside-OS tech
Greater dev access to iOS 8 will put us AT RISK from HACKERS
Knocking holes in Apple's walled garden could backfire, says securo-chap
NHS grows a NoSQL backbone and rips out its Oracle Spine
Open source? In the government? Ha ha! What, wait ...?
Google extends app refund window to two hours
You now have 120 minutes to finish that game instead of 15
Intel: Hey, enterprises, drop everything and DO HADOOP
Big Data analytics projected to run on more servers than any other app
New 'Cosmos' browser surfs the net by TXT alone
No data plan? No WiFi? No worries ... except sluggish download speed
prev story

Whitepapers

Providing a secure and efficient Helpdesk
A single remote control platform for user support is be key to providing an efficient helpdesk. Retain full control over the way in which screen and keystroke data is transmitted.
Top 5 reasons to deploy VMware with Tegile
Data demand and the rise of virtualization is challenging IT teams to deliver storage performance, scalability and capacity that can keep up, while maximizing efficiency.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
Secure remote control for conventional and virtual desktops
Balancing user privacy and privileged access, in accordance with compliance frameworks and legislation. Evaluating any potential remote control choice.