Lỗi updater process ended with error 7 mi 8
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Show
In this articleThis article offers you advanced manual methods to fix problems that prevent Windows Update from installing successfully by using the System Update Readiness Tool or the Deployment Image Servicing and Management (DISM) tool. Note This article is intended for use by support agents and IT professionals. If you're home users and looking for more information about fixing Windows update errors, see Fix Windows Update errors. Original KB number: 947821 Common corruption errorsWindows updates may fail to install if there are corruption errors. The following table lists the possible error codes for Windows Update for your reference: Code Error Description 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. 0x80070490 ERROR_NOT_FOUND Windows could not search for new updates. 0x800f0984 PSFX_E_MATCHING_BINARY_MISSING Matching component directory exist but binary missing 0x800f0986 PSFX_E_APPLY_FORWARD_DELTA_FAILED Applying forward delta failed 0x800f0982 PSFX_E_MATCHING_COMPONENT_NOT_FOUND Can't identify matching component for hydration For example, an update might not install if a system file is damaged. The DISM or may help you fix some Windows corruption errors. Check this page for Windows Update troubleshooting scenarios. Solution 1: Use DISMTo resolve this problem, use the DISM tool. Then, install the Windows update or service pack again.
DISM creates a log file (%windir%/Logs/CBS/CBS.log) that captures any issues that the tool found or fixed. %windir% is the folder in which Windows is installed. For example, the %windir% folder is C:\Windows. Note The solution mentioned in this section is applicable for Windows 7 and Windows Server 2008 R2. For Modern Windows versions like Windows 11, Windows 10, Windows Server 2016, or later, check . To resolve this problem, use the System Update Readiness tool. Then, install the Windows update or service pack again.
To manually fix corruption errors that the tool detects but can't fix, see . Solution 3: Use Microsoft Update CatalogYou can also try to download the update package directly from Microsoft Update Catalog, and then install the update package manually. For example, you may have problems when you try to install updates from Windows Update. In this situation, you can download the update package and try to install the update manually. To do this, follow these steps:
Verify the integrity of resourcesThe System Update Readiness tool verifies the integrity of the following resources:
This list may be updated at any time. When the System Update Readiness tool detects incorrect manifests, Cabinets, or registry data, it may replace the incorrect data with a corrected version. LoggingThe System Update Readiness tool creates a log file that captures any issues that the tool found or fixed. The log file is located here:
Fix errors found in the CheckSUR log fileTo manually fix corruption errors that the System Update Readiness tool detects but can't fix, follow these steps:
If you're a technical professional, see How to fix errors found in the CheckSUR.log for another option on fixing errors in the CheckSUR.log. Data collectionIf you need assistance from Microsoft support, we recommend you collect the information by following the steps mentioned in Gather information by using TSS for deployment-related issues. |