VanguardLH on Thu, 1 Feb 2018 14:53:38 -0600 typed in
alt.windows7.general the following:
pyotr filipivich wrote:

Built the batchfile:

Echo "should kill a stuck mailwasher"
Echo "good bye world"

C:\Windows\System32\taskkill.exe /IM "C:\Program Files
(x86)\FireTrust\MailWasher\MailWasher.exe" /F /T

C:\Windows\System32\taskkill.exe /IM "mailwasher.exe *32" /T /F

echo "done"
EOF

Should have put a pause at the end "Next time"

The first invocation - makes with the "access denied" message. I
really wasn't expecting much.

taskkill.exe requires admin privileges. Either you define a shortcut to
run the .bat file and configure the shortcut with elevated privileges or
you disable UAC. I do the former with my shortcuts so I can leave UAC
enabled.
Ah, I see you methodology.

Batch files are not shortcuts. Shortcuts let you configure them to run
the target program with elevated privileges. Else, you have to load a
command shell (cmd.exe) *with elevated privileges* and then run the .bat
file inside that command shell.

Could try that.

You could add a pause at the end of the .bat file but you can also look
in Task Manager as a check that the process is absent. Before running
the .bat file, use Task Manager to verify the mailwasher.exe process is
actually present. No point in trying to kill a process that doesn't
exist because you think that's the faulting process. After running the
.bat file, use Task Manager again if you want to verify mailwasher.exe
is absent.

I add Pause at the end, so that any messages, flags, froo-froo
will be there when I look. (I have one batch file change the colors
of the screen so I can tell at a glance "I'm done" without having to
read the fine print.)

Oh, by the way, the " *32" is *NOT part of the process name* so you
entered the wrong process name to the taskkill command.

Okay, I had some confusion. Being told to enter the process as in
Taskmanager - it seemed that was what it was.
Now I know. All I need no is for mailwasher to break again.

[snpp]

Is mailwasher.exe the ONLY process used by Mailwasher?

As far as I can tell.

More snippage.

Mailwasher sometimes hangs at the splash screen. Is there an option to
not show a splash screen (to advertize themself)? Since a splash screen
is showing, likely you have Mailwasher loading as a startup program.
Well, disable it loading on Windows startup or upon login, [re]start
Windows, login, and then yourself load Mailwasher. Try that for awhile
to see if the freeze goes away.

Is Mailwasher loading as a startup program? If so, by what means does
it get loaded?

Shortcut on the taskbar, which runs the program

"C:\Program Files (x86)\FireTrust\MailWasher\MailWasher.exe"



Could be you have a
conflict with Mailwasher loading when some other startup program loads.

That's my guess.

You could try disabling all startup programs leaving only Mailwasher to
load on Windows startup and user login.

What happens, as near as I can figure, is that I start the
computer, login to MyLogin, and hit the shortcut "too early" after
logging in, - before Windows has it's morning coffee and gotten its
brains fully functional. My usual morning procedure is start the
computer, have my own coffee, feed the cats, and then login. Once it
is through wearing out the drive heads, then I will start mailwasher
from the taskbar, and palemoon.
Some times "when I start too soon", mailwasher hangs up at the
spashscreen, and palemoon acts funky. The solution to both seems to
be a reboot, but I have to kill mailwasher else Windows gets stuck
waiting to log out.

But as I said, I usually start it from the taskbar after he
browser, or a wait. I'll have to get impatient and will then try the
shortcut rout on the Kill_Mailwasher batch file.

thanks for the advice information.

tschus
pyotr
--
pyotr filipivich
Next month's Panel: Graft - Boon or blessing?