2011 crash on startup

[Sidewinder]

Yea, I got prompted to add it after one of the crashes - I use Microsoft Security Essentials......

Did you do both?

[chbimun]

Have you changed the settings in your security software to designate both MWP .exe files as "Trusted"?

I don't get an opportunity to. It worked fine before, but as soon as it tried to upgrade to 2011 it started doing this. I reinstalled yet again, and this time didn't let it update (which crashes as well btw), now not even 1.0.35 works anymore.

[Sidewinder]

You should be able to go into your security software and change the settings without having to start MWP.

You may also have an issue with .NET 3.5 SP1 and need to do a repair.

[chbimun]

You should be able to go into your security software and change the settings without having to start MWP.

You may also have an issue with .NET 3.5 SP1 and need to do a repair.

I'm using .NET 4 and already ran a repair which didn't help the issue.

[Sidewinder]

You should be able to go into your security software and change the settings without having to start MWP.

You may also have an issue with .NET 3.5 SP1 and need to do a repair.

I'm using .NET 4 and already ran a repair which didn't help the issue.

.NET 4 is used only with a beta version that was posted for a few selected users related to specific issues. If you are using this version let us know.

If you are using the release version then it uses .NET 3.5 SP1 and you may have to run the repair for it. If you are using XP or Vista go the the Add/Remove Programs or Programs and Features, scroll down to .NET 3.5 SP1 and click on it and it should then offer you the option to Repair.

[chbimun]

I don't have 3.5 in my add/remove programs in Windows 7 (64bit). All I have is Microsoft .Net Framework 1.1, Microsoft .Net Framework 4 Client Profile, and Microsoft .Net Framework 4 Extended. It was updated to 4 in a Windows Update back in April.

[racker]

I don't have 3.5 in my add/remove programs in Windows 7 (64bit). All I have is Microsoft .Net Framework 1.1, Microsoft .Net Framework 4 Client Profile, and Microsoft .Net Framework 4 Extended. It was updated to 4 in a Windows Update back in April.

In this case I can certainly advise you to install the latest beta; this has proven to be quite stable and without any real issues. This beta is based on .NET 4.0 instead of 3.5; you can download it here: http://forum.firetrust.com/viewtopic.php?f=50&t=8894

[jschumann]

Dot Net 3.5 is listes under add/change Windows Components, not listed with regular programs. Usually there is an icon to the left to select Windows components.

Regards,
John

[chbimun]

I don't have 3.5 in my add/remove programs in Windows 7 (64bit). All I have is Microsoft .Net Framework 1.1, Microsoft .Net Framework 4 Client Profile, and Microsoft .Net Framework 4 Extended. It was updated to 4 in a Windows Update back in April.

In this case I can certainly advise you to install the latest beta; this has proven to be quite stable and without any real issues. This beta is based on .NET 4.0 instead of 3.5; you can download it here: http://forum.firetrust.com/viewtopic.php?f=50&t=8894

Unfortunately, even this didn't work. It immediately crashed as soon as it tried to run. Previously, I'd get as far as it attempting to authenticate my key before crashing. This is where the program consistently crashes. I can install 1.035 successfully and run it. I can do everything I can normally do with it, but the moment I input my key it crashes and every attempt to reload the program results in crashing at verifying the key.

This is what I get from the error log:

Code: Select all

12/31/2010 11:15:27 AM	Message: String was not recognized as a valid DateTime.
12/31/2010 11:15:27 AM	Stacktrace:    at MailWasherPro.ActivateKey.RegisterThread(Object o)
   at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

[rusticdog]

1.0.35 won't take a lifetime license key, which I assume this is.

If you rename C:\Users\<your username>\AppData\Roaming\Firetrust\MailWasher to something like MailWasherOld, will then the 1.0.53 (.NET4 version) run ?

[chbimun]

1.0.35 won't take a lifetime license key, which I assume this is.

Yes I upgraded to the lifetime just before this all started happening.

If you rename C:\Users\<your username>\AppData\Roaming\Firetrust\MailWasher to something like MailWasherOld, will then the 1.0.53 (.NET4 version) run ?

Tried it and nope, it still crashed immediately after I had it launch the application after installing it.
--

FINALLY, got it to work! Since you mentioned that the key didn't work on 1.0.35 and I didn't have an executable for 1.0.50, the only way for me to get the 1.0.50 was to install 1.0.35 and let it autoupdate whilst never inputting my key. I was getting some writing errors previously to a file in the C:\Config directory when doing this upgrade, but in installing 1.0.53 it actually manged to overwrite the irksome file or remove it, not sure which, but whatever it was, it allowed the 1.0.50 update from 1.0.35 to occur without any errors. Once it was at 1.0.50, I was able to input my key and now it runs as it should.

Thank you for all the help!

[keno]

I updated to 2011 and a lifetime licence yesterday and afterwards it crashed on start so I put an Acronis image back onto drive C: that was ten days old. This would have replaced every thing including registry etc but Mailwasher (now 2010) still crashed on start up.
Today 24 hours later it as all started to work OK so I can only presume that it was an error on the Firetrust server after the licence change that as now resolved it'self.