80244019 ошибка обновления windows 2008 r2 — Ваш верный помощник с OS Windows

Some colleagues had recently performed a migration from an old Windows Server 2003 WSUS server to a new Server 2012 R2 one. I had just upgraded a new tablet from Windows 8.1 Professional to Enterprise, and was trying to update it as the update process doe not retain updates applied to the original OS. Group policy was telling the tablet to talk to my WSUS server (the one that had just been migrated). Windows Update on the tablet was finding updates, but getting an error 80244019 when trying to downlad them. Searching against Windows Update on the internet both found and was able to download updates.

I had a look in the Windows Update log file (C:\Windows\WindowsUpdate.log) and found some of the following:

2014-10-28	13:13:36:140	 368	1558	DnldMgr	***********  DnldMgr: New download job [UpdateId = {7F8FDE4D-B17B-4093-915E-A807DA18A2DE}.204]  ***********
2014-10-28	13:13:36:140	 368	1558	DnldMgr	WARNING: CheckIfDirExists returned error 0x80070002.
2014-10-28	13:13:36:140	 368	1558	DnldMgr	  * Queueing update for download handler request generation.
2014-10-28	13:13:36:140	 368	1558	DnldMgr	Generating download request for update {7F8FDE4D-B17B-4093-915E-A807DA18A2DE}.204
2014-10-28	13:13:36:140	 368	1558	IdleTmr	WU operation (GenerateAllDownloadRequests) started; operation # 635; does not use network; is at background priority
2014-10-28	13:13:36:140	 368	18ec	IdleTmr	Decremented idle timer priority operation counter to 2
2014-10-28	13:13:36:156	 368	1558	Handler	Generating request for CBS update 7F8FDE4D-B17B-4093-915E-A807DA18A2DE in sandbox C:\WINDOWS\SoftwareDistribution\Download\5cbfe1eec732bb919f7239386a1b893b
2014-10-28	13:13:36:156	 368	1558	Handler	Selected payload type is ptExpress
2014-10-28	13:13:36:156	 368	1558	Handler	Detected download state is dsStart
2014-10-28	13:13:36:156	 368	1558	Handler	Adding windows8.1-kb2975719-x64-express.cab (entire file) to request list.
2014-10-28	13:13:36:156	 368	1558	Handler	Request generation for CBS update complete with hr=0x0 and pfResetSandbox=0 
2014-10-28	13:13:36:156	 368	1558	IdleTmr	WU operation (GenerateAllDownloadRequests, operation # 635) stopped; does not use network; is at background priority
2014-10-28	13:13:36:156	 368	1558	DnldMgr	***********  DnldMgr: New download job [UpdateId = {7F8FDE4D-B17B-4093-915E-A807DA18A2DE}.204]  ***********
2014-10-28	13:13:36:156	 368	1558	DnldMgr	WARNING: CheckIfDirExists returned error 0x80070002.
2014-10-28	13:13:36:156	 368	1558	DnldMgr	  * BITS job initialized, JobId = {EC94DB72-43C2-4A3D-9972-62715BD76BBF}
2014-10-28	13:13:36:156	 368	1558	DnldMgr	  * Downloading from http://wsus.rcmtech.co.uk/Content/08/40D35A609AE17FA88A39A1E98420A646FE750A08.cab to C:\WINDOWS\SoftwareDistribution\Download\5cbfe1eec732bb919f7239386a1b893b\windows8.1-kb2975719-x64-express.cab (full file).
2014-10-28	13:13:36:171	 368	1558	IdleTmr	WU operation (DownloadManagerDownloadJob) started; operation # 637; does use network; is not at background priority; will NOT stop idle timer
2014-10-28	13:13:36:171	 368	1558	IdleTmr	Incremented idle timer priority operation counter to 3
2014-10-28	13:13:36:171	 368	1558	DnldMgr	*********
2014-10-28	13:13:36:171	 368	1558	DnldMgr	**  END  **  DnldMgr: Begin Downloading Updates [CallerId = AutomaticUpdatesWuApp]
2014-10-28	13:13:36:171	 368	1558	DnldMgr	*************
2014-10-28	13:13:36:171	 368	18ec	AU	AU checked download status and it changed: Downloading is paused
2014-10-28	13:13:36:171	 368	148c	DnldMgr	WARNING: BITS job {EC94DB72-43C2-4A3D-9972-62715BD76BBF} failed, updateId = {7F8FDE4D-B17B-4093-915E-A807DA18A2DE}.204, hr = 0x80190194, BG_ERROR_CONTEXT = 5
2014-10-28	13:13:36:171	 368	148c	DnldMgr	  Progress failure bytes total = 177805422, bytes transferred = 0
2014-10-28	13:13:36:171	 368	148c	DnldMgr	  Failed job file: URL = http://wsus.rcmtech.co.uk/Content/08/40D35A609AE17FA88A39A1E98420A646FE750A08.cab, local path = C:\WINDOWS\SoftwareDistribution\Download\5cbfe1eec732bb919f7239386a1b893b\windows8.1-kb2975719-x64-express.cab
2014-10-28	13:13:36:171	 368	148c	DnldMgr	CUpdateDownloadJob::GetNetworkCostSwitch() Neither unrestricted or restricted network cost used, so using current cost
2014-10-28	13:13:36:187	 368	148c	IdleTmr	WU operation (DownloadManagerDownloadJob, operation # 637) stopped; does use network; is not at background priority; will NOT start idle timer (task did not previously stop it
2014-10-28	13:13:36:187	 368	148c	IdleTmr	Decremented idle timer priority operation counter to 2
2014-10-28	13:13:36:187	 368	148c	DnldMgr	Error 0x80244019 occurred while downloading update; notifying dependent calls.

and also several of these:

2014-10-28	13:12:10:040	 368	1294	Misc	WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194
2014-10-28	13:12:10:040	 368	1294	Misc	WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194
2014-10-28	13:12:10:040	 368	1294	Agent	WARNING: Fail to download eula file http://wsus.rcmtech.co.uk/Content/78/5FB2FB1198FAF0871AF09DAE0EF815C92642FD78.txt with error 0x80244019
2014-10-28	13:12:10:040	 368	1294	Misc	WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194
2014-10-28	13:12:10:040	 368	1294	Misc	WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194
2014-10-28	13:12:10:040	 368	1294	Agent	WARNING: Fail to download eula file http://wsus.rcmtech.co.uk/Content/78/5FB2FB1198FAF0871AF09DAE0EF815C92642FD78.txt with error 0x80244019

I tried to retrieve one of the EULA text files referenced via Internet Explorer and got a 404 page not found error.

So then I did a bit of digging and came across this thread, where the guy fixed the problem by moving the location of his (misconfigured) WsusContent folder.

I checked out my new WSUS server and sure enough found a WsusContent folder within a WsusContent folder on the drive that had been specified during the WSUS migration/configuration.

D:\WsusContent had about 240GB of data in it, whereas D:\WsusContent\WsusContent only had about 1.6GB of data. D:\WsusData did include the EULA text file that I’d seen referenced in the log, and had received a 404 for via IE.

I didn’t like the idea copying the 240GB of data into the nested WsusContent folder, so thought I’d try fixing the problem by reconfiguring WSUS instead. It was actually fairly easy:

Change the following two registry values:

HKLM\Software\Microsoft\Update Services\Server\Setup\ContentDir
Change the REG_EXPAND_SZ to D:\ and restart the WsusService service. (note that this step may not be necessary due to the naming of the registry ke, i.e. “Setup”, but I’m doing it anyway to be tidy.
HKLM\System\CurrentControlSet\Services\LanmanServer\Shares\WsusContent
Change the REG_MULTI_SZ from D:\wsuscontent\WsusContent to D:\WsusContent and restart the lanmanserver service.

Next, in IIS Manager, expand <Servername>, Sites, Default Web Site, right-click Content, Manage virtual directory, Advanced Settings and change Physical Path to D:\WsusContent\ – I did an iisreset after this, but that may not be necessary.

Finally, I moved the contents of the erroneous D:\WsusContent\WsusContent folder into D:\WsusContent.

After those steps were completed, the text file was avaible via IE and my tablet is now happily updating itself from the WSUS server.

Incidentally, I like keeping the WsusContent folder on a separate drive as a) it can get quite big and I don’t want to risk my C: drive filling up, and b) it means I can use Windows Data Deduplication on it, where I’m currently getting about a 43% space reduction.

Источник

1 / 1 / 0

Регистрация: 24.12.2010

Сообщений: 20

Server 2008

02.08.2012, 12:51. Показов 28620. Ответов 1

Ошибка 80244019 WindowsUpdate на кленте
Непойму в чем проблема фаер вол отключен , сервер обновлений указан с портом,
связь к серверу есть…другой сервер по тому же адресу конектится…

Добавлено через 23 минуты
log

2012-08-02 12:02:35:293 848 615c PT WARNING: Cached cookie has expired or new PID is available
2012-08-02 12:02:35:293 848 615c PT Initializing simple targeting cookie, clientId = 8f537605-ef6b-467c-bdf3-c5641b0a0c35, target group = Terminal-servers, DNS name = ts01-msk.khortitsa.com
2012-08-02 12:02:35:293 848 615c PT Server URL = http://wsus.khortitsa.com/Simp… eAuth.asmx
2012-08-02 12:02:35:364 848 615c PT WARNING: GetAuthorizationCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2012-08-02 12:02:35:364 848 615c PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244019
2012-08-02 12:02:35:364 848 615c PT WARNING: PopulateAuthCookies failed: 0x80244019
2012-08-02 12:02:35:364 848 615c PT WARNING: RefreshCookie failed: 0x80244019
2012-08-02 12:02:35:364 848 615c PT WARNING: RefreshPTState failed: 0x80244019
2012-08-02 12:02:35:364 848 615c PT WARNING: PTError: 0x80244019
2012-08-02 12:02:35:364 848 615c Report WARNING: Reporter failed to upload events with hr = 80244019.
2012-08-02 12:09:32:666 848 94d8 AU Triggering AU detection through DetectNow API
2012-08-02 12:09:32:666 848 94d8 AU Triggering Online detection (interactive)
2012-08-02 12:09:32:667 848 277c AU #############
2012-08-02 12:09:32:667 848 277c AU ## START ## AU: Search for updates
2012-08-02 12:09:32:667 848 277c AU #########
2012-08-02 12:09:32:669 848 277c AU <<## SUBMITTED ## AU: Search for updates [CallId = {0F2BFC7F-79BA-4337-8CD6-C27E1AF2EB61}]
2012-08-02 12:09:32:670 848 615c Agent *************
2012-08-02 12:09:32:670 848 615c Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2012-08-02 12:09:32:670 848 615c Agent *********
2012-08-02 12:09:32:670 848 615c Agent * Online = Yes; Ignore download priority = No
2012-08-02 12:09:32:670 848 615c Agent * Criteria = «IsInstalled=0 and DeploymentAction=’Installation’ or IsPresent=1 and DeploymentAction=’Uninstallation’ or IsInstalled=1 and DeploymentAction=’Installation’ and RebootRequired=1 or IsInstalled=0 and DeploymentAction=’Uninstallation’ and RebootRequired=1»
2012-08-02 12:09:32:670 848 615c Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2012-08-02 12:09:32:670 848 615c Agent * Search Scope = {Machine}
2012-08-02 12:09:32:670 848 615c Setup Checking for agent SelfUpdate
2012-08-02 12:09:32:671 848 615c Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2012-08-02 12:09:32:671 848 615c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpda te\wuident.cab:
2012-08-02 12:09:32:681 848 615c Misc Microsoft signed: Yes
2012-08-02 12:09:32:752 848 615c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpda te\wuident.cab:
2012-08-02 12:09:32:760 848 615c Misc Microsoft signed: Yes
2012-08-02 12:09:32:763 848 615c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpda te\wsus3setup.cab:
2012-08-02 12:09:32:770 848 615c Misc Microsoft signed: Yes
2012-08-02 12:09:32:808 848 615c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpda te\wsus3setup.cab:
2012-08-02 12:09:32:814 848 615c Misc Microsoft signed: Yes
2012-08-02 12:09:32:862 848 615c Setup Determining whether a new setup handler needs to be downloaded
2012-08-02 12:09:32:862 848 615c Setup SelfUpdate handler is not found. It will be downloaded
2012-08-02 12:09:32:863 848 615c Setup Evaluating applicability of setup package «WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600 .256»
2012-08-02 12:09:32:868 848 615c Setup Setup package «WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600 .256» is already installed.
2012-08-02 12:09:32:868 848 615c Setup Evaluating applicability of setup package «WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.760 0.256»
2012-08-02 12:09:32:896 848 615c Setup Setup package «WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.760 0.256» is already installed.
2012-08-02 12:09:32:896 848 615c Setup Evaluating applicability of setup package «WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.760 0.256»
2012-08-02 12:09:32:937 848 615c Setup Setup package «WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.760 0.256» is already installed.
2012-08-02 12:09:32:937 848 615c Setup SelfUpdate check completed. SelfUpdate is NOT required.
2012-08-02 12:09:33:156 848 615c PT +++++++++++ PT: Synchronizing server updates +++++++++++
2012-08-02 12:09:33:157 848 615c PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsus.khortitsa.com/Clie… lient.asmx
2012-08-02 12:09:33:207 848 615c PT WARNING: Cached cookie has expired or new PID is available
2012-08-02 12:09:33:207 848 615c PT Initializing simple targeting cookie, clientId = 8f537605-ef6b-467c-bdf3-c5641b0a0c35, target group = Terminal-servers, DNS name = ts01-msk.khortitsa.com
2012-08-02 12:09:33:207 848 615c PT Server URL = http://wsus.khortitsa.com/Simp… eAuth.asmx
2012-08-02 12:09:33:274 848 615c PT WARNING: GetAuthorizationCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2012-08-02 12:09:33:274 848 615c PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244019
2012-08-02 12:09:33:274 848 615c PT WARNING: PopulateAuthCookies failed: 0x80244019
2012-08-02 12:09:33:274 848 615c PT WARNING: RefreshCookie failed: 0x80244019
2012-08-02 12:09:33:274 848 615c PT WARNING: RefreshPTState failed: 0x80244019
2012-08-02 12:09:33:274 848 615c PT WARNING: Sync of Updates: 0x80244019
2012-08-02 12:09:33:274 848 615c PT WARNING: SyncServerUpdatesInternal failed: 0x80244019
2012-08-02 12:09:33:274 848 615c Agent * WARNING: Failed to synchronize, error = 0x80244019
2012-08-02 12:09:33:275 848 615c Agent * WARNING: Exit code = 0x80244019
2012-08-02 12:09:33:275 848 615c Agent *********
2012-08-02 12:09:33:275 848 615c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2012-08-02 12:09:33:275 848 615c Agent *************
2012-08-02 12:09:33:275 848 615c Agent WARNING: WU client failed Searching for update with error 0x80244019
2012-08-02 12:09:33:282 848 8428 AU >>## RESUMED ## AU: Search for updates [CallId = {0F2BFC7F-79BA-4337-8CD6-C27E1AF2EB61}]
2012-08-02 12:09:33:283 848 8428 AU # WARNING: Search callback failed, result = 0x80244019
2012-08-02 12:09:33:283 848 8428 AU # WARNING: Failed to find updates with error code 80244019
2012-08-02 12:09:33:283 848 8428 AU #########
2012-08-02 12:09:33:283 848 8428 AU ## END ## AU: Search for updates [CallId = {0F2BFC7F-79BA-4337-8CD6-C27E1AF2EB61}]
2012-08-02 12:09:33:283 848 8428 AU #############
2012-08-02 12:09:33:283 848 8428 AU Successfully wrote event for AU health state:0
2012-08-02 12:09:33:285 848 8428 AU AU setting next detection timeout to 2012-08-02 12:13:07
2012-08-02 12:09:33:286 848 8428 AU Successfully wrote event for AU health state:0
2012-08-02 12:09:33:286 848 8428 AU Successfully wrote event for AU health state:0
2012-08-02 12:09:38:278 848 615c Report REPORT EVENT: {E6FF2450-768A-440A-B239-E4BAB6197DC9} 2012-08-02 12:09:33:275+0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244019 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244019.
2012-08-02 12:09:38:289 848 615c Report CWERReporter::HandleEvents — WER report upload completed with status 0x8
2012-08-02 12:09:38:289 848 615c Report WER Report sent: 7.6.7600.256 0x80244019 00000000-0000-0000-0000-000000000000 Scan 101 Managed
2012-08-02 12:09:38:289 848 615c Report CWERReporter finishing event handling. (00000000)
2012-08-02 12:12:06:597 848 94d8 AU Triggering AU detection through DetectNow API
2012-08-02 12:12:06:597 848 94d8 AU Triggering Online detection (interactive)
2012-08-02 12:12:06:598 848 277c AU #############
2012-08-02 12:12:06:598 848 277c AU ## START ## AU: Search for updates
2012-08-02 12:12:06:598 848 277c AU #########
2012-08-02 12:12:06:600 848 277c AU <<## SUBMITTED ## AU: Search for updates [CallId = {335591D8-DEBF-414A-BF2C-0A1FBD829721}]
2012-08-02 12:12:06:601 848 615c Agent *************
2012-08-02 12:12:06:601 848 615c Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2012-08-02 12:12:06:601 848 615c Agent *********
2012-08-02 12:12:06:601 848 615c Agent * Online = Yes; Ignore download priority = No
2012-08-02 12:12:06:601 848 615c Agent * Criteria = «IsInstalled=0 and DeploymentAction=’Installation’ or IsPresent=1 and DeploymentAction=’Uninstallation’ or IsInstalled=1 and DeploymentAction=’Installation’ and RebootRequired=1 or IsInstalled=0 and DeploymentAction=’Uninstallation’ and RebootRequired=1»
2012-08-02 12:12:06:601 848 615c Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2012-08-02 12:12:06:601 848 615c Agent * Search Scope = {Machine}
2012-08-02 12:12:06:601 848 615c Setup Checking for agent SelfUpdate
2012-08-02 12:12:06:602 848 615c Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2012-08-02 12:12:06:602 848 615c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpda te\wuident.cab:
2012-08-02 12:12:06:615 848 615c Misc Microsoft signed: Yes
2012-08-02 12:12:06:689 848 615c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpda te\wuident.cab:
2012-08-02 12:12:06:695 848 615c Misc Microsoft signed: Yes
2012-08-02 12:12:06:699 848 615c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpda te\wsus3setup.cab:
2012-08-02 12:12:06:707 848 615c Misc Microsoft signed: Yes
2012-08-02 12:12:06:744 848 615c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpda te\wsus3setup.cab:
2012-08-02 12:12:06:752 848 615c Misc Microsoft signed: Yes
2012-08-02 12:12:06:810 848 615c Setup Determining whether a new setup handler needs to be downloaded
2012-08-02 12:12:06:810 848 615c Setup SelfUpdate handler is not found. It will be downloaded
2012-08-02 12:12:06:810 848 615c Setup Evaluating applicability of setup package «WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600 .256»
2012-08-02 12:12:06:814 848 615c Setup Setup package «WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600 .256» is already installed.
2012-08-02 12:12:06:814 848 615c Setup Evaluating applicability of setup package «WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.760 0.256»
2012-08-02 12:12:06:843 848 615c Setup Setup package «WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.760 0.256» is already installed.
2012-08-02 12:12:06:844 848 615c Setup Evaluating applicability of setup package «WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.760 0.256»
2012-08-02 12:12:06:884 848 615c Setup Setup package «WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.760 0.256» is already installed.
2012-08-02 12:12:06:884 848 615c Setup SelfUpdate check completed. SelfUpdate is NOT required.
2012-08-02 12:12:07:096 848 615c PT +++++++++++ PT: Synchronizing server updates +++++++++++
2012-08-02 12:12:07:096 848 615c PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsus.khortitsa.com/Clie… lient.asmx
2012-08-02 12:12:07:136 848 615c PT WARNING: Cached cookie has expired or new PID is available
2012-08-02 12:12:07:136 848 615c PT Initializing simple targeting cookie, clientId = 8f537605-ef6b-467c-bdf3-c5641b0a0c35, target group = Terminal-servers, DNS name = ts01-msk.khortitsa.com
2012-08-02 12:12:07:136 848 615c PT Server URL = http://wsus.khortitsa.com/Simp… eAuth.asmx
2012-08-02 12:12:07:203 848 615c PT WARNING: GetAuthorizationCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2012-08-02 12:12:07:203 848 615c PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244019
2012-08-02 12:12:07:203 848 615c PT WARNING: PopulateAuthCookies failed: 0x80244019
2012-08-02 12:12:07:203 848 615c PT WARNING: RefreshCookie failed: 0x80244019
2012-08-02 12:12:07:203 848 615c PT WARNING: RefreshPTState failed: 0x80244019
2012-08-02 12:12:07:203 848 615c PT WARNING: Sync of Updates: 0x80244019
2012-08-02 12:12:07:203 848 615c PT WARNING: SyncServerUpdatesInternal failed: 0x80244019
2012-08-02 12:12:07:203 848 615c Agent * WARNING: Failed to synchronize, error = 0x80244019
2012-08-02 12:12:07:205 848 615c Agent * WARNING: Exit code = 0x80244019
2012-08-02 12:12:07:205 848 615c Agent *********
2012-08-02 12:12:07:205 848 615c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2012-08-02 12:12:07:205 848 615c Agent *************
2012-08-02 12:12:07:205 848 615c Agent WARNING: WU client failed Searching for update with error 0x80244019
2012-08-02 12:12:07:212 848 8428 AU >>## RESUMED ## AU: Search for updates [CallId = {335591D8-DEBF-414A-BF2C-0A1FBD829721}]
2012-08-02 12:12:07:212 848 8428 AU # WARNING: Search callback failed, result = 0x80244019
2012-08-02 12:12:07:212 848 8428 AU # WARNING: Failed to find updates with error code 80244019
2012-08-02 12:12:07:212 848 8428 AU #########
2012-08-02 12:12:07:212 848 8428 AU ## END ## AU: Search for updates [CallId = {335591D8-DEBF-414A-BF2C-0A1FBD829721}]
2012-08-02 12:12:07:213 848 8428 AU #############
2012-08-02 12:12:07:213 848 8428 AU Successfully wrote event for AU health state:0
2012-08-02 12:12:07:214 848 8428 AU AU setting next detection timeout to 2012-08-02 12:35:56
2012-08-02 12:12:07:214 848 8428 AU Successfully wrote event for AU health state:0
2012-08-02 12:12:07:215 848 8428 AU Successfully wrote event for AU health state:0
2012-08-02 12:12:12:205 848 615c Report REPORT EVENT: {2F67A85B-EF08-4DA2-9C6E-D2BA0320BB7D} 2012-08-02 12:12:07:204+0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244019 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244019.
2012-08-02 12:12:12:214 848 615c Report CWERReporter::HandleEvents — WER report upload completed with status 0x8
2012-08-02 12:12:12:215 848 615c Report WER Report sent: 7.6.7600.256 0x80244019 00000000-0000-0000-0000-000000000000 Scan 101 Managed
2012-08-02 12:12:12:215 848 615c Report CWERReporter finishing event handling. (00000000)

Добавлено через 32 минуты
В папке Windows есть папка SoftwareDistribution,в ней ней папка DataStore,с нее надо все удалить,а после с папки Download,которая находится в этой же папке SoftwareDistribution,но перед удалением надо посетить панель управления — администрирование — управление компьютером — службы и приложения — службы.Последний процесс в списке — центр обновления Windows надо остановить(от прав администратора),потом все удаляем,потом перезагружаемся на всякий случай,потом вновь запускаем центр обновления Windows(от прав администратора).

У меня все заработало.

Источник

Error 80244019 is a Windows Update failure error that is triggered when the Windows Updates fails to connect to the Windows Server.

Windows Updates is a feature built into Windows responsible for securing your system by checking with the Windows Update Server and applying the necessary updates. It runs in the background, and works continuously to check for updates, and apply them. Since, it is responsible for securing a large number of programs – things can go wrong due to technical and software glitches.

When the updates stop working, or for any reason they fail to update, it will return an error code which helps technician take the directions in addressing the issue.

In this guide, we will be troubleshooting error 80244019.

Resetting Windows Update Components for Windows 7

Microsoft has released a Fixit numbered 50202 for Resetting Update Components. Resetting, them usually fixes this issue on Windows 7. To run it click (here) to download the Fixit file, and run it. Accept the agreement and click Next, and put a check on Aggressive Mode, and then hit Next again. Wait for it to finish, once it finishes and the system has rebooted, check for updates again. If the issue still persists, move on to the next solution.

Turn On Data Execution Prevention (DEP) (Windows 7 / Windows 8 / 10)

Turning DEP on apparently resolved this issue for many users. The DEP feature restricts interruption to Windows Updates.

Hold the Windows Key and Press R. Type sysdm.cpl and ClickOK.

Then click Advanced -> Settings -> Data Execution Protection.

Select Turn on DEP for Essential Windows Programs and Services only and Click Apply. Click OK.

Reboot your system, and now try updating.

Limit Windows Update (Windows 7 and 8 and 10)

Windows Update servers can refuse your request to get updates if your system is incorrectly requesting updates. What we will do next is disable checking updates for other programs. Once the update suceeds, you can then re-enable it.

Go to Control Panel. Change the View by type to Large icons from the drop down list in the upper right corner.

Scroll down and Click on Windows Update.

Now click on Change settings link on the left pane.

Uncheck Give me updates for other Microsoft products when I update Windows. Click OK.

If it was already unchecked, then place a check next to it. Click OK. Restart your system and test to see if the updates work, if not, move on to the next solution.

Check and Install the Failing Update Manually

Sometimes, manually install the update also works in correcting the issue. First, view your update history from Windows Updates and take a note of the update number that has failed.

Go to Control Panel and search for Windows Update. Now click on View Update History. Get the update number and do a google search. Go to the Microsoft site with the update and download it. Run it and install it.

Kamil Anwar

Kamil is a certified MCITP, CCNA (W), CCNA (S) and a former British Computer Society Member with over 9 years of experience Configuring, Deploying and Managing Switches, Firewalls and Domain Controllers also an old-school still active on FreeNode.

Источник

Table of contents

How to Fix the Error 0x80244019
- Method 1: Check the features of your antivirus software
- Method 2: Use the troubleshooter for Windows updates
- Method 3: Change the settings for your Windows Update
- Method 4: Reset the Windows Update components
- Method 5: Perform a clean boot
- Method 6: Manually install the updates
- Method 7: Installing optional updates
- Method 8: Perform an in-place upgrade
Conclusion
FAQ

Have you experienced theWindows update error 0x80244019 ? This guide will help you resolve the problem. As you know, keeping your Windows updated is important to protect your system from cyber threats. However, the error number 0x80244019 can be problematic if it is not resolved early. This article will show you how to resolve the 0x80244019 error. Let’s begin.

How to Fix the Error 0x80244019

Follow the methods below to fix the 0x80244019 error:

Method 1: Check the features of your antivirus software

If you’re using a third-party antivirus program, it can interfere with your system and cause the error 0x80244019 to appear.

You can eliminate this problem by disabling certain features in your antivirus.

If you’ve tried that solution and yet the error persists, you should try removing your antivirus. This just might permanently fix the problem.

If so, we recommend switching to a different antivirus program.

PRO TIP

Several security tools are available on the market. However, we highly suggest using a reliable program like Auslogics Anti-Malware.

It is designed not to interfere with your main antivirus while detecting threats and attacks you’d never suspect existed.

You can remove the error and still get the protection your computer needs.

Learn more at: Auslogics Anti-Malware: Features and Reviews

Method 2: Use the troubleshooter for Windows updates

Windows 10 has different troubleshooters dedicated to repairing specific programs and processes.

Users who tried to find methods to fix Windows 10 error code 0x80244019 discovered that using the Windows update troubleshooter helped them resolve the problem.

You can also use that tool to get rid of the error. Simply follow these instructions:

On your keyboard, press Windows key + I . This should open the Settings app.
Select Updates & Security , then go to the left pane and click Troubleshoot .
Go to the right pane and click Windows Update .
Click Run the troubleshooter .
Once the troubleshooter has completed the scanning and repair process, check if the problem persists.

Related:Windows Update Troubleshooter: Fixing Windows Update Issues

Method 3: Change the settings for your Windows Update

Certain settings of your Windows Update client may be causing the error 0x80244019 to show up. You can tweak the options to see if this fixes the issue.

Simply follow the steps below:

Click the Search icon on your taskbar.
Type settings , then hit Enter .
Go to Update & Security .
Scroll down until you reach the Update settings section.
Click on Advanced options .
Switch off the Give me updates for other Microsoft products when I update Windows option.

Related:How to Fix Windows Update Error 0x80073712?

Method 4: Reset the Windows Update components

You have to ensure that all the important components of Windows Update are running correctly. You can’t successfully download and install the updates if they aren’t.

You might even see the error 0x80244019. Thankfully, this can be resolved by resetting certain components.

To do that, you just need to follow these instructions:

Right-click the Windows logo on your taskbar.
Select Command Prompt (Admin) or Powershell (Admin) from the menu.
Run the following commands:

net stop wuauserv 

net stop cryptSvc 

net stop bits 

net stop msiserver 

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old 

ren C:\Windows\System32\catroot2 Catroot2.old 

net start wuauserv 

net start cryptSvc 

net start bits 

net start msiserver

These commands should reset the necessary components for Windows Update. Try downloading and installing the updates again and see if the error persists.

Related:[EXPLAINED] Does Windows 10 Need Antivirus?

Method 5: Perform a clean boot

The error 80244019 can show up due to certain third-party applications interfering with your system. You can fix this by performing a clean boot.

By doing this, your computer will start without any third-party services or applications. That said, here are the steps you need to follow:

On your keyboard, press Windows key + R . This should open the Run dialog box.
Type msconfig , then hit Enter .
Go to the Services tab and select the Hide all Microsoft services box.
Click Disable all .
Go to the Startup tab, then click Open Task Manager .
Right-click every startup item, then select Disable .
Exit Task Manager, then click OK to restart your PC.

After performing a clean boot, try installing the update and check if the error is gone.

Method 6: Manually install the updates

Resolving the Windows update error 0x80244019 on Windows 10 sometimes requires manual installation. The process is not too complicated.

The first step is to get the update’s KB number. To do so, search for that number in the Windows Update section.

Once you’ve taken note of the KB number, follow the steps below:
Visit the Windows Update Catalog website.
Click the search field and submit the KB number.
You will see a list of matching updates. Choose the update that is suitable for your system architecture.
Download and install the update, then check if the error persists.

It is worth noting that this method is just a workaround for the error. It lets you avoid the error but does not fix the core problem. If you find the time, try performing an in-place upgrade as laid out in Method 8.

Method 7: Installing optional updates

Some users who had become tired of problematic updates opted to use a special tool that blocked the installation process.

Of course, this method can help you avoid specific update issues. However, hiding optional updates can cause the error 0x80244019 to appear.

So, it would be best to unblock and install them. Doing this should help you install the rest of the updates without hassle.

Method 8: Perform an in-place upgrade

You can also get rid of the error 0x80244019 by performing an in-place upgrade. This allows you to install and update the latest Windows version.

Don’t worry, because this method still allows you to keep all your files and applications. You just have to follow the instructions below:

Go to Microsoft’s website and download the Media Creation Tool .
Run the program, then select Upgrade this PC now . The setup will now download all the necessary files.
Select the Download and install updates (recommended) option.
Wait while the setup is downloading the updates.
Follow the on-screen instructions until you reach the Ready to install screen.
Click the Change what to keep option.
Don’t forget to select the Keep personal files and apps option. Click Next to proceed.

After completing the process, your PC should have the latest Windows version. This should also help you resolve the error 0x80244019 .

PRO TIP

We recommend updating your drivers first if you plan to run the Media Creation Tool from a USB flash drive.

This ensures that you will be able to perform the in-place upgrade with no problems. You can manually do that, but an easier option would be to use Auslogics Driver Updater.

This tool fixes and updates all your problematic drivers, ensuring you can use your USB flash drive and other peripherals without hassle.

Conclusion

Now that you have the methods to rectify the annoying Windows update error 0x80244019, you can take on the problem.

By properly troubleshooting and resolving errors, you can keep your system updated and safe from cyberattacks.

Let us know which solution works best for you in the comments section below, and don’t let this error stop you from moving forward.

Share this information with friends who may be having similar problems.

FAQ

How do I fix the error 0x80244019?

Check your antivirus software and disable any features causing the error. If that doesn’t work, remove your antivirus program, as it may conflict with system updates.

An additional tool for identifying and resolving update-related issues is the Windows Update troubleshooter.

Additionally, you can resolve the issue by changing the settings or restarting the Windows Update components.

How do I fix the 0x80244010 Windows 10 update error?

First, make sure your internet connection is reliable and stable. Then, restart your computer and attempt to install the Windows update once more.

If the error continues, you can use the Windows Update troubleshooter to find and fix any update process problems.

The error 0x80244010 can also be fixed by manually applying the updates or looking for any pending updates that may be interfering with the process.

Источник

Ошибка 80244019 в Windows

Давайте разберемся, как исправить ошибку 80244019, подробнее как она выглядит на скриншоте, как видите, у меня есть и эти пакости 80244019 и 84B20001. Вообще у 84B20001 забавная формулировка (произошла неизвестная ошибка Центра обновления Windows)

Ошибка 80244019 при обновлении в Windows Server 2008 R2-01

Наиболее частые причины этой ошибки 80244019 и 84B20001:

Вирус
Битовая служба и Центр обновления Windows не работают
И надо чистить реестр от старых и неправильных ключей.
заблокировать брандмауэр
проверьте, есть ли интернет
проверь свой DNS
перезапуск службы BITS

Первое, что нужно сделать, это проверить, запущены ли службы. Для этого нажимаем Win + R, откроется окно Выполнить и введите services.msc,

Ошибка 80244019 при обновлении в Windows Server 2008 R2-02

откроется сервисная оснастка. Давайте сделаем все по алфавиту и посмотрим внизу, чтобы работали Центр обновления Windows и фоновая интеллектуальная служба передачи (BITS).

Ошибка 80244019 при обновлении в Windows Server 2008 R2-03

Если со службами все в порядке, мы очищаем реестр Windows с помощью Ccleaner или Privazer.
Если это не помогает, просканируйте свою систему на вирусы в безопасном режиме.
Вы также можете исправить значение реестра.

Для этого нажмите WIN + R и введите Regedit

HKEY_LOCAL_MACHINE \ SOFTWARE \ Policies \ Microsoft \ Windows \ Центр обновления Windows \ AU
Дважды щелкните ключ UseWUServer DWORD и измените его значение на 0. И перезапустите.

Если раздела нет, его можно создать, например, в Windows 8.1 и новее.

Иногда бывает полезно запустить команду wuauclt / reset через командную строку cmd

Если в настройках сети указаны DNS-серверы вручную, проверьте их доступность.

Картинка с сайта: zhivye-oboi-windows.ru
Я также видел на другом форуме, что удаление программы proxyswitch помогает, если она у вас есть.

Исправляем 80244019 ошибка обновления windows 8.1

Например, в Windows 8.1 нет раздела реестра WindowsUpdate \ AU и код 80244019 в Windows 8.1 появляется очень часто при сбое службы BITS, попробуйте ее перезапустить. Для этого откройте командную строку от имени администратора и введите команды:

чистый стоповый бит

чистые стартовые биты

и чистая остановка wuauser

чистый старт wuausserv

Если вам лень регистрировать все, вы можете скачать готовый cmd файл, который перезапускает битовые службы и центр обновлений

Снимаем галку «Обновите другие продукты Microsoft«

Если кто не в курсе, есть два типа обновлений:

Обновления безопасности и исправления ошибок
Для дополнительных продуктов

Если обновление Windows выдает код ошибки 80244019, вы можете попробовать снять флажок «При обновлении Windows предоставлять обновления для других продуктов Microsoft»

Находится попутно (для Windows 7 и Windows 8.1)

Панель управления \ Все элементы панели управления \ Центр обновления Windows \ Настройка параметров

отключить дополнительные обновления Windows

Вот как легко разрешить ошибку 80244019 и ошибку 84B20001 при обновлении до Windows Server 2008 R2. Убедитесь, что у вас есть Интернет и ваши серверы Microsoft не заблокированы внешним брандмауэром, не забывайте об этом.

обновление агента центра обновлений, которое можно загрузить с веб-сайта Microsoft и установить отдельно, также может быть полезным

Для других версий Windows 7–10 процедура для 84B20001 и 80244019 такая же. Да пребудет с тобой победа.

Материал с сайта zhivye-oboi-windows.ru

Источник