Windows 7: Live Mail won't open...references bad calendar data?

Alright so I'm using the 2011 version of Live Mail and all has been well since install... But now an old problem I saw with the older version is rearing its ugly head again: the program will begin to load, but after a while i get the message that Live Mail can't open because of corrupted data in my calendar (don't remember the specific message or error code here at the office), and of course i've never used its calendar. Sometimes a reboot helps, others not at all.

From googling i see this is not a new problem, but I also don't see a definitive cause or solution. Has anyone else had success making this go away?

Seems to be a corrupted registry entry. There are some suggestions here. Windows Live Mail Could Not Be Started. Calendar contains corrupt data. Error 0x80070057

Ken J

It's interesting that both people with the problem in that thread were running Windows in Parallels on a Mac.

...yes i'm not doing anything in parallel with Mac or anything else. Just the standard, vanilla installation.

You can repair the vanilla installation of Windows Live Essentials either from "Programs and Features" or by rerunning the original file you downloaded from Microsoft "wlsetup-web.exe". Just uncheck the new stuff and the old (Mail) will be listed at the bottom for repair. Be careful not to download the current version unless you are ready to upgrade to the 2011 version (with the ribbon).

Yep...already tried the repair functions also...

I also have this problem and cannot fix it. Unsure if its related to me resently moving my user files to another disk (used advise from these forums on doing this). If I delete the registry key for windows live mail for local user my mail opens. Then when I close it and open it again it wont work again.

Have posted on the windows live support forums but got no reply as yet, please help!

Had the exact same issue and SOLVED IT. You need to download and install the latest Intel storage drivers....its extremely weird that the two would be related. You can get the drivers here: http://downloadcenter.intel.com/Deta...adType=Drivers

Yes, extremely so. It's possible the fix happened coincidentally with the driver install.