Mailwasher Pro 7.12.173 Closes after Opening

[gingbat]

Yes, sorry about this all, hardware issue on our end causing unexpected results in MWPro, please disable Firstalert:

(when MW starts, click Stop, to stop the mail check first)

Settings>>Spam Tools>>Firstalert, uncheck, "Use Firstalert" and click Save.

If no better, disable any servers listed under Settings>>Spam Tools>>Origin of Spam, click Save.

If you cannot start MW long enough to disable it, please try what's recommended here:

viewtopic.php?f=50&t=58383#p167431

Should fix it for now, it'll be fixed early next week....

[ucon]

I uninstalled Mailwasher Pro 7.12.173 and installed Mailwasher Pro 7.12.125. Mailwasher Pro 7.12.125 seems to work OK. v119 also works. Mailwasher Pro previous versions can be found here:

https://www.firetrust.com/products/mail ... change-log

If your browser complains the download is not secure, download it anyway. (Firetrust should have secure downloads for previous versions)

My guess is Firetrust will be releasing a new version to fix this bug, but I can't wait around for that. I use Mailwasher Pro every day, multiple times a day, and depend on it to filter out bad emails - which it excels at.

[kevlarheart]

Add me to the list. Once calendar moved to September MWP will begin d/l mail then disappear. Program won't stay open long enough to access support. Please patch y'all, this is a real nuisance.

[Larebear]

Same problem here. Mailwasher Pro crashes after opening with Windows 11 Pro O.S.

Tried uninstalling and reinstalling v7.12.173 with no success. Still crashed.

Went back to the previous version 7.12.125 and it's working again.

[OrdinaryJoe]

Im having the same problem. (Crashes after opening. Doesnt even download the emails from the server )

I did this and it seems to have worked...........

"NOTE: if you cannot do the above because MW crashes before you can stop the mail check, try this.....

Go to Start, type run (then click the Run file so it runs) then in the ‘Open:’ box type (or copy / paste):

%AppData%\Firetrust\MailWasher

Rename the current "SpamToolSettings.xml" file to "SpamToolSettingsOLD.xml" (or remove it).

Then move the attached one into the same folder.

Start MWpro."

[gingbat]

viewtopic.php?f=50&t=58384&start=45#p167512

[dydxdx]

The following works for me..........

I uninstalled Mailwasher Pro 7.12.173 and installed Mailwasher Pro 7.12.125. Mailwasher Pro 7.12.125 seems to work OK. v119 also works. Mailwasher Pro previous versions can be found here:

https://www.firetrust.com/products/mail ... change-log

If your browser complains the download is not secure, download it anyway. (Firetrust should have secure downloads for previous versions)

My guess is Firetrust will be releasing a new version to fix this bug, but I can't wait around for that. I use Mailwasher Pro every day, multiple times a day, and depend on it to filter out bad emails - which it excels at.

[krissully]

I also reinstalled the previous version. Quick and easy and it works. Could not wait and the two solutions offered did not work for me. Thanks for the tip.

[iamjaydear]

UPDATE 1... I started my computer this morning to revert to xxx.125 and noticed the MWP icon spinning in the task bar! Totally bizarre. I tried restarting it several times (including restarting Win11) last night with no luck, and here it is working like it had never misbehaved. Good Fathers' Day prezzie Anyway I'll leave it alone, do backups jic and see what transpires this week.

[higgsie]

I am having the same issue where MailWasher crashes and creates a dump file, in the crash logs it states the following DLL "MWPappDLL.dll" as causing the exception.
I've looked at my daily PC backups and can see this DLL was changed in the new release as the new file is smaller.

As stated in the thread the only approach that works for me is to revert back to the previous release "7_12_125", I don't wasn't to disable any of my rules or firstalert as these were created for a reason.

Thanks

[emmrecs]

Removing the latest version and reinstalling .125 worked for me also.

[johnnysaint]

Was having the problems as described but, without trying to implement a fix myself, everything seems back to normal when switched on PC this morning.

[krissully]

So is it SAFE to upgrade again? Reverted to 7.12.125. Need assurances.

[ucon]

If 7.12.125 is working for you, you should NOT upgrade to v7.12.173. Cancel out of the prompts to upgrade. You will find yourself in the same situation again. Wait for Firetrust to release a New version that fixes this bug.

[krissully]

Thank you SO much.