Fix Windows Update errors
What does this guided walk-through do?
This guided walk-through provides steps to fix problems with Windows Updates for Windows 8.1 and 7, such as taking a long time to scan, or error codes while installing updates.
For help with Windows Update issues in Windows 10, see Troubleshoot problems updating Windows 10 instead.
A common cause of errors is inadequate drive space. If you need help freeing up drive space, see Tips to free up drive space on your PC.
Common error codes
The steps in this guided walk-through should help with all Windows Update errors and other issues— you don’t need to search for the specific error to solve it. As an example, here are some commonly seen error codes: 0x0xc1900223223; 0x80240034; 0x8007000E, 0x80242006, 0x80244018, 0x80D02002, 0x80246017, 0x80240438, 0x80070070, 0x8007000D, 0x80246008, 0x80096004, 0x80070020.
The steps provided here should help fix any errors that come up during the Windows Update process.
How does it work?
We’ll begin by asking you questions about the Windows version you’re using and the issue you’re experiencing. Next, we’ll take you through a series of troubleshooting steps that are specific to your situation. At the end of each step, you’ll be asked “Did this resolve the issue?” If it’s resolved, select Yes, and you’re done! If it isn’t resolved, select No and continue with the guided walk-through.
0x80244010: Исправляем ошибку обновления Windows Update
После установки нового сервера WSUS в сети нашей компании многие клиенты не смогли получить новые обновления с сервера с ошибкой 0x80244010. Как оказалось, эта ошибка характерна не только для компьютеров, обновляющихся с внутреннего сервера WSUS, но и для устройств, получающих обновления напрямую с Windows Update. Рассмотрим, основные способы исправления ошибки 0x80244010 и восстановления работоспособности системы обновлений.
Для диагностики проблемы нужно открыть лог агента обновлений WindowsUpdate.log (в Windows 7 и 8 он находится в каталоге %Windir% , а в Windows 10 его можно получить так). В журнале обновлений при этом будут присутствовать такие строки:
2018-04-10 18:40:38:994 828 11a3c PT WARNING: Exceeded max server round trips: 0x80244010
2018-04-10 18:40:38:994 828 11a3c PT WARNING: Sync of Updates: 0x80244010
2018-04-10 18:40:38:994 828 11a3c PT WARNING: SyncServerUpdatesInternal failed: 0x80244010
2018-04-10 18:40:38:994 828 11a3c Agent * WARNING: Failed to synchronize, error = 0x80244010
2018-04-10 18:40:39:024 828 11a3c Agent * WARNING: Exit code = 0x80244010
2018-04-10 18:40:39:024 828 11a3c Agent *********
2018-04-10 18:40:39:024 828 11a3c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2018-04-10 18:40:39:024 828 11a3c Agent *************
2018-04-10 18:40:39:024 828 11a3c Agent WARNING: WU client failed Searching for update with error 0x80244010
2018-04-10 18:40:39:024 828 1017c AU >>## RESUMED ## AU: Search for updates [CallId = <128ccead-f84d-405e-9bc2-607d1694894b>]
2018-04-10 18:40:39:024 828 1017c AU # WARNING: Search callback failed, result = 0x80244010
2018-04-10 18:40:39:024 828 1017c AU # WARNING: Failed to find updates with error code 80244010
Наибольший интерес вызывает строка Exceeded max server round trips: 0x80244010. Т.е. превышено максимальное число обращений к серверу обновлений (WSUS) во время сканирования обновлений. Об этом же свидетельствует код ошибки Windows Update согласно таблице (SUS_E_PT_EXCEEDED_MAX_SERVER_TRIPS). Т.е. сервер отключает клиента, который превысил лимит обращений. Этот лимит обращений в протоколе получения обновлений Windows устанавливается на сервере обновлений и по умолчанию составляет 200 обращений. Также имеется лимит на максимальный размер XML файла, который клиент получает с сервера в рамках одного обращения — 200 Кб. Чем большее количество обновлений на сервере для клиента нужно проверить, тем больший размер скачиваемого XML файла. В том случае, если клиенту не удается получить необходимые данные за 200 сессий, он временно отключается от сервера и возвращает ошибку.
Эта ошибка возникает, как правило, из-за плохого или нестабильного сетевого соединения с сервером обновлений или когда клиенту нужно получить слишком большое количество обновлений (новый клиент сервера WSUS или компьютер, на котором давно не устанавливались обновлений).
Самый простой вариант попробовать на клиенте несколько раз (3-7 раз) нажать кнопку Try Again или выполнить команду
В большинстве случаев это решает проблему, но в том случае если клиентов в сети много, такой способ решения проблемы неприемлем.
По умолчанию клиент проверяет обновления на сервере каждые 22 часа. Можно увеличить частоту таких синхронизаций с помощью групповой политики Automatic Update detection frequency (в секции Computer Configuration -> Adminsitrative Templates -> Windows Components -> Windows Update), например до 3 часов.
Также можно на стороне сервера WSUS убрать ограничение на максимальный размер XML файла, который может скачать клиент с сервера. Для этого придется выполнить следующую команду в базе данных WSUSDB.
USE SUSDB
GO
UPDATE tbConfigurationC SET MaxXMLPerRequest = 0
Если вам не хочется менять настройки в базе WSUS, можно выполнить очистку WSUS сервера с помощью встроенного мастера очистки (Консоль Update Service -> Options -> Server Cleanup Wizard -> все опции -> Next), удалив старые, неиспользуемые и замененные обновления (особенно много мусора от обновлений MS Office). В результате такой операции, клиент Windows Update будет получать намного меньше мета-информации с WSUS сервера, и его взаимодействие должно уместиться в 200 сессий по 200кб.
Кроме того, если клиентов сервера WSUS достаточно много, можно попробовать увеличить производительность пула WsusPool согласно рекомендаций из статьи: Ошибка обновления Windows 80244022.
Если все рассмотренные способы не помогли исправить ошибку обновления на каком-то клиенте, выполните на нем скрипт сброса текущих настроек WSUS и удаления локального кэша. После чего выполните несколько циклов поиска обновлений.
Windows updates fail with the error code 0x800703f1
I recently noticed that my computer is having troubles downloading updates. It hasn’t even been able to download the November update. If I go to updates and press «Install updates», it runs for a while, gives errors on the updates, tries to install the version 1511 for a while then fails with an error too. Then it displays the same error code 0x800703f1 on all of them.
Updates that fail:
Cumulative Update for Windows 10 for x64-based Systems (KB3116869)
Update for Windows 10 for x64-based Systems (KB3106932)
Security Update for Internet Explorer Flash Player for Windows 10 for x64-based Systems (KB3087040)
SAMSUNG Electronics Co., Ltd. — Other hardware — SAMSUNG Mobile USB Composite Device
Logitech — WebCam — Logitech USB Camera (HD Webcam C525)
Upgrade to Windows 10 Pro N, version 1511, 10586
If I try the Update troubleshooter, it returns with the same fix every single time I run it. It just says it has made some changes to my system. «Windows Update components must be repaired — Fixed». It basically does nothing but indeed finds something.
I also tried the startup repair / automatic repair but it couldn’t even start. Only said that it couldn’t repair my PC.
I really would like to solve this problem without having to reinstall W10 or resetting my PC. Getting my PC back up would take time I don’t really have. Any ideas?
Replies (6)
Thank you for contacting Microsoft Community. I understand that you have an issue with installing Windows Updates and receive error code 0x800703f1 . I will surely help you to fix this issue.
This issue could have occurred due to corrupt Windows Update Components.
It looks like the Windows Update components are not completely fixed, let’s try to manually reset Windows Update components and check if it helps. I suggest you to try the steps under the section Manually reset Windows Update components and check if it helps. Resetting Windows Update Components will fix corrupt Windows Update Components.
How do I reset Windows Update components?
http://support.microsoft.com/kb/971058/en-us
Warning:
1. Applies to Windows 10.
2. Please avoid running Fixit’s and Step 11 in this article, as it does not applies to Windows 10.
3. This section, method, or task contains steps that tells you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
Hope this information helps. Reply to the post with an updated status of the issue so that we can assist you further.
Windows update failed code 1
Вопрос
I recently installed the creators update and now Windows update fails with code. 0x80070001. I tried to run WindowsUpdateDiagnostic.diagcab and it told me the problem was fixed, but I still get the error.
Все ответы
I installed KB3213641 and that seemed to work, but I still get (almost) the same errors in Windows Update after the install.
I suggest you run the following commands:
sfc /scannow
Dism /Online /Cleanup-Image /RestoreHealth
If the issue persists, manually reset the Windows Update Components:
How do I reset Windows Update components?
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
The two commands sfc and Dism completed successfully. Still the same problem.
I then tried to reset Windows Update components, but the two dirs CatRoot and SoftwareDistribution were locked. I used a tool that could rename them after a reboot. However, I still get the Windows update errors and the error seems to be related to any update, not just word 2007.
This is what I get when I search on the catalog page
We did not find any results for «kb4041994»
Please indicate whether you were or were not able to fix error 0x80070001.
If you were able to fix it please indicate the troubleshooting steps that you made.
If you were not able to fix it please let us know so that we can provide help.
I found out the problem some time ago, I just forgot to update this thread. I am running ImDisk since I want to limit the amount of writes to my flash drive. I have the temp directories set to this ram disk.
Installing ImDisk causes windows update to stop working: https://sourceforge.net/projects/imdisk-toolkit/
However, I regard using a RAM disk is as more important than windows updates so for now I have no updates.
Thanks for posting.
Thank you RTL-coder! You just made my day. I have been looking for solution to my update problem for some time now, and nothing helped.
I just needed to uninstall ImDisk and update started to work. But i’m missing my RAM disk already.
Thanks. It helped me.
In my case , I had «A» drive which was created by mounting a floppy disk image using ImDisk. But that drive wasn’t accessible. After un-mounting «A» drive, the update worked!
I think, you can reproduce this as follows ( I didn’t tried though):
1. mount an image to any drive using ImDisk
2. reboot without unmounting the drive
I had the same problem. But after uninstalling ImDisk I was able to install the updates.
I found the solution here: https://www.nico-maas.de/?p=1999
I have been having this Windows update problem for several months. I am glad I at last found this page. Looking at the current ImDisk issues, I also found the following https://sourceforge.net/p/imdisk-toolkit/tickets/9/
So after switching the RAM disk drive letter to Z: (i.e., neither A: nor B:) the issue is gone. That means Windows Update no longer fails and I can keep using ImDisk.
This last post has solved a mystery I have been having for months.
I am not using ImDisk but I am using FreeOTFE (similar to TrueCrypt and VeraCrypt) and one of my volume files is mounted as drive letter B:
I read this post, dismounted the Drive B: and now I no longer get this error and Windows Update proceeds correctly for the first time in many months.
Thanks so much. Had no idea drive letter B: was not up for grabs and should be left free for the Windows system. I will change it.
