System update readiness tool for windows 7 for x64
Восстановление хранилища компонентов при помощи средства проверки готовности системы к обновлению (SURT)
Сегодня вашему вниманию предоставляется еще одно пополнение цикла статей о методах восстановления хранилища компонентов Windows. Помимо изобретения широкой общественностью бесчисленного множества «наколеночных» методик восстановления работоспособности компонентной модели, сами разработчики из Microsoft предлагают вполне официальные методы. В данной публикации мы рассмотрим один из подобных методов, который заключается в восстановлении хранилища компонентов при помощи средства проверки готовности системы к обновлению или, иными словами восстановлении хранилища компонентов при помощи SURT. Фактически описываемым методом предусматривается проверка каталогов/файлов компонентной модели при помощи специализированного пакета и попытка устранения найденных ошибок.
Что же это за средство проверки готовности системы к обновлению?
Представляет собой набор (базу) файлов компонентов, регулярно обновляемый (был, до некоторого времени) по мере выхода новых исправлений. Грубо говоря, утилита SURT это отличный способ для большинства пользователей проанализировать хранилище компонентов в собственной системе на разного рода повреждения, и иметь возможность устранить найденные повреждения в случае, если встроенная база имеет необходимые для восстановления файлы.
Первый запуск SURT
Для начала скачиваем пакет для вашего языка и разрядности системы: KB947821 (x32) или KB947821 (x64). Запускаем только что выкачанный пакет обновления с повышенными привилегиями.
Анализ результатов
После окончания установки (статус: Установка завершена ) проверяем лог-файл %Windir%\Logs\CBS\CheckSUR.log на предмет наличия записей об ошибках. На наличие проблем в хранилище компонентов обычно указывают сообщения о найденных ошибках ( Found X errors ) или недоступных файлов для восстановления ( Unavailable repair files ):
По изначальному замыслу разработчиков, средство SURT предназначалось для автоматического исправления найденных в хранилище компонентов ошибок, именно для этого в продукт поместили полный каталог эталонных файлов. Тем не менее, со временем ситуация изменилась:
Вот именно поэтому, в случае обнаружения в лог-файле %Windir%\Logs\CBS\CheckSUR.log (битых) ненайденных файлов для восстановления, у нас имеется несколько вариантов решения.
Вариант 1: файловая часть
После того, как вы определили имена, есть несколько возможных вариантов решений:
Вариант 2: реестровая часть
Как мы помним, у компонентной модели Windows имеется часть, размещающаяся в реестре операционной системы.
Вариант 3: удаление битого пакета
Этот вариант заключается в ручном удалении проблемного пакета из командной строки.
dism /Online /Remove-Package /PackageName:Package_for_KB3037574
Fix Windows Update errors by using the DISM or System Update Readiness tool
Original product version: В Windows 10, version 1809 and later versions, Windows 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1, Windows Server 2008 R2 Service Pack 1
Original KB number: В 947821
Symptom
Windows updates and service packs may fail to install if there are corruption errors. For example, an update might not install if a system file is damaged. The DISM or System Update Readiness tool may help you to fix some Windows corruption errors.
This article is intended for Support agents and IT professionals. If you are home users and looking for more information about fixing Windows update errors, see Fix Windows Update errors.
Resolution for Windows 8.1, Windows 10 and Windows Server 2012 R2
To resolve this problem, use the inbox Deployment Image Servicing and Management (DISM) tool. Then, install the Windows update or service pack again.
Open an elevated command prompt. To do this, open Start menu or Start screen, type Command Prompt, right-select Command Prompt, and then select Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or select Allow.
Type the following command, and then press Enter. It may take several minutes for the command operation to be completed.
When you run this command, DISM uses Windows Update to provide the files that are required to fix corruptions. However, if your Windows Update client is already broken, use a running Windows installation as the repair source, or use a Windows side-by-side folder from a network share or from a removable media, such as the Windows DVD, as the source of the files. To do this, run the following command instead:
Replace the C:\RepairSource\Windows placeholder with the location of your repair source. For more information about using the DISM tool to repair Windows, reference Repair a Windows Image.
Type the sfc /scannow command and press Enter. It may take several minutes for the command operation to be completed.
Close the command prompt, and then run Windows Update 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.
Resolution for Windows 7 Service Pack 1 (SP1) and Windows Server 2008 R2 SP1
To resolve this problem, use the System Update Readiness tool. Then, install the Windows update or service pack again.
Download the System Update Readiness tool.
select the download link in the following table that corresponds to the version of Windows that is running on your computer. For more information about how to find the version of Windows that you installed, see Find out if your computer is running the 32-bit or 64-bit version of Windows.
This tool is updated regularly, we recommend that you always download the latest version. This tool is not available in every supported language. Check the link below to see if it is available in your language.
Install and run the tool.
Select Download on the Download Center webpage, then do one of the following:
In the Windows Update Standalone Installer dialog box, select Yes.
When the tool is being installed, it automatically runs. Although it typically takes less than 15 minutes to run, it might take much longer on some computers. Even if the progress bar seems to stop, the scan is still running, so don’t select Cancel.
When you see Installation complete, select Close.
Reinstall the update or service pack you were trying to install previously.
To manually fix corruption errors that the tool detects but can’t be fixed, see How to fix errors that are found in the CheckSUR log file.
You can also try to directly download the update package 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:
Open Microsoft Update Catalog in Internet Explorer.
In the search box, input the update number that you want to download. In this example, input 3006137. Then, select Search.
Find the update that applies to your operating system appropriately in the search results, and then select Add to add the update to your basket.
Select view basket to open your basket.
Select Download to download the update in your basket.
Select Browse to choose a location for the update you are downloading, and then select Continue.
Select Close after the download process is done. Then, you can find a folder that contains the update package in the location that you specified.
Open the folder, and then double-select the update package to install the update.
If the Windows update or service pack installed successfully, you are finished. If the problem is not fixed, or if System Update Readiness Tool cannot find the cause, contact us for more help.
Description of the common corruption errors
The following table lists the possible error code with 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 |
What does the System Update Readiness tool do
Verify the integrity of resources
The 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.
Logging
The System Update Readiness tool creates a log file that captures any issues that the tool found or fixed. The log file is located here:
How to fix errors that are found in the CheckSUR log file
To manually fix corruption errors that the System Update Readiness tool detects but can’t fix, follow these steps:
%SYSTEMROOT% is an environment variable that saves the folder in which Windows is installed. For example, generally the %SYSTEMROOT% folder is C:\Windows.
Identify the packages that the tool can’t fix. For example, you may find the following in the log file:
In this case, the package that is corrupted is KB958690.
Copy the package (.msu) to the %SYSTEMROOT%\CheckSUR\packages directory. By default, this directory doesn’t exist and you need to create the directory.
System Update Readiness Tool for Windows 7 for x64-based Systems
User rating User Rating
Windows updates and service packs could fail to install if there are some corruption errors on the user’s PC. For instance, an update might not install if there is a system file which is damaged. The DISM or System Update Readiness tool may help them to fix some Windows corruption errors.
Microsoft released this tool because an inconsistency was found in the Windows servicing store which may prevent the successful installation of future updates, service packs, and software. This tool checks a user’s computer for such inconsistencies and tries to resolve any issues if any are located.
Supported Operating System: Windows 7 Service Pack 1.
Technical
System Update Readiness Tool for Windows 7 for x64-based Systems
User rating User Rating
Changelog
We don’t have any change log information yet for version 947821 of System Update Readiness Tool for Windows 7 for x64-based Systems. Sometimes publishers take a little while to make this information available, so please check back in a few days to see if it has been updated.
Can you help?
If you have any changelog info you can share with us, we’d love to hear from you! Head over to ourContact pageand let us know.
Related Software
IObit Advanced SystemCare
IObit Advanced SystemCare is a software designed to speed your computer up. With the optimization, it also comes with security options that protect the internet connection from hackers. This app comes
Postman
Postman is a free tool that makes developing and using APIs easier. Postman provides all the features needed to create or mock API specifications and use the Postman Collection Runner to create tests.
Steam Gaming Platform for PC Windows
Steam, the ultimate online game platform. Instantly access your favorite gamesOver 1,100 games are available to purchase, download, and play from any computer. Join the Steam CommunityFind someo
IObit Advanced Systemcare Ultimate
Advanced SystemCare Ultimate 12 is a powerful, full-scale antivirus utilityaimed at maximising PC security and performance. It provides a one-stop solution to clean, optimize, speed up, and protect y
WinZip System Utilities Suite
WinZip System Utilities Suite enables the user to safely repair, maintain and optimise their PC’s functionality. This all-in-one maintenance solution strives to recover valuable disk space, in turn bo
IObit Advanced SystemCare Pro
Advanced SystemCare Pro 11 is a powerful full-scale software for PC security and performance. Based on the new Bitdefender antivirus engine, along with the privacy protection and PC optimization uti
iMyFone iOS System Recovery
iMyFone iOS System Recovery is able to effectively eliminate the risks of losing your current data and settings. It’s a one click solution to boot up Your iOS device back to normal without having to
Wise System Monitor
Wise System Monitor provides a clear window into your system’s real-time processes and hardware status. The app provides you with an organized list of all the processes that are run by both user and
SysTools Outlook Recovery
SysTools Outlook Recovery is a useful tool that specializes in recovering data from a corrupt, password-protected, or inaccessible PST file*. It supports both ANSI and Unicode type PST files, and the