So I got me to look at a Windows Vista system that has been running for quite a long time. With just 1 (one) gigabyte of RAM.
At every operating system start, it would search for updates and the hard disk would thrash alot.
With Resource Monitor I discovered that the oft-accessed file was DataStore.edb, located at
The file is a log file in database format listing the history of all updates installed to the system, and also includes the current status of updates waiting to install.
Now, the typical solution[Yes, Citation needed] to this that I had been looking at on the interwebs has been to create a backup of this file and then delete it. After that, Windows Update won't list the history of all updates installed to the system, and that would be that. < Well, there's more than that :>
DataStore.edb, turn off the Windows Update service, because when that service is active, the DataStore file is in use.
For a short while I thought that defagmenting this one file with a command-line tool called
esentutlwould be the solution, so I wanted to go on with it. The catch was that the tool would not be able to copy the defragmented file to its original location and yielding an error about it, saying that the defragmented TEMP file could still manually be taken to its original location, with the original file replaced. I didn't do it and left it at that.
By the way, the
esentutltool does not list where the .TMP file is located. I eventually found out that it was at the main user data folder of a logged-in user:
For a long time I couldn't put my finger on what it was that was not working, and then a month or two later it turned out that I had not been running the
esentutlcommand in Administrator mode.
The full command for defragmenting the file went on like this:
esentutl /d %windir%\SoftwareDistribution\DataStore\DataStore.edb
So I launched Command Prompt as Administrator and the tool did its job as expected. So that was that.
But checking for updates in Windows Update took a lot of time anyway, and the hard disk still kept thrashing when checking for updates.
What happens when removing Note that you will still have to back up the file, just in case...
Well, Windows Update then knows no history of previous updates and takes a lot of time to check for them. Maybe an hour. Or so, because I assume it will check updates file-by-file for nearly all present Microsoft software. Before, when the still-large
datastore.edbfile was there, it seemed that the check for updates actually took much, much less time. Since I didn't measure the actual minutes and did not compare, then I can't tell with any reliable numbers as to what the effect was with regards to differences in update checking times.
Anyways, after installing the updates, DataStore.edb was recreated and sported about the same size as before (over 315 MB). So, there is really no point in deleting the file.
Worse is, that there doesn't seem to be any built-in way to merge two separate DataStore.edb files into one cohesive database, if the older database were absent for a short while and another one created anew.
Then I just moved the recently backed-up
datastore.edbback, and checking for updates in Windows Update took about ten minutes, including a reasonably minor database refresh on account of the May updates installed in the interim, which was not reflected there.
To avoid Windows Update thrashing the hard drive anyway, it's then best not to have the Windows Update service run with such a low RAM count at all (1 GB); perhaps with the exception of every second Tuesday each month.
So much for now.
I don't have that Vista computer at hand, or any other Vista computer in any useful proximity, so it's impossible to tell with precision where to optimize wrt Windows Update.
Point being that it's possible to keep Windows Update from checking updates at every startup by making changes in scheduling.
- I remember there being a scheduler snap-in module in Windows Management Console, which feature-wise in Windows Vista replaced the Scheduled Tasks folder in Windows xp. The Task Scheduler snap-in is alot more complex and allows very granular configuration options.
- Turning off automatic updates is useful for very experienced users. If the computer has behaved well, then I've usually set the Windows Update service to delayed start. Attempt this at your own risk. Even if the risk is low, it doesn't account for unintended behaviour, especially when making large updates, such as upgrades to Windows service packs.
I also hazily remember a separate update not advertised on Windows Update itself, that also must have improved the situation, if only a bit. The overall result was that the DataStore file was touched only when I launched the Windows Update program.