A
Albert M Gostick
Hi all,
A client of mine asked me to look at a domain controller that is not updating properly. I found out that the updates have not been applied since mid 2015. When I run the updater manually, it comes back with error 0x8007000e. Looking in the Windows update log, I see this (I will highlight a couple entries that I think are important but don't let that sway you, I really don't know if they are the root problem or not):
2019-04-23 12:27:02:319 2804 14a8 CltUI FATAL: CNetworkCostChangeHandler::RegisterForCostChangeNotifications: CoCreateInstance failed with error 80004002
2019-04-23 12:27:02:319 2804 14a8 CltUI WARNING: RegisterNetworkCostChangeNotification: Error 80004002
2019-04-23 12:27:05:034 6268 e20 AU Triggering AU detection through DetectNow API
2019-04-23 12:27:05:034 6268 e20 AU Triggering Online detection (interactive)
2019-04-23 12:27:08:045 6268 f44 AU #############
2019-04-23 12:27:08:045 6268 f44 AU ## START ## AU: Search for updates
2019-04-23 12:27:08:045 6268 f44 AU #########
2019-04-23 12:27:08:138 6268 f44 Report *********** Report: Initializing static reporting data ***********
2019-04-23 12:27:08:138 6268 f44 Report * OS Version = 6.2.9200.0.0.131344
2019-04-23 12:27:08:138 6268 f44 Report * OS Product Type = 0x00000007
2019-04-23 12:27:08:138 6268 f44 Report * Computer Brand = VMware, Inc.
2019-04-23 12:27:08:138 6268 f44 Report * Computer Model = VMware Virtual Platform
2019-04-23 12:27:08:138 6268 f44 Report * Platform Role = 1
2019-04-23 12:27:08:138 6268 f44 Report * AlwaysOn/AlwaysConnected (AOAC) = 0
2019-04-23 12:27:08:154 6268 f44 Report * Bios Revision = 6.00
2019-04-23 12:27:08:154 6268 f44 Report * Bios Name = PhoenixBIOS 4.0 Release 6.0
2019-04-23 12:27:08:154 6268 f44 Report * Bios Release Date = 2014-04-14T00:00:00
2019-04-23 12:27:08:154 6268 f44 Report * Bios Sku Number unavailable.
2019-04-23 12:27:08:154 6268 f44 Report * Bios Vendor = Phoenix Technologies LTD
2019-04-23 12:27:08:154 6268 f44 Report * Bios Family unavailable.
2019-04-23 12:27:08:154 6268 f44 Report * Bios Major Release = 4
2019-04-23 12:27:08:154 6268 f44 Report * Bios Minor Release = 6
2019-04-23 12:27:08:154 6268 f44 Report * Locale ID = 1033
2019-04-23 12:27:08:185 6268 f44 AU <<## SUBMITTED ## AU: Search for updates [CallId = {40E65281-D4B4-4AE6-93CF-18FE5F00A282} ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}]
2019-04-23 12:27:08:185 6268 1760 Agent *************
2019-04-23 12:27:08:185 6268 1760 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdatesWuApp]
2019-04-23 12:27:08:185 6268 1760 Agent *********
2019-04-23 12:27:08:185 6268 1760 Agent * Online = Yes; Ignore download priority = No
2019-04-23 12:27:08:185 6268 1760 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"
2019-04-23 12:27:08:185 6268 1760 Agent * ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
2019-04-23 12:27:08:185 6268 1760 Agent * Search Scope = {Machine & All Users}
2019-04-23 12:27:08:185 6268 1760 Agent * Caller SID for Applicability: S-1-5-21-3061872972-298715413-1103976531-500
2019-04-23 12:27:08:200 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:247 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:247 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:247 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:247 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:247 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:247 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP9A38.tmp with dwProvFlags 0x00000080:
2019-04-23 12:27:08:263 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:263 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:388 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\v6-wuredir.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:388 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:388 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:388 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\v6-wuredir.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:388 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:388 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:403 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP9AC6.tmp with dwProvFlags 0x00000080:
2019-04-23 12:27:08:403 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:403 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:403 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:419 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:419 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:419 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:419 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:419 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:419 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP9AE6.tmp with dwProvFlags 0x00000080:
2019-04-23 12:27:08:435 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:435 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:435 6268 1760 EP Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir Client/Server URL: "https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx"
2019-04-23 12:27:08:435 6268 1760 Setup Checking for agent SelfUpdate
2019-04-23 12:27:08:435 6268 1760 Setup Client version: Core: 7.8.9200.17185 Aux: 7.8.9200.17185
2019-04-23 12:27:08:450 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\v6-wuredir.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:450 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:450 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:450 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\v6-wuredir.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:466 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:466 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:466 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP9B16.tmp with dwProvFlags 0x00000080:
2019-04-23 12:27:08:481 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:481 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:481 6268 1760 EP Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SelfUpdate URL: "https://fe2.update.microsoft.com/v11/3/win8/windowsupdate/selfupdate"
2019-04-23 12:27:08:746 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:746 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:746 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:762 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP9C30.tmp with dwProvFlags 0x00000080:
2019-04-23 12:27:08:762 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:762 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:778 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:793 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:793 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:793 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:809 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:809 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:918 6268 1760 Setup Determining whether a new setup handler needs to be downloaded
2019-04-23 12:27:08:918 6268 1760 Setup SelfUpdate handler is not found. It will be downloaded
2019-04-23 12:27:08:918 6268 1760 Setup Evaluating applicability of setup package "Package_for_KB2887537~31bf3856ad364e35~amd64~~6.2.1.6"
2019-04-23 12:27:08:949 6268 1760 Setup Setup package "Package_for_KB2887537~31bf3856ad364e35~amd64~~6.2.1.6" is not applicable
2019-04-23 12:27:08:949 6268 1760 Setup Evaluating applicability of setup package "Package_for_KB2887536~31bf3856ad364e35~amd64~~6.2.1.6"
2019-04-23 12:27:09:012 6268 1760 Setup Setup package "Package_for_KB2887536~31bf3856ad364e35~amd64~~6.2.1.6" is not applicable
2019-04-23 12:27:09:012 6268 1760 Setup Evaluating applicability of setup package "Package_for_KB2887535~31bf3856ad364e35~amd64~~6.2.1.10"
2019-04-23 12:27:09:043 6268 1760 Setup Setup package "Package_for_KB2887535~31bf3856ad364e35~amd64~~6.2.1.10" is not applicable
2019-04-23 12:27:09:043 6268 1760 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2019-04-23 12:27:14:565 6268 1760 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2019-04-23 12:27:14:565 6268 1760 PT + ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL = https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx
2019-04-23 12:27:14:565 6268 1760 Agent Reading cached app categories using lifetime 604800 seconds
2019-04-23 12:27:14:565 6268 1760 Agent Read 0 cached app categories
2019-04-23 12:27:19:807 6268 1760 PT WARNING: PopulateDataStore failed: 0x8007000e
2019-04-23 12:27:19:823 6268 1760 PT WARNING: Sync of Updates: 0x8007000e
2019-04-23 12:27:19:823 6268 1760 PT WARNING: SyncServerUpdatesInternal failed: 0x8007000e
2019-04-23 12:27:19:823 6268 1760 Agent * WARNING: Failed to synchronize, error = 0x8007000E
2019-04-23 12:27:19:901 6268 1760 Agent * WARNING: Exit code = 0x8007000E
2019-04-23 12:27:19:901 6268 1760 Agent *********
2019-04-23 12:27:19:901 6268 1760 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdatesWuApp]
2019-04-23 12:27:19:901 6268 1760 Agent *************
2019-04-23 12:27:19:901 6268 1760 Agent WARNING: WU client failed Searching for update with error 0x8007000e
2019-04-23 12:27:19:901 6268 1768 AU >>## RESUMED ## AU: Search for updates [CallId = {40E65281-D4B4-4AE6-93CF-18FE5F00A282} ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}]
2019-04-23 12:27:19:901 6268 1768 AU # WARNING: Search callback failed, result = 0x8007000E
2019-04-23 12:27:19:901 6268 1768 AU #########
2019-04-23 12:27:19:901 6268 1768 AU ## END ## AU: Search for updates [CallId = {40E65281-D4B4-4AE6-93CF-18FE5F00A282} ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}]
2019-04-23 12:27:19:901 6268 1768 AU #############
2019-04-23 12:27:19:901 6268 1768 AU All AU searches complete.
2019-04-23 12:27:19:901 6268 1768 AU # WARNING: Failed to find updates with error code 8007000e
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Secondly, looking in the event log, it appears that the system is running out of paging room. Maybe because there are now so many updates to download (or catalog)?
Here is the error in the event log:
Error ID: 2004, Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: svchost.exe (916) consumed 1815674880 bytes, firefox.exe (1896) consumed 284778496 bytes, and svchost.exe (1508) consumed 134553600 bytes.
Looking at the details, here is what it gives for mem info:
- <SystemInfo>
<SystemCommitLimit>4294430720</SystemCommitLimit>
<SystemCommitCharge>4030889984</SystemCommitCharge>
<ProcessCommitCharge>3769360384</ProcessCommitCharge>
<PagedPoolUsage>154599424</PagedPoolUsage>
<PhysicalMemorySize>4294430720</PhysicalMemorySize>
<PhysicalMemoryUsage>4208680960</PhysicalMemoryUsage>
<NonPagedPoolUsage>76775424</NonPagedPoolUsage>
<Processes>47</Processes>
</SystemInfo>
Looking on this server (virtual), there is no paging file used - I am pretty sure their IT guy though said he does not use page files on his virtual servers (cannot get him right now to confirm why).
I have also run these processes (based on a couple of articles):
DISM.exe /online /cleanup-image /Restorehealth
And it completed with "The restore operation completed successfully. The component store corruption was repaired"
I then ran the following (also suggested in an article):
sfc /scannow
That did not seem to do anything. After every step, I ran the updater again with the same error code being thrown. Note that I was not able to reboot the server after the above as it is their primary domain controller - but the above did not seem to indicate that I needed to do so.
I have mostly run out of ideas but here are a couple:- should I get their sys admin to specify a pagefile size?
- since there are SO many updates to download, is there a tool or a way to bring down a few at a time instead of having the auto updater try to figure out the whole batch?
Thanks,
Albert
Continue reading...
A client of mine asked me to look at a domain controller that is not updating properly. I found out that the updates have not been applied since mid 2015. When I run the updater manually, it comes back with error 0x8007000e. Looking in the Windows update log, I see this (I will highlight a couple entries that I think are important but don't let that sway you, I really don't know if they are the root problem or not):
2019-04-23 12:27:02:319 2804 14a8 CltUI FATAL: CNetworkCostChangeHandler::RegisterForCostChangeNotifications: CoCreateInstance failed with error 80004002
2019-04-23 12:27:02:319 2804 14a8 CltUI WARNING: RegisterNetworkCostChangeNotification: Error 80004002
2019-04-23 12:27:05:034 6268 e20 AU Triggering AU detection through DetectNow API
2019-04-23 12:27:05:034 6268 e20 AU Triggering Online detection (interactive)
2019-04-23 12:27:08:045 6268 f44 AU #############
2019-04-23 12:27:08:045 6268 f44 AU ## START ## AU: Search for updates
2019-04-23 12:27:08:045 6268 f44 AU #########
2019-04-23 12:27:08:138 6268 f44 Report *********** Report: Initializing static reporting data ***********
2019-04-23 12:27:08:138 6268 f44 Report * OS Version = 6.2.9200.0.0.131344
2019-04-23 12:27:08:138 6268 f44 Report * OS Product Type = 0x00000007
2019-04-23 12:27:08:138 6268 f44 Report * Computer Brand = VMware, Inc.
2019-04-23 12:27:08:138 6268 f44 Report * Computer Model = VMware Virtual Platform
2019-04-23 12:27:08:138 6268 f44 Report * Platform Role = 1
2019-04-23 12:27:08:138 6268 f44 Report * AlwaysOn/AlwaysConnected (AOAC) = 0
2019-04-23 12:27:08:154 6268 f44 Report * Bios Revision = 6.00
2019-04-23 12:27:08:154 6268 f44 Report * Bios Name = PhoenixBIOS 4.0 Release 6.0
2019-04-23 12:27:08:154 6268 f44 Report * Bios Release Date = 2014-04-14T00:00:00
2019-04-23 12:27:08:154 6268 f44 Report * Bios Sku Number unavailable.
2019-04-23 12:27:08:154 6268 f44 Report * Bios Vendor = Phoenix Technologies LTD
2019-04-23 12:27:08:154 6268 f44 Report * Bios Family unavailable.
2019-04-23 12:27:08:154 6268 f44 Report * Bios Major Release = 4
2019-04-23 12:27:08:154 6268 f44 Report * Bios Minor Release = 6
2019-04-23 12:27:08:154 6268 f44 Report * Locale ID = 1033
2019-04-23 12:27:08:185 6268 f44 AU <<## SUBMITTED ## AU: Search for updates [CallId = {40E65281-D4B4-4AE6-93CF-18FE5F00A282} ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}]
2019-04-23 12:27:08:185 6268 1760 Agent *************
2019-04-23 12:27:08:185 6268 1760 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdatesWuApp]
2019-04-23 12:27:08:185 6268 1760 Agent *********
2019-04-23 12:27:08:185 6268 1760 Agent * Online = Yes; Ignore download priority = No
2019-04-23 12:27:08:185 6268 1760 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"
2019-04-23 12:27:08:185 6268 1760 Agent * ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
2019-04-23 12:27:08:185 6268 1760 Agent * Search Scope = {Machine & All Users}
2019-04-23 12:27:08:185 6268 1760 Agent * Caller SID for Applicability: S-1-5-21-3061872972-298715413-1103976531-500
2019-04-23 12:27:08:200 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:247 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:247 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:247 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:247 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:247 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:247 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP9A38.tmp with dwProvFlags 0x00000080:
2019-04-23 12:27:08:263 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:263 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:388 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\v6-wuredir.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:388 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:388 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:388 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\v6-wuredir.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:388 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:388 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:403 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP9AC6.tmp with dwProvFlags 0x00000080:
2019-04-23 12:27:08:403 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:403 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:403 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:419 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:419 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:419 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:419 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:419 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:419 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP9AE6.tmp with dwProvFlags 0x00000080:
2019-04-23 12:27:08:435 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:435 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:435 6268 1760 EP Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir Client/Server URL: "https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx"
2019-04-23 12:27:08:435 6268 1760 Setup Checking for agent SelfUpdate
2019-04-23 12:27:08:435 6268 1760 Setup Client version: Core: 7.8.9200.17185 Aux: 7.8.9200.17185
2019-04-23 12:27:08:450 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\v6-wuredir.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:450 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:450 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:450 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\v6-wuredir.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:466 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:466 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:466 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP9B16.tmp with dwProvFlags 0x00000080:
2019-04-23 12:27:08:481 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:481 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:481 6268 1760 EP Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SelfUpdate URL: "https://fe2.update.microsoft.com/v11/3/win8/windowsupdate/selfupdate"
2019-04-23 12:27:08:746 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:746 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:746 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:762 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP9C30.tmp with dwProvFlags 0x00000080:
2019-04-23 12:27:08:762 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:762 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:778 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:793 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:793 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:793 6268 1760 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2019-04-23 12:27:08:809 6268 1760 Misc Microsoft signed: NA
2019-04-23 12:27:08:809 6268 1760 Misc Infrastructure signed: Yes
2019-04-23 12:27:08:918 6268 1760 Setup Determining whether a new setup handler needs to be downloaded
2019-04-23 12:27:08:918 6268 1760 Setup SelfUpdate handler is not found. It will be downloaded
2019-04-23 12:27:08:918 6268 1760 Setup Evaluating applicability of setup package "Package_for_KB2887537~31bf3856ad364e35~amd64~~6.2.1.6"
2019-04-23 12:27:08:949 6268 1760 Setup Setup package "Package_for_KB2887537~31bf3856ad364e35~amd64~~6.2.1.6" is not applicable
2019-04-23 12:27:08:949 6268 1760 Setup Evaluating applicability of setup package "Package_for_KB2887536~31bf3856ad364e35~amd64~~6.2.1.6"
2019-04-23 12:27:09:012 6268 1760 Setup Setup package "Package_for_KB2887536~31bf3856ad364e35~amd64~~6.2.1.6" is not applicable
2019-04-23 12:27:09:012 6268 1760 Setup Evaluating applicability of setup package "Package_for_KB2887535~31bf3856ad364e35~amd64~~6.2.1.10"
2019-04-23 12:27:09:043 6268 1760 Setup Setup package "Package_for_KB2887535~31bf3856ad364e35~amd64~~6.2.1.10" is not applicable
2019-04-23 12:27:09:043 6268 1760 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2019-04-23 12:27:14:565 6268 1760 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2019-04-23 12:27:14:565 6268 1760 PT + ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL = https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx
2019-04-23 12:27:14:565 6268 1760 Agent Reading cached app categories using lifetime 604800 seconds
2019-04-23 12:27:14:565 6268 1760 Agent Read 0 cached app categories
2019-04-23 12:27:19:807 6268 1760 PT WARNING: PopulateDataStore failed: 0x8007000e
2019-04-23 12:27:19:823 6268 1760 PT WARNING: Sync of Updates: 0x8007000e
2019-04-23 12:27:19:823 6268 1760 PT WARNING: SyncServerUpdatesInternal failed: 0x8007000e
2019-04-23 12:27:19:823 6268 1760 Agent * WARNING: Failed to synchronize, error = 0x8007000E
2019-04-23 12:27:19:901 6268 1760 Agent * WARNING: Exit code = 0x8007000E
2019-04-23 12:27:19:901 6268 1760 Agent *********
2019-04-23 12:27:19:901 6268 1760 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdatesWuApp]
2019-04-23 12:27:19:901 6268 1760 Agent *************
2019-04-23 12:27:19:901 6268 1760 Agent WARNING: WU client failed Searching for update with error 0x8007000e
2019-04-23 12:27:19:901 6268 1768 AU >>## RESUMED ## AU: Search for updates [CallId = {40E65281-D4B4-4AE6-93CF-18FE5F00A282} ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}]
2019-04-23 12:27:19:901 6268 1768 AU # WARNING: Search callback failed, result = 0x8007000E
2019-04-23 12:27:19:901 6268 1768 AU #########
2019-04-23 12:27:19:901 6268 1768 AU ## END ## AU: Search for updates [CallId = {40E65281-D4B4-4AE6-93CF-18FE5F00A282} ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}]
2019-04-23 12:27:19:901 6268 1768 AU #############
2019-04-23 12:27:19:901 6268 1768 AU All AU searches complete.
2019-04-23 12:27:19:901 6268 1768 AU # WARNING: Failed to find updates with error code 8007000e
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Secondly, looking in the event log, it appears that the system is running out of paging room. Maybe because there are now so many updates to download (or catalog)?
Here is the error in the event log:
Error ID: 2004, Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: svchost.exe (916) consumed 1815674880 bytes, firefox.exe (1896) consumed 284778496 bytes, and svchost.exe (1508) consumed 134553600 bytes.
Looking at the details, here is what it gives for mem info:
- <SystemInfo>
<SystemCommitLimit>4294430720</SystemCommitLimit>
<SystemCommitCharge>4030889984</SystemCommitCharge>
<ProcessCommitCharge>3769360384</ProcessCommitCharge>
<PagedPoolUsage>154599424</PagedPoolUsage>
<PhysicalMemorySize>4294430720</PhysicalMemorySize>
<PhysicalMemoryUsage>4208680960</PhysicalMemoryUsage>
<NonPagedPoolUsage>76775424</NonPagedPoolUsage>
<Processes>47</Processes>
</SystemInfo>
Looking on this server (virtual), there is no paging file used - I am pretty sure their IT guy though said he does not use page files on his virtual servers (cannot get him right now to confirm why).
I have also run these processes (based on a couple of articles):
DISM.exe /online /cleanup-image /Restorehealth
And it completed with "The restore operation completed successfully. The component store corruption was repaired"
I then ran the following (also suggested in an article):
sfc /scannow
That did not seem to do anything. After every step, I ran the updater again with the same error code being thrown. Note that I was not able to reboot the server after the above as it is their primary domain controller - but the above did not seem to indicate that I needed to do so.
I have mostly run out of ideas but here are a couple:- should I get their sys admin to specify a pagefile size?
- since there are SO many updates to download, is there a tool or a way to bring down a few at a time instead of having the auto updater try to figure out the whole batch?
Thanks,
Albert
Continue reading...