Shoutbox

Is that possible? I just renamed livecall.exe to livecall.exe_ for now. It uses 20mb of my precious ram..

Go to start>run then type msconfig

Then go to the startup tab.

Then uncheck livecall.exe (might be somthing else, look at the path)

Click apply then restart.

If it says you have to be an admin and you are ignore it. If you not one it wont work.

If it was so easy, i would never ask here, because livecall.exe does not compare in the list. And if i terminate it from task manager, it starts itself after some time, but thanks for the suggestion

sorry, try the startup up folder?
If you just renamed it and its fine well i would just leave it.
I am looking for help now.
I can wright a program to stop this but it will take time
Good luck

No man, its neither in the startup folder, it starts only when WLM starts

Wohoo, thanks

well...
none of these worked for me...
i'vd renamed/moved/deleted those files , but install keeps restoring them and livecall.exe returns...
nothing either in the startup folder or msconfig ...
i searched many places and it seems this move/delete procedure the only thing that worked, at least for sum ppl... but no in here...
any idea what to do???

quote:

---

but install keeps restoring them and livecall.exe returns...
nothing either in the startup folder or msconfig ...

---

yes, onlny if you restart messenger. my pc is on 24/7 and so is my messenger. i don't shut it down and installer never comes out

The suggestions above won't work for most users, because most users have to restart either Messenger or their computers, occasionally.  If you delete/rename the registry key, Messenger throws an error when starting up.  If you delete/rename the file, the MSI repair puts it back.  So there's no winning either way.

To solve the problem, use the Group Policy editor (gpedit.msc) to create a Software Restriction Policy that Disallows the "C:\Program Files\MSN Messenger\livecall.exe" program in the Local Computer Policy.  That way, both the registry key for the MSI repair and the program files can exist, but livecall.exe simply isn't allowed to execute.

You can use the same method to disallow other pesky programs that are pernicious enough to re-assert themselves in spite of your best efforts to delete/rename them.

I really wish that Microsoft would make LiveCall an option that could be toggled on or off.  That would've been the polite/smart thing to do...