Some (like 1-2) updates won't install for some reason and Windows Update recommended me the System Update Readiness Tool.
This is the log it made:
CheckSUR.persist.log
=================================
Checking System Update Readiness.
Version 6.0.6001.22275
2009-02-12 16:47
Checking Deployment Packages
Checking Package Manifests and catalogs.
Checking package watchlist.
Checking component watchlist.
Checking packages.
Checking component store
(f) CSI Manifest and S256H Do Not Match 0x00000000 WinSxS\Manifests\x86_microsoft-windows-i..nternetcontrolpanel_31bf3856ad364e35_6.0.6000.16809_none_8d5c6dd054a9dde3.manifest x86_microsoft-windows-i..nternetcontrolpanel_31bf3856ad364e35_6.0.6000.16809_none_8d5c6dd054a9dde3
Checking SMI Store
Summary:
Milliseconds: 879505
Found 1 errors
CSI Manifest and S256H Do Not Match Total Count: 1
Customer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.
=================================
Checking System Update Readiness.
Binary Version 6.0.6001.22375
Package Version 5.0
2009-05-01 10:32
Checking Deployment Packages
Checking Package Manifests and catalogs.
Checking package watchlist.
Checking component watchlist.
Checking packages.
Checking component store
Summary:
Seconds executed: 854
No errors detected
Customer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.
So did it actually fix that found error? If so, what kind of error was that? Or is there anything else I should do?
Thanks
This post has been edited by Bv202: 01 May 2009 - 03:50 AM

Help


Back to top









