Annoyances.org
Home » Windows XP Discussion Forum » Message 1069718987 Search | Help | Home
  
Tip: Run a free scan for common Windows errors ad

re: msmsgs.exe
Monday, November 24, 2003 at 4:09 pm
Windows XP Annoyances Discussion Forum
Posted by ALL The info u need (1 messages posted)


http://www.theregister.co.uk/content/4/24708.html Nuking MS Messenger By Thomas C Greene in Washington Posted: 04/04/2002 at 13:44 GMT 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. ?


On Friday, August 1, 2003 at 2:51 am, Dave wrote:
>How do I stop Windows Messenger from loading to run in the background each time I
>start Windows XP? If I use Task Manager to end the (msmsgs.exe) process, it comes
>right back in a few moments.


Written in response to:
msmsgs.exe (Dave: Friday, August 1, 2003 at 2:51 am)

Responses to this message:
*re: msmsgs.exe (Mike: Tuesday, December 2, 2003 at 9:30 pm)

All messages in this thread [show all]
-msmsgs.exe (Dave: Fri, Aug 1, 2003, 2:51 am)
-re: msmsgs.exe (Bob Cerelli: Fri, Aug 1, 2003, 3:10 am)
-re: msmsgs.exe (Dave: Fri, Aug 1, 2003, 4:47 am)
*re: msmsgs.exe (Xenon: Wed, Apr 5, 2006, 1:28 pm)
*re: msmsgs.exe (Sarbajit De: Tue, Dec 12, 2006, 11:43 pm)
-re: msmsgs.exe (Mike Stepansky: Thu, Sep 18, 2003, 4:56 pm)
*re: msmsgs.exe (keith twombley: Sun, Mar 7, 2004, 12:41 pm)
-re: msmsgs.exe Port 1900 (DDK: Sat, Sep 20, 2003, 4:44 am)
*re: msmsgs.exe Port 1900 (Mete: Fri, Oct 31, 2003, 10:32 am)
*re: msmsgs.exe Port 1900 (Jeruvy: Wed, Dec 31, 2003, 5:57 am)
*re: msmsgs.exe Port 1900 (TAWNY: Tue, Jan 13, 2004, 8:02 am)
*re: msmsgs.exe Port 1900 (BOLO: Tue, May 25, 2004, 3:00 am)
-re: msmsgs.exe (Barbara: Fri, Jan 9, 2004, 5:36 am)
-re: msmsgs.exe (robert tan: Mon, Jan 12, 2004, 5:49 am)
-re: msmsgs.exe (Barbara: Mon, Jan 12, 2004, 8:44 am)
-re: msmsgs.exe (Craig: Thu, Feb 5, 2004, 6:54 am)
*re: msmsgs.exe (Niklas: Tue, Feb 10, 2004, 2:11 pm)
-re: msmsgs.exe (Mike: Fri, Jun 25, 2004, 8:47 pm)
-re: msmsgs.exe (Pantera: Sat, Jun 26, 2004, 10:07 am)
-re: msmsgs.exe (hohner: Sat, Jun 26, 2004, 11:15 pm)
*re: msmsgs.exe (Bob: Sun, Jun 27, 2004, 5:48 am)
*re: msmsgs.exe (Bob: Sat, Jun 26, 2004, 10:46 am)
-re: msmsgs.exe (Barbara: Mon, Jan 12, 2004, 9:05 am)
*re: msmsgs.exe (Ed: Sat, Jan 17, 2004, 10:47 pm)
-re: msmsgs.exe (martin: Sun, Jan 18, 2004, 11:28 am)
*re: msmsgs.exe (Barbara: Mon, Jan 19, 2004, 4:39 am)
*re: msmsgs.exe (martin: Mon, Jan 19, 2004, 9:42 am)
-re: msmsgs.exe (TAPE: Mon, Jan 24, 2005, 1:03 pm)
*re: msmsgs.exe (woosoobi: Sat, Feb 12, 2005, 1:29 am)
-re: msmsgs.exe (hohner: Fri, Apr 16, 2004, 10:41 pm)
-re: msmsgs.exe (mikey: Fri, May 21, 2004, 8:11 am)
*re: msmsgs.exe (hohner: Fri, May 21, 2004, 9:01 pm)
-re: msmsgs.exe (Hylen: Sun, Jul 4, 2004, 11:47 am)
*re: msmsgs.exe (Hylen: Sun, Jul 4, 2004, 12:27 pm)
*re: msmsgs.exe (Daniel Brockman: Wed, Feb 11, 2004, 12:22 pm)
*re: msmsgs.exe (VICTOR: Wed, Apr 7, 2004, 4:32 pm)
*re: msmsgs.exe Simple Reply (Matt: Tue, Aug 3, 2004, 6:12 am)
-re: msmsgs.exe (Jeff Harrison: Thu, Aug 5, 2004, 8:44 am)
*re: msmsgs.exe (hohner: Thu, Aug 5, 2004, 5:26 pm)
-re: msmsgs.exe (john milner: Wed, Feb 16, 2005, 1:10 pm)
*re: msmsgs.exe (Falcon: Wed, Feb 16, 2005, 1:14 pm)
*re: msmsgs.exe (Jeff: Fri, Aug 1, 2003, 5:11 am)
-re: msmsgs.exe (Adam Bradley: Fri, Aug 1, 2003, 6:15 am)
-re: msmsgs.exe (Ron: Tue, Aug 12, 2003, 8:18 pm)
-re: msmsgs and firewall (Ammo: Thu, Aug 21, 2003, 9:53 am)
*re: msmsgs and firewall (JOse: Tue, Sep 9, 2003, 7:39 am)
-re: msmsgs.exe (icewings: Sun, Jan 25, 2004, 11:26 pm)
*re: msmsgs.exe (Cam: Fri, Feb 6, 2004, 2:57 am)
-re: msmsgs.exe (Rick Leton: Sat, Aug 16, 2003, 12:03 am)
-re: msmsgs.exe (Dave: Sat, Aug 16, 2003, 4:23 am)
-re: msmsgs.exe (internet user: Fri, Sep 12, 2003, 9:03 pm)
*re: msmsgs.exe (Dylan: Wed, Jul 7, 2004, 6:19 pm)
-re: msmsgs.exe (Tone: Mon, Aug 18, 2003, 5:46 pm)
-re: msmsgs.exe (mark: Tue, Aug 19, 2003, 9:13 am)
-How to disable msmsgs.exe (bbb: Thu, Aug 21, 2003, 2:30 pm)
-re: How to disable msmsgs.exe (bbb: Thu, Aug 21, 2003, 2:41 pm)
*re: How to disable msmsgs.exe (Janet: Fri, Jan 30, 2004, 5:38 pm)
*re: How to disable msmsgs.exe (Holli Would: Fri, Aug 4, 2006, 12:26 pm)
*re: How to disable msmsgs.exe (Nitrox: Thu, Nov 16, 2006, 9:35 am)
*re: How to disable msmsgs.exe (budwiizer: Sun, Aug 31, 2003, 11:53 am)
-re: How to disable msmsgs.exe (username: Tue, Sep 9, 2003, 8:50 am)
*re: How to disable msmsgs.exe (a01hjd: Tue, Oct 21, 2003, 11:01 am)
*re: msmsgs.exe (methegrate: Thu, Aug 21, 2003, 1:34 am)
-re: msmsgs.exe - this was the fix!! (fuol: Fri, Oct 3, 2003, 8:45 pm)
-re: msmsgs.exe - this REALLY was the fix!! (Gastric: Tue, Oct 28, 2003, 7:10 am)
-re: msmsgs.exe - this REALLY was the fix!! (BillFinkRI: Tue, Dec 16, 2003, 9:57 pm)
*re: msmsgs.exe - this REALLY was the fix!! (wb: Sun, Dec 28, 2003, 10:41 pm)
*re: msmsgs.exe (carlos: Thu, Oct 16, 2003, 2:49 pm)
*re: msmsgs.exe (Paul: Fri, Nov 7, 2003, 5:39 pm)
*re: msmsgs.exe (Yonatan: Wed, Dec 31, 2003, 4:19 am)
-re: msmsgs.exe (Anon: Sat, Jan 3, 2004, 4:58 am)
*re: msmsgs.exe (ezywoo: Sun, Jan 18, 2004, 4:43 pm)
*re: msmsgs.exe (Raphael: Fri, Jan 23, 2004, 3:38 pm)
*re: msmsgs.exe (Garry: Tue, Feb 3, 2004, 10:40 am)
-re: msmsgs.exe (sciserg: Wed, Jul 7, 2004, 7:48 pm)
-re: msmsgs.exe (bgreen: Sun, Dec 12, 2004, 9:54 pm)
*re: msmsgs.exe (Hillel: Thu, Dec 23, 2004, 1:50 pm)
*re: msmsgs.exe (Texas: Sat, Jan 22, 2005, 2:31 pm)
*Ever resuscitating msmsgs.exe process finally killed (Latice: Thu, Jul 13, 2006, 7:19 am)
*re: msmsgs.exe (Ratznium: Thu, May 10, 2007, 10:21 pm)
-re: msmsgs.exe (Nazir: Tue, Aug 19, 2003, 7:04 am)
*re: msmsgs.exe (donganos: Fri, Dec 26, 2003, 1:05 pm)
-re: msmsgs.exe (RZ150XM: Tue, Sep 2, 2003, 6:11 am)
-re: msmsgs.exe (checkon: Wed, Sep 3, 2003, 9:05 pm)
-re: msmsgs.exe (Jyothi: Wed, Sep 10, 2003, 9:42 pm)
*re: msmsgs.exe (Elwood: Wed, Feb 1, 2006, 5:51 pm)
-re: msmsgs.exe and Outlook (John Welch: Thu, Sep 11, 2003, 12:33 pm)
-re: msmsgs.exe and Outlook (john: Thu, Sep 11, 2003, 4:18 pm)
-re: msmsgs.exe and Outlook (Mr A.: Fri, Sep 12, 2003, 1:34 pm)
-re: msmsgs.exe and Outlook (Martin: Tue, Sep 16, 2003, 6:10 am)
*re: msmsgs.exe and Outlook (Ashok: Tue, Jul 13, 2004, 4:45 pm)
*re: msmsgs.exe and Outlook (Darek: Mon, Jan 5, 2004, 9:37 am)
*re: msmsgs.exe and Outlook (hohner: Fri, Apr 16, 2004, 10:01 pm)
*re: msmsgs.exe and Outlook... without your permission! (Toni: Sun, Jun 13, 2004, 10:03 am)
*re: msmsgs.exe and Outlook (Scott: Sat, Nov 15, 2003, 9:59 pm)
*re: msmsgs.exe and Outlook (Diana103172: Wed, Jun 29, 2005, 2:48 pm)
*re: msmsgs.exe (Mark: Fri, Oct 10, 2003, 4:15 am)
-re: msmsgs.exe (Karl Kemerait: Fri, Oct 31, 2003, 7:52 am)
*re: msmsgs.exe (Ron: Sun, Apr 18, 2004, 12:16 am)
*re: msmsgs.exe (Bryan: Sun, Jun 13, 2004, 10:36 pm)
*re: msmsgs.exe (mario: Sun, Nov 2, 2003, 10:02 am)
-re: msmsgs.exe (anon: Sun, Nov 2, 2003, 12:17 pm)
*re: msmsgs.exe (trailmeister: Tue, Jan 16, 2007, 12:48 am)
*re: msmsgs.exe (Webwoef: Tue, Nov 4, 2003, 2:12 am)
*re: msmsgs.exe (Andy Radtke: Tue, Nov 4, 2003, 10:49 am)
-re: msmsgs.exe (ALL The info u need: Mon, Nov 24, 2003, 4:09 pm)
-re: msmsgs.exe (Mike: Tue, Dec 2, 2003, 9:30 pm)
*re: msmsgs.exe (dougal83: Sun, Aug 15, 2004, 6:42 am)
*re: msmsgs.exe (steve crouch: Tue, Jan 6, 2004, 11:25 pm)
*re: msmsgs.exe (Jose Morales: Tue, Jan 13, 2004, 11:24 pm)
-re: msmsgs.exe (Rono: Fri, Jan 30, 2004, 9:56 pm)
-re: msmsgs.exe (Stephen Foong: Tue, Feb 10, 2004, 1:41 pm)
-re: msmsgs.exe (Rono: Wed, Feb 11, 2004, 1:44 pm)
*re: msmsgs.exe (Stephen Foong: Sun, Feb 22, 2004, 7:11 am)
*re: msmsgs.exe (Ignatius: Wed, Feb 11, 2004, 1:33 pm)
*re: msmsgs.exe (XManUK: Mon, Apr 5, 2004, 11:47 am)
-re: msmsgs.exe (myardor: Sat, Apr 10, 2004, 1:17 am)
*re: msmsgs.exe (Linguisticsprof: Wed, Sep 8, 2004, 9:01 pm)
*re: msmsgs.exe (Craig: Tue, Apr 27, 2004, 8:48 am)
-re: msmsgs.exe (Robert: Sat, May 8, 2004, 10:53 pm)
*re: msmsgs.exe (al: Mon, Oct 11, 2004, 7:49 pm)
-re: msmsgs.exe (copied from microsoft website) (Onionfx: Mon, May 10, 2004, 2:47 am)
*re: msmsgs.exe (copied from microsoft website) (oldtree: Mon, May 10, 2004, 3:00 am)
*re: msmsgs.exe (Christopher: Thu, May 27, 2004, 4:38 pm)
-re: msmsgs.exe (Raylene: Mon, May 31, 2004, 7:48 pm)
-re: msmsgs.exe (Jim P: Wed, Jun 2, 2004, 12:49 pm)
*re: msmsgs.exe (Jim P: Wed, Jun 2, 2004, 12:58 pm)
-re: msmsgs.exe (hohner: Wed, Jun 2, 2004, 8:17 pm)
-re: msmsgs.exe (rocket: Fri, Jun 11, 2004, 3:10 am)
-re: msmsgs.exe (hohner: Fri, Jun 11, 2004, 5:57 pm)
*re: msmsgs.exe (croaker: Fri, Dec 24, 2004, 10:15 am)
-re: msmsgs.exe (Karl Kemerait: Mon, Jun 14, 2004, 6:20 am)
-re: msmsgs.exe (HouseMuzikLvr: Tue, Jun 29, 2004, 7:08 am)
*re: msmsgs.exe (Paul: Sat, Jul 3, 2004, 12:05 pm)
-re: msmsgs.exe (samal: Tue, Jun 15, 2004, 4:38 am)
*re: msmsgs.exe (sawman: Sun, Jun 27, 2004, 4:22 pm)
-re: msmsgs.exe (Lan Fisher: Sat, Oct 23, 2004, 4:15 am)
*re: msmsgs.exe (unfilthy: Wed, Oct 27, 2004, 4:37 pm)
*re: msmsgs.exe (Bernard Clark: Sat, Dec 11, 2004, 12:37 pm)
-re: msmsgs.exe (David: Tue, Feb 15, 2005, 4:03 pm)
-re: msmsgs.exe (takchi: Fri, Feb 25, 2005, 7:34 pm)
*re: msmsgs.exe (El Jamón Misterioso: Sat, Mar 5, 2005, 6:47 am)
*re: msmsgs.exe (tiplex: Mon, Apr 18, 2005, 6:10 pm)
*re: msmsgs.exe (vic: Mon, Jul 31, 2006, 8:22 am)
*re: msmsgs.exe (onehayes: Thu, Nov 10, 2005, 2:39 am)
-re: msmsgs.exe (Craig: Thu, Dec 7, 2006, 10:04 pm)
*re: msmsgs.exe (Simon: Tue, Jan 2, 2007, 5:35 am)
-re: msmsgs.exe (BC: Sat, Jan 20, 2007, 6:24 pm)
-re: msmsgs.exe (Karl Rudnick: Sun, Apr 15, 2007, 1:41 pm)
*re: msmsgs.exe (Tez: Wed, Jul 11, 2007, 12:18 am)
Return to the Windows XP Discussion Forum


All content at Annoyances.org is Copyright ©1995-2012 Creative Elementtm All rights reserved.
Please do not plagiarize; redistributing these pages without permission is strictly prohibited.