An unknown error has occurred. MailWasher is unable to determine the cause of this error.

[OssianF]

Same problem here. On two PC´s. Both with latest updates of Win 11 and MailWasher Pro.

[paultt]

I can not afford to change my system date back - I hate to think of what that will do to my daily scheduled backups, etc!

[keiths]

Yup - same here. Eventally got 'database is corrupted' message. Uninstalled, leaving settings as is, then reinstalled 7_12_125. All now working.

Like a previous poster I fail to understand what connction to FireTrust central is needed in order to make connection to my mail servers. I understand the need for subscription verification, but this smells of more than that.

[Elektra]

I changed the system date back and it worked however, when opening Outlook my license had been invalidated. It remained that way after returning the date to current but recovered after a reboot.

I'm no software programmer but I cannot see how a date can wreck a perfectly functioning program, unless those of us affected have been subjected to some kind of cyber attack? I say that because MW must have hundreds of thousands of users and yet only a handful are here complaining the program no longer works.

[rosamundi]

I changed the system date back and it worked however, when opening Outlook my license had been invalidated. It remained that way after returning the date to current but recovered after a reboot.

I'm no software programmer but I cannot see how a date can wreck a perfectly functioning program, unless those of us affected have been subjected to some kind of cyber attack? I say that because MW must have hundreds of thousands of users and yet only a handful are here complaining the program no longer works.

I doubt it's a cyberattack on specific users. It's more likely that people aren't registered for the support forum. I've been using Mailwasher pro for years and I've only just registered because I've never had problems with the software before, so I've never needed to ask for help.

[peak4]

Same problem with me in UK, changing PC time back to 11th also cures it.
I can then check mail, but changing time back to 12th and the program crashes.
Bill

[atiamplan]

I am only came here because I was suffering from the same issue. After reading that downgrading to v7.12.119 cures the problem, I tried the same thing and can report that MailWasher works as expected after downgrading to v7.12.119.

Hopefully it won't take too long for the bug to be fixed. I expect that there will be many users reporting this issue, so I suspect that the developer might receive a somewhat abrupt awakening this morning.

I'd like to know the actual cause of the problem and why it wasn't picked up during bug testing.

[atiamplan]

I'm no software programmer but I cannot see how a date can wreck a perfectly functioning program, unless those of us affected have been subjected to some kind of cyber attack? I say that because MW must have hundreds of thousands of users and yet only a handful are here complaining the program no longer works.

I'm old enough to remember the panic that the Y2K bug caused and with good reason too, as it did actually affect some computers.

https://en.wikipedia.org/wiki/Year_2000_problem

[trevor the worker]

I am only came here because I was suffering from the same issue. After reading that downgrading to v7.12.119 cures the problem, I tried the same thing and can report that MailWasher works as expected after downgrading to v7.12.119.

Hopefully it won't take too long for the bug to be fixed. I expect that there will be many users reporting this issue, so I suspect that the developer might receive a somewhat abrupt awakening this morning.

I'd like to know the actual cause of the problem and why it wasn't picked up during bug testing.

How did you perform the downgrading?

Did you uninstall from Control Panel > Programs > Programs and Features > MailWasherPro

and then reinstall from something like C:\ProgramData\Firetrust\updates\Update712119\mailwasher_pro_setup_7_12_119.exe

or is more required to preserve the Settings?

[wildlife~horizons]

Same problem here. I turned the pc on this afternoon to be greeted with the same error.
My wife's laptop is using version 7.12.97 and it is unaffected unlike the 7.12.173 version I am using along with many others.
I have not decided to uninstall the current version and reinstall the old version as yet, but that may be my best solution.

[MWman]

I have the same problem here in the UK.
I'm certainly not going to turn the clock back as some users have done, that could cause more problems.
Hopefully the bug will be solved soon (fingers crossed).

[wildlife~horizons]

If you are familiar with Registry Editor, you can backup your account details from the registry. I have not tried restoring the accounts from there as yet, but that will be my quick path to get it back working, if all the data goes walk-about.

[general714]

If you are familiar with Registry Editor, you can backup your account details from the registry. I have not tried restoring the accounts from there as yet, but that will be my quick path to get it back working, if all the data goes walk-about.

Easier to simply export the data from the software directly then import back if needed...

[emmrecs]

Mailwasher Mobile (linked to my PW Pro account) has no problems!

[atiamplan]

How did you perform the downgrading?

Did you uninstall from Control Panel > Programs > Programs and Features > MailWasherPro

and then reinstall from something like C:\ProgramData\Firetrust\updates\Update712119\mailwasher_pro_setup_7_12_119.exe

or is more required to preserve the Settings?

The uninstaller asks if you want to keep user settings and data, so this is what I did before installing the previous version.

If you want to ensure you keep your settings, I personally backup the Firetrust folder in %APPDATA%. Open Windows file explorer, type %APPDATA% into the address bar at the top and press Enter - this should take you to the roaming appdata folder, containing the Firetrust folder that you should backup. When I do system reinstalls, I just make a backup of this folder and restore it on my new install - this has always worked for me.