eM Client doesn't restart after being closed

I’m Running eMClient version 7 under Windows 10. Since few days (and may be installation of both latest updates of eM Client and windows 10), eM Client doesn’t restart after being closed in the same windows session. No error message, just nothing. I always have to sign out and reopen a windows session to get eM Client working again … until I close the program. I guess there is an error message posted somewhere, but I can’t find it. Any idea ?

Hi Noel.

Check in your Windows Task Manager, under Background Processes. There may be an instance of eM Client running. If you manually close that, then the application will start normally.

It may be that you are using an older version of eM Client, where there were known issues with closing the application. If you are not using the latest version, you can download and install it from http://www.emclient.com/release-history.

Hi Gary,Thanks for this quick reply. Indeed, I found eM Client task running in the backround and got eM Client restarted after having close this one. Tactical solution working fine. Thanks again.
But I checked that the version I’m using is the latest one 7.1.33101.0, just released, and it could be that the the reported problem pop up with this recent update (july 12 - official release date). Known issues on closing are may be back ?

I have not seen this problem in a while on my computer, but I suppose it is possible that a specific set of circumstances may cause it to reappear. If you have a Pro License, you could open a support ticket. I am sure your log files will help with solving the problem.

I have this issue lately:  eM does not restart after being closed and then re-run soon thereafter. The process runs, but no window appears. I then have to kill the process, restart the client, and wait a long time for the database check to finish.

Operating system           : Microsoft Windows 7 Professional 
OS version                 : 6.1.7601
Service pack major version : 1
Service pack minor version : 0
Free physical memory       : 5574544
Total physical memory      : 17052119040
PC manufacturer            : TOSHIBA
PC model                   : PORTEGE R930
CPU                        : Intel64 Family 6 Model 58 Stepping 9
OS bitness                 : 64
CPU bitness                : 64
BIOS manufacturer          : TOSHIBA
BIOS name                  : Default System BIOS
BIOS version               : Version 6.80  
Motherboard manufacturer   : TOSHIBA
Motherboard product        : PORTEGE R930
Motherboard version        : Version A0
Display                    : Intel(R) HD Graphics 4000
Display width              : 1680
Display height             : 1050
DPI                        : 120

Yes, closing the application abnormally, like terminating it, will automatically invoke the database check on start.

I was trying to find a thread on this forum where Jay mentioned something about this, but can’t find it now. I think he mentioned something about the anti-virus application. If this is happening regularly, try disabling your anti-virus application before you close eM Client and see if there is any difference. Don’t know what you would do about it if there is, but it will be interesting.

Another thing is that sometimes after the initial setup there is a lot of syncing going on, and that prevents eM Client from closing normally. Maybe see if the application is not stuck in a sync loop before terminating it.

I can try these things. The developer should investigate what happens when the program is closed normally and then quickly restarted.

Did you check in Taskmanager if and when eMC  (MailClient.exe) has left the processes list and how long it took to do this?..
Also - the program has loaded much more than MailClient.exe, which is only
the tip of the iceberg…

BTW - This is not unusual for certain applications.
Restarting them while they’re still shutting down causes a conflict and neither one
can run through its course.

Yes, OK, probably the user’s fault, but I wonder if there is a way for eM to trap the issue so that it does not occur.

What can I say?
It’s not probably, but definitely the user’s fault for not taking into account what the characteristics are of the program…

Like I wrote, certain programs load  slower and linger on shutdown.
Don’t single out eMC - even Windows processes can do this.
You must also have these problems with e.g Photoshop or Video editors or games and many more…

It’s up to the user to take this into account once they know how the program reacts
and  adapt to it.

Are you doing this for testing purposes? because it doesn’t make sense for regular use.
In normal situations you minimize the app - not close it.
If this is your regular way of working, you may want to vary it…
because you may be too “trigger-happy”…
Anyway, do as you like…

Mind you - the speed with which a program starts or stops and unloads 
depends on many things - performance specs of the computer to start with
AV programs tend to hold on to processes and other elements as do Windows processes for whatever purposes.

if  you’re not happy with my answer, contact eM Client directly.

I don’t disagree. Just wondering if the program can prevent the problem from occurring, but it sounds like it cannot. Thank you. 

Hi, Thanks for the feedback.

You’re not totally off the mark tho…

I’ve come across some very clever true freeware programs that have the feature you are looking for.
Clever, because the programmer took the time to implement those features.

Unfortunately, this is not the norm, often not even by large companies…

it goes like this - Suppose you terminate a program, but it is slow to shutdown for whatever reason - 
Now you want to restart it. Rather than trying to start- causing a conflict and fail.
a notice or warning comes up that the program cannot be started because the full shutdown has not been completed -  a simple OK button to acknowledge.

The program may not start on its own after that, nor do you get a notice that it has  completely shut down. But that could also be programmed or it keeps the start command in memory and will start up when it can.
meaning,  it monitors the shutdown waiting for an inactive state and then the start command gets executed.

In programming the sky is the limit - anything you want can be programmed,

The question is now whether or not the programmer or team sees the benefit
versus time and expense…

So a lot of things never see the light of day…

So you see - I don’t disagree with you either - despite my statements in the previous post 
it’s just the way things are from a practical standpoint…


Sure, makes sense. Would be an easy fix, I think: just create a launcher that checks for MailClient.exe; if already running, then set a recurring timer to check it again soon, or provide an alert, etc. A lot of programs have separate launchers like this that may do various things.

@echo off
SET appfn=MailClient.exe
REM --------------------------------------------
echo  888b     d888          d8b 888 
echo  8888b   d8888          Y8P 888 
echo  88888b.d88888              888 
echo  888Y88888P888  8888b.  888 888 
echo  888 Y888P 888     "88b 888 888 
echo  888  Y8P  888 .d888888 888 888 
echo  888   "   888 888  888 888 888 
echo  888       888 "Y888888 888 888 
REM --------------------------------------------
echo This file: %~0
%WINDIR%\System32\tasklist.exe /FI "IMAGENAME eq %appfn%" 2\>NUL | find /I "%appfn%"\>NUL
IF ERRORLEVEL 1 START "Mail" "%ProgramFiles(x86)%\eM Client\%appfn%" & EXIT
echo %appfn% is running. & TIMEOUT /T 5
GOTO :check

This problem, “eM Client was not closed correctly the last time”, is very frequent after closing and running the program. I get it about twice every week with the latest version.