Windows Mail uses 100% CPU?

  • Thread starter Thread starter James Bailey
  • Start date Start date
J

James Bailey

When I first start Windows Mail, it'll sit at close to 100% CPU and spin for
up to 30 minutes before stopping on its own. During this time, other
programs are able to run and WinMail functions just fine. Anyone have an
idea?
 
under Advanced Options, set the compact count to 1.
close WM. answer yes to Compact.
when it is done, open WM and set the count back to 100 or what ever you desire.
see if that made a difference.
I have found that 100 is WAY to high a number.



(e-mail address removed)



When I first start Windows Mail, it'll sit at close to 100% CPU and spin for
up to 30 minutes before stopping on its own. During this time, other
programs are able to run and WinMail functions just fine. Anyone have an
idea?
 
I have it set to 5 right now. It doesn't matter if I compact the store as it happens all the time.

----
James Bailey





under Advanced Options, set the compact count to 1.
close WM. answer yes to Compact.
when it is done, open WM and set the count back to 100 or what ever you desire.
see if that made a difference.
I have found that 100 is WAY to high a number.



(e-mail address removed)



When I first start Windows Mail, it'll sit at close to 100% CPU and spin for
up to 30 minutes before stopping on its own. During this time, other
programs are able to run and WinMail functions just fine. Anyone have an
idea?
 
is your virus program set to scan email.
if so turn that off and try it again.



(e-mail address removed)



I have it set to 5 right now. It doesn't matter if I compact the store as it happens all the time.

----
James Bailey





under Advanced Options, set the compact count to 1.
close WM. answer yes to Compact.
when it is done, open WM and set the count back to 100 or what ever you desire.
see if that made a difference.
I have found that 100 is WAY to high a number.



(e-mail address removed)



When I first start Windows Mail, it'll sit at close to 100% CPU and spin for
up to 30 minutes before stopping on its own. During this time, other
programs are able to run and WinMail functions just fine. Anyone have an
idea?
 
No virus scanner installed; only Windows Defender.

----
James Bailey





is your virus program set to scan email.
if so turn that off and try it again.



(e-mail address removed)



I have it set to 5 right now. It doesn't matter if I compact the store as it happens all the time.

----
James Bailey





under Advanced Options, set the compact count to 1.
close WM. answer yes to Compact.
when it is done, open WM and set the count back to 100 or what ever you desire.
see if that made a difference.
I have found that 100 is WAY to high a number.



(e-mail address removed)



When I first start Windows Mail, it'll sit at close to 100% CPU and spin for
up to 30 minutes before stopping on its own. During this time, other
programs are able to run and WinMail functions just fine. Anyone have an
idea?
 
my cpu usage go up when WM first loads. how long it stays up varies on the size of the data base and its compact status. but has never stayed high for more than couple of minutes at most.




(e-mail address removed)



No virus scanner installed; only Windows Defender.

----
James Bailey





is your virus program set to scan email.
if so turn that off and try it again.



(e-mail address removed)



I have it set to 5 right now. It doesn't matter if I compact the store as it happens all the time.

----
James Bailey





under Advanced Options, set the compact count to 1.
close WM. answer yes to Compact.
when it is done, open WM and set the count back to 100 or what ever you desire.
see if that made a difference.
I have found that 100 is WAY to high a number.



(e-mail address removed)



When I first start Windows Mail, it'll sit at close to 100% CPU and spin for
up to 30 minutes before stopping on its own. During this time, other
programs are able to run and WinMail functions just fine. Anyone have an
idea?
 
Hi, James;

30 minutes? Ouch. I don't know that I would have had that much patience.
:)

As Mikey intimates, there is most likely something wrong in the data files
that WinMail uses. Which is complicated, having both a massive database
file and then all those individual .EML and .NWS files.

First guess/step would be to create a new folder named C:\WinStore on your
Vista drive. Then go into WinMail, run through the Options to the
Advanced/Store Folder section and change that to reflect the C:\WinStore
folder you just created. Then close WinMail, count slowly to 100 (it may be
doing compaction in the background) and when you see the disk activity light
go out restart WinMail.

Your WinMail stores will now be in the new folder you created. Work with
that for a few days while it gets indexed and normalized. But hopefully you
will not see a 30 minute startup again after moving to the new folder.

BTW, if that does not help, post back. Be sure to include your computer
specs, as Vista is known to be lethargic on older/slower/RAM-limited
systems.

--

....Sky

Tom "Sky" King
===========

In
 
You can check event viewer and ESENT activity that is related to WinMail to
see if there are errors.

Its programmed to backup the database every 24 hours, so that might be what
its doing when it starts. Be mindful that Vista has all kinds of stuff
going on in the background, such as defender, so it may not be WinMail that
is the culprit. Check Task manager and the processes to see if its really a
WinMail issue.

steve
 
Task Manager shows WinMail as the culprit. Looking at the ESENT log
entries, I see a lot of recovery steps going on:

WinMail (4088) WindowsMail0: The database engine is initiating recovery
steps.
WinMail (4088) WindowsMail0: The database engine has begun replaying logfile
C:\..\Windows Mail\edb.log.
WinMail (4088) WindowsMail0: The database engine has successfully completed
recovery steps.

I shut it down normally, so I don't know why this would come up so often.
 
Okay, try repairing the database. This seems to be helping some.


Open a command prompt using Run as Administrator.

Then copy this line, edit the path to the messasge store, and then hit
enter:

esentutl /p "path\windowsmail.msmessagestore"


Where path is default %USERPROFILE%\AppData\Local\Microsoft\Windows Mail

so the default would be:

esentutl /p "%USERPROFILE%\AppData\Local\Microsoft\Windows
Mail\windowsmail.msmessagestore"

Copy and paste that and then edit it to fill in the variable %USERPROFILE%

steve
 
Then I'd wipe out the database and start over again. Save your eml files
and delete everything else and see if it behaves itself after that. You can
actually probably just wipe out the database files and leave the rest and
that might fix it. See www.oehelp.com/backup.aspx for info on the files.

steve
 
Back
Top