Zebra22


I have been using Windows Live Messenger for months and today I clicked on the livecall button option. I closed the livecall window and never made any changes but now whenever I open Live Messenger it automatically loads the livecall.exe process which stays resident and uses 17-18MB of ram. This process is just a resource hog as I don't use the service at all and can find no way to set Live Messenger to not load this process upon startup. Can anyone tell me how to tell live messenger to not load this process on startup anymore I am using Windows Live Messenger version 8.1.0178.00 on XPSP2.



Re: Livecall.exe backgound process

Rhavin


Folks, there have been 2 posts about this issue, and no replies. I too am looking for information on this.

Anyone out there got an answer to this

Thanks.






Re: Livecall.exe backgound process

BrEeZiE

same here, i never use the livecall.exe but it keeps on loading when I run windows live messenger





Re: Livecall.exe backgound process

BrEeZiE

I found a solution:
Put the following files from your messenger directory in a backup directory:
htc.8.1.0178.00.dll
livecall.exe
pcsexeps.dll
softphone.dll
softphoneps.dll
softphoneres.dll

then WLM won't load the livecall anymore




Re: Livecall.exe backgound process

Rhavin

Breezie,

I tried what you suggested, but it does not work.

The reason is that when you start up Messenger again, the installer runs and repairs the missing files. So when you check the directory again, all the files you said to move to a backup folder, are there again. So there must be some other file/files that it is using to put new copies back.

Thanks.





Re: Livecall.exe backgound process

ferchon03

It seems to work fine with me.

Thank you BrEeZiE.




Re: Livecall.exe backgound process

NaCl

Here's how I fixed this issue. Open regedit or another registry editor and browse to HKEY_CLASSES_ROOT\Installer\Products . Go down through the list of products until you find the key for WLM. Mine was 0F007175D9BDA3B40BD3531AB45B39F9 . Right click on the key and choose export to save a copy of the key and then , delete the key and rename livecall.exe. Now, when you open WLM, MS installer won't attempt to repair your installation.

If you want to uninstall/update WLM, you'll have to merge the key back in the registry. (might not be necessary for update)





Re: Livecall.exe backgound process

Ettore Mazza

You can just rename the file livecall.exe, but then (to avoid the restore process) you have to launch the file msnmsgr.exe and not the clsid link messenger installation creates.



Re: Livecall.exe backgound process

Hijax

I just renamed the file and then deleted it and things seem to work fine for me. Also I blocked the program from accessing the internet through my firewall(Norton)

Hope this helps





Re: Livecall.exe backgound process

KatanaBlade

To get rid of this pesky RAM-hog, the secret is:

1) move the livecall.exe, the softphone.dll's (x 3) and the pcsexeps.dll to a backup folder
2) disable the auto-startup option inside Messenger
3) create your own shortcut to msnmsgr.exe
4) add this to your Startup folder (in the Start/All Programs menu)

This will give you the same effect, in that MSN will still startup with windows, but the difference is that you will be calling msnmsgr.exe directly, instead of calling the full Messenger startup routines, which force the program to check that all the 'proper' files are in place and performs a repair if any are missing - meaning that the files you moved will be recreated!

I had the same problems as you guys above, but doing it this way does work!

Good luck!




Re: Livecall.exe backgound process

msaddict

I think that there's an even simpler solution.

I've been using WLM 8.0 for quite a while now, but it was only recently that I discovered this livecall.exe process appearing in the task manager.

In fact it was only recently that I decided to click the little phone icon just out of curiosity. After looking around for a way to prevent it from starting up, I simply just reinstalled WLM. Now livecall.exe doesn't start up at all. Therefore it seems to start from the first time you click the phone icon within WLM (I'm guessing that those of you who have this problem have at one stage started Live Call from within WLM - if not, my solution probably wont work).

If you don't use Live Call, I recommend reinstalling WLM (all your settings should remain intact) and just don't click on the phone icon - simple.

Worked for me!





Re: Livecall.exe backgound process

MarkyB71

Rename or delete the livecall.exe and create a new shortcut to the msnmsgr.exe. This stops the install when you run messenger.




Re: Livecall.exe backgound process

Da-SCSII

Hi,

I had the same problems listed in this thread. (Windows XP SP2)

I believe I have found the answer to this problem. It is all in having the UPnP Framework disabled in your router and have a check mark next to it under Windows Firewall, Exceptions.

Do not have any Windows Live Messenger open, if you were able to get it open.


The procedure I recommend is as follows; open your router in your browser (http://192.168.0.1 or whatever your router location is) and go to (mine happens to be a D-link router) the "Tools" tab than to "Miscellaneous" button on the left and you will see the setting "UPNP Settings" click on the "Disabled" radio button, if needed, and click on "Apply". You can then exit your router.

Then open your "Control Panel" click on "Windows Firewall" and click on the tab "Exceptions" you should see there under "Programs and Services" the name "UPnP Framework" this needs to have a check mark next to it. Click OK.

To verify that this has worked go to the following web page; http://www.microsoft.com/technet/sysinternals/utilities/TcpView.mspx and download (at the bottom of the page) and install "TCPView for Windows v2.4". Start the software and it will show you all of your internet connections.

Then start "Windows Live Messenger" and you will see it start in the TCPView, and then "livecall.exe" will start. Then close Windows Live Messenger, and restart it again, and you will see that "livecall.exe" did not start but Windows Live Messenger works fine.

This eliminates the memory usage, and with your router setting as "Disabled" it protects you.

If you have read the other possible fixes to this problem, you may have read where one person recommended to open a hole bunch of ports. I recommend you do NOT do that. If you have, close them.





Re: Livecall.exe backgound process

Andrew Levicki

Hi guys, I have read all the solutions offered and they all seem far too complicated.

I have a simple solution, it is this:

Solution:

1. Close Windows Live Messenger.

2. Terminate the livecall.exe process in Task Manager.

3. Open the %programfiles%\MSN Messenger folder.

4. Right-click livecall.exe and select properties.

5. Go to the Security tab.

6. Click Advanced.

7. Unselect Inherit permissions...

8. Click "Copy" when it asks Copy or remove.

9. Remove all users except SYSTEM.

10. Set SYSTEM's permissions to Read and Write, but crucially, NOT Execute.

When you run MSN Messenger in future, it can check that livecall.exe is there, but can not run it.

Enjoy.





Re: Livecall.exe backgound process

Bud Herzog

I, too, would love to find a way to NUKE that livecall.exe process in my task window. At first, I thought it was a Trojan that I got that would hijack my modem and make $1,000 calls to Bermuda; but, alas, it's just Bill Gates trying to make my life more efficient.

How do I get rid of this thing

Bud Herzog