Ошибка 8024200D — системная ошибка, которая возникает при сбое в работе Центра обновления Windows.
Причиной ошибки 8024200D могут быть:
- Конфликт DNS;
- Конфликт системного уровня.
Иногда при индивидуальных настройках антивирусов или программ, выявляющих вредоносные ПО и блокирующих рекламу, можно заодно заблокировать установку обновлений Windows. В таком случае нужно временно отключить антивирус, вернуться к стандартным настройкам, либо переустановить программы.
Следующим шагом нужно сделать проверку системных файлов Windows для восстановления поврежденных или отсутствующих.
- Нажмите клавишу Windows на клавиатуре + R;
- Введите команду cmd;
- Нажмите «ОК».
Перед вами откроется консоль командной строки Windows. В ней введите команду:
Sfc / scannow
Просто скопируйте ее отсюда и вставьте, нажав после «ОК».
Если это не помогло воспользуйтесь следующими рекомендациями.
If you’re seeing an error code 0x8024200d when performing a Windows update, you’re not alone. Many Windows users are reporting it. This error code usually appears when they try to update to a new build of the Windows system. The reason behind it is that some updated files are missing or corrupted.
The good news is you can fix it. You should be able to fix the problem quite easily using one of the solutions we’ve listed below. You may not have to try them all. Just work your way down the list until you find the one that works.
- Running the Windows Update Troubleshooter
- Restarting the Windows Update service
- Running System File Checker
- Downloading updates from Microsoft Update Catalog manually
Method 1: Running the Windows Update Troubleshooter
You can download and run the Windows Update Troubleshooter to automatically diagnose and resolve any issues regarding Windows Update.
1) Click here to download the Windows Update Troubleshooter.
2) Double-click the downloaded file (WindowsUpdate.diagcab) to run the troubleshooter, and then click Next.
If your current operating system is Windows 7, you just need to wait until the troubleshooter finishes the process and shows you the process result. If your current operating system is Windows 8 or Windows 10, you may need to follow the steps below.
3) If there is a more recent version of Windows Update troubleshooter available, click to run it.
4) In the new version of Windows Update troubleshooter, Click Next. The troubleshooter will check the available updates for your machine.
5) Click Apply this fix to start the update process in the background immediately.
The troubleshooter will try to fix the issue for you. You can restart your computer and try to perform the Windows update again. If it still doesn’t work, please try the next method.
Method 2: Restarting the Windows Update service
You may see this error code if there is something wrong with the Windows Update service. You can try to restart the Windows Update service to resolve this problem. Here’s how to do it:
1) On your keyboard, press the Windows Logo key and R at the same time to open the Run dialog, then type services.msc and press Enter to open the Services window.
2) Right-click Windows Update and select Stop if its current status is “Running”. If the Windows Update service is not running, please skip this step.
3) On your keyboard, press the Windows Logo Key and E at the same time to open File Explorer. Copy the path below and paste it into the address bar, then press Enter on your keyboard to go to the DataStore folder.
C:\Windows\SoftwareDistribution\DataStore
4) Delete all the files in the folder DataStore.
5) On your keyboard, press the Windows Logo Key and E at the same time to open File Explorer. Copy the path below and paste it into the address bar, then press Enter on your keyboard to open the Download folder.
C:\Windows\SoftwareDistribution\Download
6) Delete all the files in the folder Download.
7) In the Services window, right-click Windows Update and select Start.
Go and check Windows Update again to see whether you can perform the Windows update or not. If it still doesn’t work, please try the next method.
Method 3: Running System File Checker
System File Checker can scan for corruptions in Windows system files and restore corrupted files. When you fail to install Windows updates, it may be caused by some corruption error. In this case, running System File Checker may help you resolve this issue.
1) On your keyboard, press the Windows Logo Key and then type cmd in the search box. When you see Command Prompt in the list of results, right-click it and then select Run as administrator. You will be prompted for permission. Click Ok to run the Command Prompt.
2) On your keyboard, type the command below and press Enter. If your current operating system is Windows 7, please skip this step.
DISM.exe /Online /Cleanup-image /Restorehealth
It may take several minutes for this command operation to be completed.
3) When this command operation is completed, on your keyboard, type the following command and press Enter.
sfc /scannow
It may take some time for the command operation to be completed.
4) When this command operation is completed, close the Command Prompt and run Windows Update again to check whether this method works or not. If you still fail to install updates for your Windows system, please try the next method.
Method 4: Downloading updates from Microsoft Update Catalog manually
If all the methods mentioned above still don’t work for you, you can try to download the updates you failed to install from Microsoft Update Catalog and install them manually.
1) On your keyboard, press the Windows Logo Key and type Windows Update, and then press Enter to open Windows Update.
2) Click View update history to check the updates you failed to install. For example, if you fail to install update KB3006137, you can download the update and install it manually.
3) Follow the instructions below to view your system type:
i. On your keyboard, press the Windows Logo key and R at the same time to open the Run dialog. Type cmd and press Enter to open the Command Prompt.
ii. Type the command line systeminfo and press Enter to view your system type.
“X64-based PC” indicates that your Windows OS is 64-bit; “X86-based PC” means that your Windows OS is 32-bit.
4) Visit Microsoft Update Catalog.
5) Type the update number that you want to download. In this example, type KB3006137 and then click Search.
6) In the list of search results, select the right update for your operating system and click Download.
If your Windows OS is 64-bit, you should download the update whose name contains “x64-based”.
7) In the pop-up window, click the link to start downloading the updates.
Double-click the downloaded file and follow the on-screen instructions to install the update.
The Windows Update Error 8024200D (WU_E_UH_NEEDANOTHERDOWNLOAD) means that the Windows Update handled can’t install the update because the update downloaded is invalid and corrupted. This error is most commonly encountered on Windows 7.
If you are affected by this error code, you are likely to experience this behavior every time Windows Update attempt to install an update that has failed on the first try. This problem has been patched with newer Windows builds but remains prevalent with older builds.
The main reason why you’ll see this error is a WU inconsistency that can be fixed either by resetting the entire Windows component or by bypassing it entirely by downloading and installing the update manually using the Windows Update Catalog.
Update: This problem can also occur due to a corrupted Windows Update database.
Here’s a list of confirmed methods that you can use to troubleshoot this error:
1. Install the failing update manually
If you’re looking for a quick fix that will bypass a local issue that triggers the 8024200d error, use the Windows Update Catalog to install the failing update manually.
This method is only recommended if you only have one update that is throwing the 8024200d WU error when you attempt to install it.
Important: Keep in mind that going this route will not effectively address the root source of the issue. Even if this allows you to bypass the error and install the problematic update, it will not address the root cause of the issue. If you want to fix root the issue, continue troubleshooting with the remaining methods below even if this method allows you to install the failing update.
Here’s how to use the Windows Update Catalog to bypass the 8024200d error:
- Launch the homepage for the Microsoft Update Catalog in your web browser.
- Use the search box in the upper-right corner of the Microsoft Update Catalog page to discover the update that failed to install.
Searching for the failing update inside Windows Update Note: You can grab the update code from the WU error message inside the Windows Update page.
- From the list of results, identify the update applicable to your Windows version.
Identify the correct update Note: Consider the CPU architecture and Windows version while looking for an appropriate update, after analyzing the findings.
- After identifying the required update, click the Download option and wait until the download is complete.
- Once the download is complete, double-click the executable file you just downloaded from the Downloads folder.
- Follow the on-screen instructions to complete the sideloading of the next Windows update.
- Now that the update is installed, reboot your PC and see if the 8024200d has disappeared from the Windows update screen.
2. Run the Windows Update Troubleshooter
Running the Windows Update troubleshooter is a great way to try and fix this issue using the built-in tools provided by Microsoft.
If you are experiencing the 8024200D error due to a common WU inconsistency, running the Windows Update Troubleshooter and applying the recommended fix should help you resolve this issue.
Note: The Windows Update Troubleshooter provides a collection of automated repair strategies that may be used to treat the most common causes of a failing Windows update.
If Windows Update Troubleshooter manages to identify the cause of the error, follow the instructions to apply the recommended solution.
Here’s how to run the Windows Update Troubleshooter and apply the recommended fix:
- Press the Windows key + R to open the Run dialog box.
- Type “control” and hit the Enter key to enter the Control Panel interface.
Open up the classic Control Panel interface - Click “Yes” when prompted by User Account Control to grant administrator permissions.
- Utilize the Control Panel’s search function to look for “troubleshoot” (top-right corner of the screen).
- From the list of search results, click on Troubleshooting.
Open up the Troubleshooting tab - Under System and Security, click on Fix problems with Windows Update.
Find and Fix Problems with Windows Update Note: If you are running Windows 11, you may see different displays moving forward.
When asked by the Windows Update Troubleshooter, click Next and wait for the initial scan to complete. - Click Apply this Fix if you find a possible solution to implement it in the current situation.
Apply this fix - Once the solution is effective, restart your computer and attempt to reapply the unsuccessful update.
3. Reset the BITS & Cryptographic Services
Another scenario where you might see the 8024200d error when installing a pending Windows update is if two very important service dependencies (Background Intelligent Transfer Service and Cryptographic Service) do not receive content link headers.
Note: This is an old issue that is patched on Windows 11 and Windows 11 but still occring on Windows 7.
To fix this issue, you’ll need to reset both services & rename the two folders where Windows Update stores temporary Windows Files (Catroot 2 & Software Distribution). However, in order to complete this methods, you’ll also need to disable a series of additional WU dependencies to make sure there’s no interference.
Here’s a quick guide on how to do this:
- To open the Run dialog box, press the Windows key + R.
- Then, to start a Command Prompt with elevated privileges, type “cmd” into the text box and press Ctrl + Shift + Enter.
Open up an elevated CMD prompt Note: Grant administrator access by choosing Yes when asked by the UAC (User Account Control) window.
- To stop all WU-related services, type the following commands in the following order at the elevated Command Prompt and press Enter after each command:
net stop wuauserv net stop cryptSvc net stop bits net stop msiserver
Note: By following these steps, the Windows Update Service, MSI Installer, Cryptographic Service, and BITS Service will all be killed manually.
- Use the following commands to remove and rename the SoftwareDistribution and Catroot2 folders once all relevant services have been stopped:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 Catroot2.old
Important: These folders are responsible for storing updated files required by the WU component. If you rename these folders, your operating system will be compelled to build new, healthy copies.
- After the folders have been cleaned up, execute the following commands to enable the previously deactivated services:
net start wuauserv net start cryptSvc net start bits net start msiserver
- Restart your computer when it has restarted to verify if the issue has been resolved.
4. Run SFC & DISM Scans
File corruption that interferes with the auto-updating capability of Windows installation is one of the most common reasons of the 8024200d error while attempting to install a pending system update.
In this case, it’s recommended to perform a few system file scans utilizing built-in tools System File Checker (SFC) and Deployment Image Servicing and Management (DISM).
Note: Although SFC and DISM are fairly similar, we recommend running both checks in short succession to enhance the likelihood of recovering corrupt system files.
Our recommendation is to start with a simple SFC scan. You can deploy this tool without an active connection to the internet.
Important: It is imperative to maintain the CMD window active after initiating this process, even if the application seems frozen. This is a common occurrence, especially on Windows 7. Stopping the operation before it’s finished, this might result in logical problems on your HDD or SSD.
Once the SFC scan is finished, follow it up with a DISM scan with admin access without restarting your PC. DISM uses a component of Windows Update to obtain healthy replacements to replace corrupt system files. Because of this, you’ll need to ensure that you have a stable internet connection before beginning this operation.
Before commencing this operation, you must thus ensure that you have access to a reliable Internet connection.
After the DISM scan is complete, restart your computer to verify if the 8024200d error has been addressed.
5. Install Update in Clean Boot Mode
It’s also possible that you’re dealing with this issue due to a scenario where a 3rd party application, startup item or service that is interfering with the Windows Update procedure.
If this scenario is applicable, one way to get around the 8024200d error is to is to achieve a clean boot state before attempting to install the update again.
Note: A clean boot forces your system to load just the required Windows apps and services. Once the clean boot state has been reached, no third-party services, processes, or starting items will be permitted to run.
Here’s a quick guide on achieving a clean boot state before reinstalling the problematic update that’s triggering the 8024200d error:
- Follow the steps outlined in this article to achieve a clean boot state.
Achieve a clean boot state - Once you restart your PC in clean boot mode, press Windows key + R to open up a Run dialog box.
- Next, type ‘wuapp’ inside the text box of Run, then press Ctrl + Shift + Enter to open up an elevated Windows Update instance.
Open up the Windows update menu via Run box Note: This command will only work for Windows 7. If you’re on Windows 10 or Windows 11, use ‘ms-settings:windowsupdate’ instead.
- Inside the Windows Update screen, click on Check for Updates.
- If the problematic update is available to install again, click on Install updates and see if it installs without the same 8024200d error.
Install pending updates
6. Delete Update logs & reinstall the update
Inconsistent WU log files can also cause this error. This is even more likely you have multiple updates that are all failing with the 8024200d and you started to experience this issue after an unexpected system shutdown while the update was installing.
In this case, you’re probably dealing with an issue affecting the integrity of servicing packages, manifests or WU underlying components.
To address this issue, you’ll need to access a series of hidden directories and delete the update logs before retrying the update.
Here’s how to do this:
- Press Windows key + R to open up a Run dialog box.
- Next, type ‘%SYSTEMROOT%\Logs\CBS\’ and press Ctrl + Shift + Enter to the first hidden folder with admin access.
Open up the CBS folder - At the User Account Control (UAC), click Yes to grant admin access.
- Inside the location, delete the cbs.log by right-clicking on it and clicking Delete from the context menu.
Deleting the CBS log Note: If the CBS folder contains a secondary log file named CheckSUR.log delete that as well.
- Once both files have been deleted, restart your PC and see if the problem is now fixed.
7. Perform a repair install
If you’ve come this far and you still can get past the 8024200d and install the pending update, you are likely dealing with file corruption that you will not be able to fix without replacing the entire suite of Windows files.
In this case, doing an in-place repair (repair install) or a clean installation are your only options on getting back to a state where Windows is able to install pending updates automatically.
A clean installation is a simpler option, but the main disadvantage is that you cannot preserve your data – including applications, games, and personal files (unless you back them out first).
If you’re looking for a method to save you from losing data, go for a repair install procedure. The main advantage is that you get to keep your data, including applications, games, files present on the OS drive and even certain user preferences.
Vectra86, сведения об ошибке из WindowsUpdate.log:
Кликните здесь для просмотра всего текста
2019-08-16 09:22:03:305 5804 c78 Handler :::::::::::::
2019-08-16 09:22:03:306 5804 c78 Handler :: START :: Handler: CBS Install
2019-08-16 09:22:03:306 5804 c78 Handler :::::::::
2019-08-16 09:22:03:395 5804 c78 Handler Starting install of CBS update DF2A0E82-0BA0-4327-B470-ECDD68A24781
2019-08-16 09:22:03:863 5804 c78 Handler CBS package identity: Package_for_RollupFix~31bf3856ad364e35~a md64~~7601.24511.1.9
2019-08-16 09:22:03:865 5804 c78 Handler Installing express with source=C:\Windows\SoftwareDistribution\D ownload\15d147703e0b083c4fa1124d090e2075 , workingdir=C:\Windows\SoftwareDistributi on\Download\15d147703e0b083c4fa1124d090e 2075
2019-08-16 09:22:08:202 1028 1720 Report REPORT EVENT: {6112D2EA-2314-430C-86F1-9B0B6BCFFE1E} 2019-08-16 09:22:03:202+0300 1 181 101 {AAAC3765-DA59-4597-82B4-B05E6B206BB8} 201 0 AutomaticUpdates Success Content Install Installation Started: Windows successfully started the following update: Ежемесячный набор исправлений качества системы безопасности для систем Windows 7 на базе процессоров x64 (KB4512506), 08 2019 г.
2019-08-16 09:22:26:326 5804 1c10 Handler WARNING: CBS called ResolveSource
2019-08-16 09:22:31:285 5804 1c10 Handler FATAL: CBS called Error with 0x800f081f,
2019-08-16 09:22:31:285 5804 c78 Handler FATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x8024200d
2019-08-16 09:22:31:285 1028 1c64 AU >>## RESUMED ## AU: Installing update [UpdateId = {AAAC3765-DA59-4597-82B4-B05E6B206BB8}]
2019-08-16 09:22:31:285 1028 1c64 AU # WARNING: Install failed, error = 0x8024200D / 0x8024200D
2019-08-16 09:22:31:285 5804 c78 Handler :::::::::
2019-08-16 09:22:31:286 5804 c78 Handler :: END :: Handler: CBS Install
2019-08-16 09:22:31:286 5804 c78 Handler :::::::::::::
Сведения об ошибке 0x8024200D:
0x8024200D — WU_E_UH_NEEDANOTHERDOWNLOAD — The update handler did not install the update because it needs to be downloaded again.
Ошибка установки обновления из-за того, что обновления было некорректно скачано.
Информация из CBS.log:
Кликните здесь для просмотра всего текста
2019-08-17 07:07:37, Info CBS Calling client to resolve source, cannot find file ‘rdpcorets.dll’ at path: \\?\C:\Windows\SoftwareDistribution\Down load\15d147703e0b083c4fa1124d090e2075\am d64_microsoft-windows-r..s-regkeys-component_31bf3856ad364e35_7.1.7601.2371 3_none_7fad1d2fc274167d\rdpcorets.dll
2019-08-17 07:07:37, Error CBS Exec: Failed to pre-stage package: Package_1779_for_KB4512506~31bf3856ad364 e35~amd64~~6.1.1.9, file: rdpcorets.dll, source: \\?\C:\Windows\SoftwareDistribution\Down load\15d147703e0b083c4fa1124d090e2075\am d64_microsoft-windows-r..s-regkeys-component_31bf3856ad364e35_7.1.7601.2371 3_none_7fad1d2fc274167d\rdpcorets.dll, sandbox: (null) [HRESULT = 0x800f081f — CBS_E_SOURCE_MISSING]
2019-08-17 07:07:37, Info CBS Failed to gather all required files. [HRESULT = 0x800f081f — CBS_E_SOURCE_MISSING]
2019-08-17 07:07:37, Info CBS Failed to gather all missing files for package: Package_for_RollupFix~31bf3856ad364e35~a md64~~7601.24511.1.9 [HRESULT = 0x800f081f — CBS_E_SOURCE_MISSING]
В частности был не скачан компонент обновления rdpcorets.dll.
Добавлено через 6 минут
Выполните очистку папок SoftwareDistribution и Catroot2. См. пункт 2 статьи Устранение неполадок с Центром обновления Windows и ошибок при установке обновлений
Далее скачайте файл обновления из Каталога Центра обновления Майкрософт и запустите установку обновления из скачанного файла.
Если обновление не установиться, то пришлите файлы WindowsUpdate.log и CBS.log снова.
Привет, дорогие читатели! Сегодня я хочу поделиться с вами историей о том, как я столкнулся с одной из самых коварных ошибок обновления Windows 7 — ошибкой 8024200D. Эта проблема заставила меня потратить немало времени и нервов, прежде чем я нашел способ ее решения. Мой опыт, надеюсь, поможет вам избежать подобных трудностей в будущем.
Первая встреча с ошибкой 8024200D
Все началось одним солнечным утром, когда я решил, что пора обновить мой добрый старый компьютер с Windows 7. Все шло как по маслу, пока процесс обновления не остановился на полпути с криптографическим сообщением об ошибке 8024200D. Я был озадачен и немного разочарован, ведь до этого момента мой ПК работал как часы.
Поиски решения
Первым делом я обратился к всезнающему Google, надеясь найти быстрое и простое решение. Информации было много, но, к сожалению, далеко не все советы оказались полезными. После нескольких часов чтения форумов и статей я выяснил, что ошибка 8024200D может быть вызвана различными причинами, включая поврежденные файлы обновления или конфликты с антивирусным программным обеспечением.
Шаг 1: Запуск инструмента поиска и устранения неисправностей Windows
Первым моим шагом стал запуск встроенного инструмента Windows для устранения проблем с обновлениями. Я нашел его в панели управления в разделе «Устранение неполадок«. К сожалению, это не принесло желаемого результата, и ошибка 8024200D продолжала мне мешать.
Шаг 2: Отключение антивируса и брандмауэра
Следующим шагом я решил временно отключить антивирус и брандмауэр, догадываясь, что они могут каким-то образом блокировать процесс обновления. Это было несложно сделать, но, к моему удивлению, и это не помогло.
Шаг 3: Очистка папки SoftwareDistribution
Затем я наткнулся на совет очистить папку SoftwareDistribution, где Windows хранит временные файлы обновлений. Для этого мне пришлось открыть командную строку от имени администратора и ввести следующие команды:
net stop wuauserv
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
net start wuauserv
Это действие оказалось весьма полезным. После перезагрузки компьютера и повторной попытки установить обновления ошибка 8024200D, казалось, исчезла.
Шаг 4: Использование инструмента обновления системы
Наконец, последним шагом в моем путешествии стало использование инструмента обновления системы от Microsoft. Этот инструмент предназначен для помощи в решении проблем с обновлениями путем повторного скачивания и установки поврежденных обновлений. С его помощью я смог окончательно избавиться от ошибки и успешно обновить свою систему.
Выводы
Опыт борьбы с ошибкой 8024200D научил меня терпению и упорству. Я понял, что в мире Windows существует множество инструментов и методик, которые могут помочь в решении даже самых сложных задач. Главное — не сдаваться и не бояться пробовать разные подходы.
Моя история, надеюсь, окажется полезной для тех, кто столкнется с подобной или любой другой ошибкой обновления Windows. Помните, что за каждой технической проблемой стоит логическое решение. И да, иногда для его нахождения требуется немного больше времени и усилий, чем мы ожидаем.
Спасибо, что уделили время чтению моего рассказа. Удачи вам в решении ваших технических задач и пусть ваш компьютер всегда работает без сбоев!