Исправить ошибку Windows Update 0x80244007 в Windows 10
Ошибки Центра обновления Windows не редкость. Некоторые из них легко решить, в то время как другим нужно много времени и исследований для принятия решений. Одним из таких трудных для исправления случаев является ошибка Центра обновления Windows 0x80244007 . Эта ошибка просто останавливает процесс обновления Windows, и перезапуск системы мало чем помогает.
Ошибка Центра обновления Windows 0x80244007
Описание ошибки: « Клиент SOAP не выполнен, поскольку произошла ошибка SOAP по причинам кодов ошибок WU_E_PT_SOAP_ * ». Основная причина проблемы заключается в том, что Windows не может обновить файлы cookie для Центра обновления Windows ,
Если вы столкнулись с этой проблемой, вы можете попробовать следующие предложения:
1] Запустите средство устранения неполадок Центра обновления Windows.
Средство устранения неполадок Центра обновления Windows проверяет состояние служб, поддерживающих этот процесс. Он будет запрашивать и исправлять, если обнаружится что-то ненормальное. Процедура запуска средства устранения неполадок Центра обновления Windows выглядит следующим образом:
Нажмите Пуск> Настройки> Обновления и безопасность> Устранение неполадок. Затем выберите средство устранения неполадок Центра обновления Windows и запустите его. Перезагрузите систему.
Вы также можете попробовать запустить Microsoft Microsoft Windows для устранения неполадок при обновлении через Интернет и проверить, поможет ли это в решении любой из ваших проблем.
2] Удалить временные файлы
Запустите утилиту очистки диска и очистите все временные файлы, включая кэш браузера и файлы cookie.
3] Переименуйте папку Software Distribution
В папке «Распространение программного обеспечения» хранятся файлы, важные для процесса обновления Windows. Удаление или переименование папки Software Distribution и перезапуск системы помогут заменить эти файлы. В основном, файлы загружаются снова, когда мы перезагружаем систему.
80244007 windows update 2012r2
Hi guys
I have been wasting a lot of time struggling with WSUS error but no results
Need your help
We have one upstream WSUS server and 4 downstream (located in separate sites)
All servers work without any issue (no errors in event logs, synchronization is ok etc.)
But awhile ago we have faced with issue «There was a problem checking for updates. Code 80244007
It happens on each client (who looks on different WSUS server), even on WSUS server itself
When I select Check online for updates from microsoft update everything works fine.
Example of windowsupdate.log is below:
2018-03-26 13:53:31:004 924 eb8 Setup FATAL: GetClientUpdateUrl failed, err = 0x8024D009
2018-03-26 13:53:31:004 924 eb8 Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
2018-03-26 13:53:31:004 924 eb8 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2018-03-26 13:53:31:160 924 eb8 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2018-03-26 13:53:31:160 924 eb8 PT + ServiceId = <3da21691-e39d-4da6-8a4b-b43877bcb1b7>, Server URL = https://kiemsccmkie01.matone.materialise:8531/ClientWebService/client.asmx
2018-03-26 13:53:31:176 924 eb8 Agent Reading cached app categories using lifetime 604800 seconds
2018-03-26 13:53:31:176 924 eb8 Agent Read 0 cached app categories
2018-03-26 13:53:31:176 924 eb8 Agent SyncUpdates adding 0 visited app categories
2018-03-26 13:53:32:442 924 eb8 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 17; does use network; is at background priority
2018-03-26 13:53:32:660 924 eb8 WS WARNING: Nws Failure: errorCode=0x803d0013
2018-03-26 13:53:32:676 924 eb8 WS WARNING: The body of the received message contained a fault.
2018-03-26 13:53:32:676 924 eb8 WS WARNING: Soap fault info:
2018-03-26 13:53:32:676 924 eb8 WS WARNING: reason: Fault occurred
2018-03-26 13:53:32:676 924 eb8 WS WARNING: code: Client
2018-03-26 13:53:32:676 924 eb8 WS WARNING: detail: InvalidParameters parameters.InstalledNonLeafUpdateIDs d4242c38-2f13-4234-be31-bd8dca62ab80 » http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates»
2018-03-26 13:53:32:676 924 eb8 WS WARNING: Soap fault detail: errorCode=’InvalidParameters’, message=’parameters.InstalledNonLeafUpdateIDs’, , method='»http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates»‘
2018-03-26 13:53:32:676 924 eb8 WS FATAL: OnCallFailure failed with hr=0X80244007
2018-03-26 13:53:32:676 924 eb8 PT WARNING: PTError: 0x80244007
2018-03-26 13:53:32:676 924 eb8 PT WARNING: SyncUpdates_WithRecovery failed.: 0x80244007
2018-03-26 13:53:32:676 924 eb8 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 17) stopped; does use network; is at background priority
2018-03-26 13:53:32:676 924 eb8 PT + SyncUpdates round trips: 1
2018-03-26 13:53:32:676 924 eb8 PT WARNING: Sync of Updates: 0x80244007
2018-03-26 13:53:32:676 924 eb8 PT WARNING: SyncServerUpdatesInternal failed: 0x80244007
2018-03-26 13:53:32:676 924 eb8 Agent * WARNING: Failed to synchronize, error = 0x80244007
2018-03-26 13:53:32:676 924 eb8 Agent * WARNING: Exit code = 0x80244007
2018-03-26 13:53:32:676 924 eb8 Agent *********
2018-03-26 13:53:32:676 924 eb8 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdatesWuApp > 2018-03-26 13:53:32:676 924 eb8 Agent *************
2018-03-26 13:53:32:676 924 eb8 Agent WARNING: WU client failed Searching for update with error 0x80244007
2018-03-26 13:53:32:676 924 eb8 IdleTmr WU operation (CSearchCall::Init ID 2, operation # 16) stopped; does use network; is not at background priority
2018-03-26 13:53:32:676 924 eb8 IdleTmr Decremented idle timer priority operation counter to 1
2018-03-26 13:53:32:676 924 1f40 AU >>## RESUMED ## AU: Search for updates [CallId =
2018-03-26 13:53:32:676 924 1f40 AU # WARNING: Search callback failed, result = 0x80244007
2018-03-26 13:53:32:692 924 1f40 AU #########
2018-03-26 13:53:32:692 924 1f40 AU ## END ## AU: Search for updates [CallId =
2018-03-26 13:53:32:692 924 1f40 AU #############
2018-03-26 13:53:32:692 924 1f40 AU All AU searches complete.
2018-03-26 13:53:32:692 924 1f40 AU # WARNING: Failed to find updates with error code 80244007
2018-03-26 13:53:32:692 924 1f40 AU AU setting next detection timeout to 2018-03-26 11:42:00
2018-03-26 13:53:32:692 924 1f40 AU Adding timer:
2018-03-26 13:53:32:692 924 1f40 AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2018-03-26 11:42:00, not idle-only, not network-only
2018-03-26 13:53:32:692 924 1f40 AU Currently AUX is enabled — so not show any WU Upgrade notifications.
2018-03-26 13:53:32:692 924 1f40 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2018-03-26 13:53:32:692 924 1f40 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2018-03-26 13:53:37:682 924 180c Report REPORT EVENT: <4ff14c59-04f4-4af2-aadd-4cd97ce678a1>2018-03-26 13:53:32:676+0300 1 148 [AGENT_DETECTION_FAILED] 101 <00000000-0000-0000-0000-000000000000>0 80244007 AutomaticUpdatesWuApp Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007.
2018-03-26 13:53:37:854 924 180c Report CWERReporter::HandleEvents — WER report upload completed with WER status 0x8 (hr=0)
2018-03-26 13:53:37:854 924 180c Report WER Report sent: 7.9.9600.18838 0x80244007(0) 00000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdatesWuApp <3da21691-e39d-4da6-8a4b-b43877bcb1b7>0
2018-03-26 13:53:37:854 924 180c Report CWERReporter finished handling 1 events. (00000000)
2018-03-26 14:19:49:318 924 b10 IdleTmr Decremented idle timer priority operation counter to 0
I have found different solutions but nothing helped me
1) removing SoftwareDistribution folder
2) increasing maxCachedUpdartes parameter in C:\Program Files\Update Services\WebServices\ClientWebService\web.config
3) resetup WSUS and recreate wsus DB
WSUS servers are Windows Server 2012R2
Clients — Windows 7 — 10, Windows 2012r2, windows 2016
80244007 windows update 2012r2
Am 29.04.2016 schrieb june8807:
You are sure about the Servername?
Try on one Testclient in a Commandline open with admin rights:
net stop wuauserv
rd /s /q %windir%\SoftwareDistribution
del %windir%\WindowsUpdate.log
net start wuauserv
wuauclt /detectnow
wuauclt /reportnow
Wait 10 Minutes, now run Windows Update again. If it is not working,
have a look in %windir%\WindowsUpdates.log for errormessages.
Check the windows Firewall for outgoing port 8530 and on the WSUS
incoming port 8530.
Hello! Thank you for your answer.
yes, dns name is ok.
unfortunatly, i can not delete WindowsUpdate.log
C:\> del %windir%\WindowsUpdate.log
C:\Windows\WindowsUpdate.log
The process cannot access the file because it is being used by another process.
Of cause, windows update was stoped.
Magic! It works now!
Should I do «rd /s /q %windir%\SoftwareDistribution» on every client? Or there ia any other way?
Am 29.04.2016 schrieb june8807:
No, it is not. wsus.domain is not complete.
wsus or wsus.domain.tld
Better Way is http://yourWSUS:8530
If DNS is working, your clients must find WSUS.
C:\> del %windir%\WindowsUpdate.log
C:\Windows\WindowsUpdate.log
The process cannot access the file because it is being used by another process.
Of cause, windows update was stoped.
Not magic. In this cas you can stop BITS too.
Should I do «rd /s /q %windir%\SoftwareDistribution» on every client? Or there ia any other way?
If this help for you, yes you have to do this on each client.
Download and install the latest WU-Agent on this Client.
https://support.microsoft.com/en-us/kb/949104
Are all Updatess on your Mainstream-WSUS allready downloaded?
Unfortunatly we have historical singlelabel domain. so, wussrvr.domain is its dns.
Wuaueng.dll on win 2012r2 clients is 7.9.9600.18192
Wuaueng.dll on win 7(x64) is 7.6.7601.19161
The question is, is any possible way not to «rd /s /q %windir%\SoftwareDistribution» on every client? We have more than 800 clients. For me, creating new wsus — is more siutable. But, now I am not sure, if I create new server, I will not get the same trouble.
And the second question, is it possible to use 80 port for wsus (not to modify move than 20 GPO)? If i bind two http port — it looks like nothing works.
Are all Updatess on your Mainstream-WSUS allready downloaded?
We have only one WSUS. That uses TMG proxy for downloading from MS
This is one more question
Updating needing files:4
Downloaded 2591.09 Mb of 11466.11 Mb
This 2.5 Gb was downloaded, and more than sereral hours I have no progress.
8Gb? It is updates, that has not been approved (migration to win10)
Am 30.04.2016 schrieb june8807:
Unfortunatly we have historical singlelabel domain. so, wussrvr.domain is its dns.
Uiuiui, it should running with WSUS-Name only.
Wuaueng.dll on win 2012r2 clients is 7.9.9600.18192
Wuaueng.dll on win 7(x64) is 7.6.7601.19161
The question is, is any possible way not to «rd /s /q %windir%\SoftwareDistribution» on every client? We have more than 800 clients. For me, creating new wsus — is more siutable. But, now I am not sure, if I create new server, I will not get the same trouble.
You can run a Computerstartupscript an do so:
And the second question, is it possible to use 80 port for wsus (not to modify move than 20 GPO)? If i bind two http port — it looks like nothing works.
Am 30.04.2016 schrieb june8807:
Are all Updatess on your Mainstream-WSUS allready downloaded?
We have only one WSUS. That uses TMG proxy for downloading from MS
This is one more question
Updating needing files:4
Downloaded 2591.09 Mb of 11466.11 Mb
This 2.5 Gb was downloaded, and more than sereral hours I have no progress.
8Gb? It is updates, that has not been approved (migration to win10)
Hello! Thank you for your answer/support!
Yes, for sure, I can mark who has been already «deleted». But most of my network is slow, unstable and not permanenty online — some maschines are using vpn dial-in only. Logon script is going to be run in few monthes, probably (local reality 🙁 )
So, my desision was restore from backup (600 gb from tape), and re-do migration from WID to SQLexpress.
Now everything is fine. My mistake was, that I deleted «old» IIS Site (application) and re create new one.
This time I did not delete it. Just swithed to new SQL instance in registry only.
And, migic!, my old WSUS IIS site (application) got stable, no more falting.
