Windows Shuts down soooo slowly...

I have 1 user currently having a major issue when trying to shut down. He doesn't shut down often, as he is using the BlackBerry Redirector to send new eamils from his Outlook to his handheld. We don't have Exchange yet. So when he does decide to close down his computer, it takes several minutes to close down, which is not acceptable.

I tried uninstalling the BlackBerry stuff first, still was very slow closing down. Installed and ran Fix-It Utilities to run a diagnostic and Regisrty Fixer. The diagnostic did not turn up anything worth noting. The Registry Fixer came up with about 100 issues that required fixing or deleting. Let it do its thing and ran it again. This time it yielded 32 or so items to be fixed or deleted. Ran it a third time, got about the same results. Ran it 2 more times before all seemed happy. Shut down ran like a charm then, closeing in less than 20 seconds.

So we tried to simulate what would happen normally but without the Redirector. The machine ran all weekend long. Tried to shut down first thing this morning, and it took forever to do so. So it's not the redirector. Next I checked the Event Logs and found the following in the App Log:

Event Type: Error

Event Source: ESENT

Event Category: Logging/Recovery

Event ID: 494

Date: 9/16/2005

Time: 11:31:03 AM

User: N/A

Computer: HEALTHED2

Description:

wuauclt (3480) Database recovery failed with error -1216 because it encountered references to a database, 'C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb', which is no longer present. The database was not brought to a consistent state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, please contact PSS for further instructions regarding the steps required in order to allow recovery to proceed without this database.



For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.





Event Type: Error

Event Source: ESENT

Event Category: Logging/Recovery

Event ID: 454

Date: 9/16/2005

Time: 11:31:03 AM

User: N/A

Computer: HEALTHED2

Description:

wuauclt (3432) Database recovery/restore failed with unexpected error -1216.



For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



Event Type: Information

Event Source: ESENT

Event Category: General

Event ID: 101

Date: 9/16/2005

Time: 11:31:03 AM

User: N/A

Computer: HEALTHED2

Description:

wuauclt (3432) The database engine stopped.



For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



Event Type: Information

Event Source: ESENT

Event Category: General

Event ID: 100

Date: 9/16/2005

Time: 11:31:03 AM

User: N/A

Computer: HEALTHED2

Description:

wuauclt (3480) The database engine 5.01.2600.2180 started.



For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information

Event Source: ESENT

Event Category: General

Event ID: 102

Date: 9/16/2005

Time: 11:31:03 AM

User: N/A

Computer: HEALTHED2

Description:

wuaueng.dll (3480) SUS20ClientDataStore: The database engine started a new instance (0).



For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



Event Type: Information

Event Source: ESENT

Event Category: Logging/Recovery

Event ID: 300

Date: 9/16/2005

Time: 11:31:03 AM

User: N/A

Computer: HEALTHED2

Description:

wuaueng.dll (3480) SUS20ClientDataStore: The database engine is initiating recovery steps.



For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



Event Type: Information

Event Source: ESENT

Event Category: Logging/Recovery

Event ID: 301

Date: 9/16/2005

Time: 11:31:03 AM

User: N/A

Computer: HEALTHED2

Description:

wuaueng.dll (3480) SUS20ClientDataStore: The database engine has begun replaying logfile C:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb.log.



For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



I am not sure if this is the issue or not, but since it reoccurs a lot in the App Log, I figured it was where I shoudl start next in this mystery. From what I have found in Google, it says that this is normally an Exchange issue. But this is just a workstation running WIndows XP SP 2.

Any ideas, or at least some direction to point in?

Thanks for any help y'all offer.

Travis