On 1/18/2018 12:04 PM, Zaidy036 wrote:
On 1/18/2018 2:14 PM, David E. Ross wrote:
On 1/18/2018 9:22 AM, pyotr filipivich wrote:

Okay, one for de schmart guys.

Every so often, say once or twice a week, Mailwasher.exe hangs up
at the splash screen. Just, sits there.
I've right clicked on the taskbar icon and chosen "exit", clicked
on the red x to close the window. Used Task Manager and Process
Hacker, separately, and sequentially, to attempt to kill the process.
No luck.I've logged out or selected "Restart" as the shutdown option,
and windows has hung up on the "logging out" screen. Normally a
reboot takes long enough I can go warm up a cup of coffee on the
stove, sometimes make a fresh pot. But in this case, I have time to
brew a Fresh Cup from scratch. As in go to Columbia, pick the beans
myself, dry, roast, and grind them. I'm assuming that, I haven't
waited two weeks, I just kill the power when I get back from getting
coffee.

Because until it is dead, I can't start it again.

What I am wondering is, is there a way to determine what
services/modules/handles one might be able to track, hunt down and
terminate, unload, kill, in order to closed down the process, process
tree, or whatever is holding the splashscreen / program open?

I've attempted to close modules through Process Hacker, as well as
terminate specific threads, but no change.

Is this a new "feature" I'm just going to have to live with?

tschus
pyotr


Try the following, but I do not know if this will indeed work.

1. Using Task Manager, determine the exact, complete name of the
Mailwasher process.

2. Using Notepad, create a new file named kill_Mailwasher.bat.

3. Edit kill_Mailwasher.bat to contain the single line:
C:\Windows\System32\taskkill.exe /IM xxx
where "xxx" is the complete name of the process from step #1.

4. Copy the file kill_Mailwasher.bat and paste it as a shortcut (not
the file itself) on your desktop, in your Start menu, or in some toolbar.

The next time this problem arises, double-click on the shortcut to
execute the .bat file.

requires /T /F: C:\Windows\System32\taskkill.exe /IM xxx /T /F

xxx must be full name ***exactly*** as shown in TaskManager


Aha! I was working from a .bat file that terminates a process for an
application that has no Exit capability. Yes, the /T /F are required if
Task Manager itself will not successfully terminate the process.

--
David E. Ross
http://www.rossde.com/

President Trump: Please stop using Twitter. We need
to hear your voice and see you talking. We need to know
when your message is really your own and not your attorney's.