I have it running on my laptop and my phone - problem is the laptop always answers calls - unless it is switched off , which during the day it isn't. 

SOMEHOW the two line.exe and linecall.exe are being started without me starting the app - it's happening every reboot. I've searched all the startup settings and can't find it - I have to kill the processes - any ideas?

You don't mention your operating system but in Win 11 the first place I would look is Task Manager, Startup apps and disable from there.

ok thanks but been there done that got the t-shirt - nnoowhere to be found, maybe a hidded registry setting which I'm avoiding, I just use task Manager to kill the processese

Second option, again you may have already been there, is Settings, Apps, Startup and see if you can find them to toggle them off.

Thirdly try running shell:startup and delete any shortcuts for the apps.

On 6/8/2026 at 7:06 PM, nglodnig said:

I've searched all the startup settings and can't find it

Sorry if I have misunderstood but did you initially load Line and tick the 2 boxes under login details which say "Log me in Automatically" and "Start Line when Windows starts"?

I haven't ticked them and don't have the issue you describe.

9 minutes ago, topt said:

Sorry if I have misunderstood but did you initially load Line and tick the 2 boxes under login details which say "Log me in Automatically" and "Start Line when Windows starts"?

I haven't ticked them and don't have the issue you describe.

They were both unticked. For those interested, after checking (with the Ai from Chrome perhaps not the best advice 🙂) every possible startup option - now after reboot the two exes aren't started UNTIL run the Line App - then they hang around even after quitting Line and need to be killed - so problem solved in a way.

Edited June 13Jun 13 by nglodnig

29 minutes ago, nglodnig said:

then they hang around even after quitting Line and need to be killed - so problem solved in a way.

I found that a problem until I realised I had to hit the log out notification rather than just clicking the top right x and then they didn't hang around - YMMV

1 hour ago, topt said:

I found that a problem until I realised I had to hit the log out notification rather than just clicking the top right x and then they didn't hang around - YMMV

Thanks I'll try that.....