Vista - Strange Windows Live Mail Error

Build 12.0.1606

Started it up and got this error:

"WLM could not be started. The application was unable to open the WLM message store. Your WLM mailbox data is currently being used by another program, such as a virus scanner. Close the program or wait for it to complete its operation, then open WLM again."

followed by:

"Windows Live Mail could not be started because msmail.dll could not be initialized. Windows Live Mail may not be installed correctly."

After a little googling I tried logging off and on and it's working again??

I guess AV must have temporarily locked it somehow. First time I've encountered this in a year of use and with the same AV program in that period.

Kevin

There is a shut-down bug in WLMail 12.0.1606 that may be the cause of your problem, whereby wlmail.exe remains resident after exiting WLMail, and requires termination [End Process] through Windows Task Manager. It generally occurs when the send option "Upload Larger Images to the Web When Sending a Photo E-mail" is *un-checked*, but it does not usually manifest until a new compose window, or a saved draft has been opened.

This option is available only when you are signed in, but if it is un-checked it still causes the shutdown bug even when not signed in.

So make sure the option "Upload Larger Images to the Web When Sending a Photo E-mail" is *checked* at: Tools->Options->Send [tab] (available only when signed into Windows Live through WLMail).

However, if you do find that "Upload Larger Images to the Web When Sending a Photo E-mail" is actually checked (which it is by default), then just uncheck it and click "Apply", then check it again and click "Apply" again. Some have had to do that to fix their WLMail shut down bug that was occurring despite that option having never been unchecked.

--
Cheers,
Peter
(Windows Vista Home Premium SP1 with Windows Live Mail 14.0.5027.0908)
"There are more things in Heaven and earth, Horatio, than are dreamt of in your philosophy." - Shakespeare
---------------

"NewWorldMan" <kevin@xxxxxx> wrote in message newsB156372-73A5-450D-9C11-B55307E41B64@xxxxxx

This occurred for me straight after boot-up.

"Peter.R" <Peter.R@xxxxxx> wrote in message
news:711E0C40-CB39-4A6D-A79A-D572E92004C2@xxxxxx