Description of the CheckSUR update for Windows Vista and for Windows
Vista for x64-based systems
http://support.microsoft.com/kb/947821
" What is CheckSUR?
System resources, such as file data, registry data, and even in-memory
data, can develop inconsistencies during the lifetime of the operating
system. These inconsistencies may be caused by various hardware failures
or by software issues. In some cases, these inconsistencies can affect
the Windows Servicing Store, and they can cause a Windows Vista update
to fail. When the update fails, it blocks the user from installing
updates and service packs. CheckSUR addresses this issue.
When Windows Update detects inconsistencies that are related to system
servicing in system files or in the registry, Windows Update offers
CheckSUR as an available update package. The package titles are as follows:
• Update for Windows Vista (KB947821)
• Update for Windows Vista for x64-based Systems (KB947821)
Note This Windows Update or Automatic Update package will only be
offered if such inconsistencies have been detected on the system.
CheckSUR should run automatically after it has been installed from
Windows Update.
What Windows Update installation errors can CheckSUR potentially address?
The following table shows a list of errors that users may receive when
they try to install a Windows Vista update, and CheckSUR detects
irregularities that it can potentially fix.
Note These errors are typically listed in the
%systemroot%\Logs\CBS\CBS.log file or in the CBS.persist.log file. "
>
>> 0x80070002 ERROR_FILE_NOT_FOUND The system cannot find the file specified.
>> 0x8007000D ERROR_INVALID_DATA The data is invalid.
>> 0x800F081F CBS_E_SOURCE_MISSING The source for the package or file not found.
>> 0x80073712 ERROR_SXS_COMPONENT_STORE_CORRUPT The component store is in an inconsistent state.
>> 0x800736CC ERROR_SXS_FILE_HASH_MISMATCH A component’s file does not match the verification information present in the component manifest.
>> 0x800705B9 ERROR_XML_PARSE_ERROR Unable to parse the requested XML data.
>> 0x80070246 ERROR_ILLEGAL_CHARACTER An invalid character was encountered.
>> 0x8007370D ERROR_SXS_IDENTITY_PARSE_ERROR An identity string is malformed.
>> 0x8007370B ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME The name of an attribute in an identity is not within the valid range.
>> 0x8007370A ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_VALUE The value of an attribute in an identity is not within the valid range.
>> 0x80070057 ERROR_INVALID_PARAMETER The parameter is incorrect.
>> 0x800B0100 TRUST_E_NOSIGNATURE No signature was present in the subject.
>> 0x80092003 CRYPT_E_FILE_ERROR An error occurred while Windows Update reads or writes to a file.
>> 0x800B0101 CERT_E_EXPIRED A required certificate is not within its validity period when verifying against the current system clock or the time stamp in the signed file.
>> 0x8007371B ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE One or more required members of the transaction are not present.
NOTE: The KB article does not include this BUT, the error codes may also
appear during the Automatic Updating process and/or be present in the
WindowsUpdate.log that is located in the WINDOWS directory [folder]
*Hopefully*, this update will address the mysterious and/or undocumented
error codes specific to Vista that can be attributed to file data,
registry data, and in-memory data that have developed 'inconsistencies'.
MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============
Similar Threads
Linear Mode
