Hello guys,
my eMule is set to start with Windows and I have also added it to the Startup program menu.
Monitoring the processes on startup, I can see it starts and dies right after that.
I try to enable logging, but nothing shows up.
I have restored permissions on the folder and reinstalled.
If I start it manually, it works just fine.
I found no issues related to that on the forum (sorry if I missed any)
Can any of you help me with that troubleshoot?
Thanks in advance.
Page 1 of 1
Emule Not Starting With Windows 10
#2
Posted 12 December 2018 - 01:04 PM
LOL
just found the problem....
I had eMule running as administrator by default.
And seems in one of those Windows updates, started causing it to not start with Windows. Most probably those AV updates .... not sure.
I just went to compatibility tab of the emule.exe and unchecked the option to run as administrator.
It is starting with Windows on start up again.
Regards!
just found the problem....
I had eMule running as administrator by default.
And seems in one of those Windows updates, started causing it to not start with Windows. Most probably those AV updates .... not sure.
I just went to compatibility tab of the emule.exe and unchecked the option to run as administrator.
It is starting with Windows on start up again.
Regards!
#3
Posted 13 December 2018 - 11:05 PM
Congratulations, and thanks for posting the solution.
An application can run As administrator if it was launched by a process with already elevated permissions, or explicit user's confirmation was recieved (impossible at Windows start-up). If none of the conditions were true, the application should not run.
If eMule was running previously, then the latest security updates should have fixed this vulnerability.
An application can run As administrator if it was launched by a process with already elevated permissions, or explicit user's confirmation was recieved (impossible at Windows start-up). If none of the conditions were true, the application should not run.
If eMule was running previously, then the latest security updates should have fixed this vulnerability.
This post has been edited by fox88: 13 December 2018 - 11:06 PM
#4
Posted 03 January 2019 - 11:09 PM
I had the same problem. For me, I just had to go to Connections and check to Autoconnect at Startup. Not sure why it got unchecked during the recent reinstall I had to do.
Page 1 of 1