Have noticed lately after doing updating with AP, that the Windows update history and/or software will not work correctly.
Apparently it is having a issue with a possibly corrupt Softwaredistribution\datastore folder after the AP updates are completed. If you rerun the AP it shows all the updates unchecked and blue in color which I assume, means the updates are installed. But,if you then run the Windows Update program and either "Review your update history" or press the check for updates button, you will get a windows update error 0x80248011.
Numerous Google suggestions, say that one fix is to delete the datastore folder which in turns erases your windows update history files and lets it start from scratch. Thereafter, the Windows update program will function normally, checking for upates,etc. Woudl it be safe to assume that if the WU program is not working correctly, then it will not autoupdate as future updates become available from Microsoft.
On a clean install system w/WinXP sp2, Ran WU and it showed 95 or so critical updates to install. Ran AP April, installing nothing but Critical updates. Rebooted and re-ran WU. The scan for updates will start but soon times out, and gives the 0x80248011 error.
Tried fix nbr 1, to delete the internet cache files in IE . No, go ... on this one. So tried, fix nbr 2, which is as follows:
From Run (cmd) command prompt.
net stop wuauserv
cd /d c:\Windows\SoftwareDistribution
rd /s /q Datastore
net start wuauserv
exit
This apparently fixs the issue. But, you will show zero Windows Update history. And, it will now scan for updates, and show you any possible updates from Microsoft. Which now displays only a few critical updates to do... of which ie7 is one, and mediaplayer 9 updates, and a few that are recommend updates on Autopatcher.
Now the question. Is this being cause by AP somehow? And, on a side note, if machines are being turned out to the general public then you might want to try Windows Update prior to releasing the unit to make sure this problem doesn't exist. So, the Autoupdates will work in the future (provided you even use this feature of WinXP).
Windows Update History Error
Started by freeloader, Apr 14 2008 07:30 AM
2 replies to this topic
#1
Posted 14 April 2008 - 07:30 AM
#2
Posted 14 April 2008 - 11:34 AM
funny. i never had this issue with AP. are you sure that isn't running an limited user account or some version of win xp that is modified by nlite or something like that? are you sure that you have installed WUS that is provided by ap? are you sure that msxml is instaled fine? have you already tried this (all of this, of course)?
#3
Posted 14 April 2008 - 01:54 PM
You're right on the ball freeloader - Love the name btw 
I've created a custom Datastore file in order to generate the default aggreements when you load a fresh install.
The custom Datastore does the following:
- defaults all updates to Microsoft Updates and not Windows Update
- you won't be prompted by IE to run the .dll upon first startup
- you bypass the first time Microsoft Update "instructions"
All of my tests didn't indicate any errors when look go to Windows Update History. Technicially it should be blank since you haven't updated anything from MS update. Would it be possible to install one item from Microsoft Update to see if this corrects the history error?
I've created a custom Datastore file in order to generate the default aggreements when you load a fresh install.
The custom Datastore does the following:
- defaults all updates to Microsoft Updates and not Windows Update
- you won't be prompted by IE to run the .dll upon first startup
- you bypass the first time Microsoft Update "instructions"
All of my tests didn't indicate any errors when look go to Windows Update History. Technicially it should be blank since you haven't updated anything from MS update. Would it be possible to install one item from Microsoft Update to see if this corrects the history error?
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users












