| Tinker wrote:
| > TaurArian wrote:
| >> | >> | TaurArian wrote:
| >> | > | >> | > | Tinker wrote:
| >> | > | > My system has been trying to install the update KB947821 for
| >> several
| >> | > | > days now. The install seems to go ok, with the install
| >> reported as
| >> | > | > successful, but it keeps reappearing on the "new updates list".
| >> | > | >
| >> | > | > If I recall correctly this is one of the updates that has to be
| >> | > | > installed before SP1.
| >> | > | >
| >> | > | > Suggestions, tips and/or things to try?
| >> | > | >
| >> | > | > Tinker
| >> | > |
| >> | > | Found the log file for CheckSUR, it is below.
| >> | > |
| >> | > | Now what do I do about the "corrupt manifest" errors?
| >> | > |
| >> | > | Tinker
| >> | > |
| >> | > | =================================
| >> | > | Checking System Update Readiness.
| >> | > | Version 6.0.6000.2
| >> | > | 2008-03-21 14:18:58 PM
| >> | > |
| >> | > | Checking Deployment Packages
| >> | > |
| >> | > | Checking Package Manifests and catalogs.
| >> | > | (f) Corrupt Manifest CBS 0x800F0900
| >> | > |
| >> \servicing\packages\Package_2_for_KB946041~31bf3856ad364e35~amd64~~6.0.1.0.mum
| >>
| >> | > | Line 1: MZ
| >> | > |
| >> | > | Checking package watchlist.
| >> | > |
| >> | > | Checking component watchlist.
| >> | > |
| >> | > | Checking packages.
| >> | > | Checking component registry
| >> | > |
| >> | > | Checking component store
| >> | > | (f) Corrupt Manifest CSI 0x00000000
| >> | > |
| >> | >
| >>
\winsxs\Manifests\amd64_92ad9ec01fbfc43ff0ad4f643bfe04c9_31bf3856ad364e35_6.0.6000.16609_none_605cf59574d5d9f6.manifest
| >>
| >> | > | Hash: Stored hash does not match file hash
| >> | > | (f) Corrupt Manifest CSI 0x00000000
| >> | > |
| >> | >
| >>
\winsxs\Manifests\amd64_d71f546266d1077c9226a1ad94096174_31bf3856ad364e35_6.0.6000.20734_none_5b34654266acffac.manifest
| >>
| >> | > | Hash: Stored hash does not match file hash
| >> | > | (f) Corrupt Manifest CSI 0x00000000
| >> | > |
| >> | >
| >>
\winsxs\Manifests\amd64_microsoft-windows-oespamfilter-dat_31bf3856ad364e35_6.0.6000.20778_none_4d0666a940006185.manifest
| >>
| >> | > | Hash: Stored hash does not match file hash
| >> | > |
| >> | > | Scanned 12652 components, 18275 component payload files
| >> | > | Summary:
| >> | > | Milliseconds: 1383515
| >> | > | Found 4 errors
| >> | > | CSI Corrupt Manifest Total Count: 3
| >> | > | CBS Corrupt Manifest Total Count: 1
| >> | > | Customer Experience report successfuly uploaded. Thank you for
| >> | > | participating. For more information, see the Microsoft Customer
| >> | > | Experience Improvement Program on the Microsoft web site.
| >> | >
| >> | >
| >> | > Reboot - did it fix anything? Is SP1 now available.
| >> |
| >> |
| >> | No change still asking to install KB947821 despite the "successful
| >> | installation of the patch 14 times.
| >> |
| >> | Tinker
| >>
| >>
| >> Tinker, I really don't know at this stage - perhaps
| >> Windows Vista Service Pack 1 (All Languages)
| >> Unlimited installation and compatibility support is available at no
| >> charge until March 18, 2009.
| >>
https://support.microsoft.com/oas/default.aspx?ln=en-us&x=8&y=7&prid=11274&gprid=500921
| >>
| >>
| >> Please post back with any information that MS gives you that actually
| >> works .... this will assist others.
| >>
| > Thanks for the link. If I get an answer that is helpful, I'll post it to
| > this thread.
| >
| > Tinker
|
| Response from MS stated that there can be a correct installation without
| all the synchronization being done. MS recommended that I hide the
| update, and proceed.
|
| I have done so, and the message to install KB947821 is gone. When I
| check for hidden updates, it does not appear in that listing. (it's
| blank in my case.)
|
| Now trying to get SP1 installed: proceeds to about 6% download and
| errors with code 800F0900, but that's another thread.
|
| Thank you for the suggestions.
|
| Tinker
Thanks for the update, it appears MS weren't very helpful. All I found on that error is
"failed to evaluate install rule". Not very helpful. Go back to MS and again ask for help
again and provide the latest problem/error code.
K