Win10 update fails

Burris · 19 Jun 2019

Product: Pavilion Desktop 590-p0xxx
Operating System: Microsoft Windows 10 (64-bit)

Win10 pro 64 1809 build 17763.503

KB5403327 won't install.

Every day the PC settings downloads and tries to install this update and fails each time requiring a reboot..

Otherwise the desktop works fine' but it's getting tiresome.

thanks

hsehestedt · 19 Jun 2019

Are you sure that KB5403327 is the correct KB number? The only other reference I can find anywhere is your posting to the HP forums on the same topic. I can't find any reference to that KB number in Google, Bing, or the Microsoft Update Catalog.

That said, you could try the Microsoft "Show or Hide Updates" Troubleshooter tool located here:

http://download.microsoft.com/downlo...owhide.diagcab

If it cannot identify a problem, you can use it to stop Windows from trying to install the update repeatedly, but it would still be nice to know what that update is to see if it is really needed.

Burris · 19 Jun 2019

Sorry...fat fingers..
KB4503327
I did try the troubleshooting..dism things and will try to hide them again.
Thank you

hsehestedt · 19 Jun 2019

Okay, you currently have cumualtive updates installed through May 14th. The cumulative update you are having difficulties with is the June 11 update.

Try blocking that one as noted, and see if when you check for updates you are offered KB4501371 (the June 18th update).

You can also obtain that update here manually:

https://www.catalog.update.microsoft...px?q=KB4501371

Also, be aware that the update that you are having difficulty with requires the Servicing Stack Update (KB4504369) from June 11 as a prerequisite. Windows update should offer it to you automatically, but you can also download and install it from here:

https://www.catalog.update.microsoft...px?q=KB4504369

Burris · 19 Jun 2019

I'll check for the stack but each time I check for updates the 3327 is the only one showing. I'll try downloading the 1371 and see what happens.

- - - Updated - - -

Stack shows installed in windows updates but not in update history.
Downloaded 1371..install failed.
Downloaded a fresh copy of 3327 install failed.

My only concern with these updates was maybe better security. If they only involved features, I can wait.

Somedays I wish I was back with Mosaic and Dos and 300 baud modems. More peaceful then.

I do appreciate your help.thanks again

hsehestedt · 19 Jun 2019

Anything getting logged in the event logs when you try to install the updates and they fail?

Burris · 20 Jun 2019

This is all I see..

File(s):
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20190619.152109.665.9.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20190619.152109.665.10.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20190619.172446.956.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20190619.172446.956.2.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20190619.195558.582.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20190619.195558.582.2.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20190619.200813.330.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20190619.200853.121.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20190619.200853.121.2.etl

0.00%7.84%15.69%23.53%31.37%39.22%47.06%54.90%62.75%70.59%78.43%86.27%94.12%100.00%

Output
----------------
DumpFile: C:\Users\Burris\AppData\Local\Temp\WindowsUpdateLog\wuetl.CSV.tmp.00001

The command completed successfully.

- - - Updated - - -

The full log went to my desktop. It is huge.I'll figure out how to post it.

hsehestedt · 20 Jun 2019

What I really meant was to open up the Event Viewer application and take a look in there at the Windows System log like this...

Right click on Start, then select Event Viewer:

From there, expand Windows Logs and then select System

Look at the time where the update failed to install to see if anything is getting logged. In addition to the System log, make sure that you also check the other logs (Setup, Application, Security).

If you are not sure when the attempted update was, then try to let it install the update again, noting the time, then open the Event Viewer.

Burris · 20 Jun 2019

Don't know if this will work. These are from the last try yesterday.

Log Name: System
Source: Service Control Manager
Date: 6/20/2019 7:47:20 AM
Event ID: 7040
Task Category: None
Level: Information
Keywords: Classic
User: SYSTEM
Computer: Burris
Description:
The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="16384">7040</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2019-06-20T11:47:20.662641800Z" />
<EventRecordID>36877</EventRecordID>
<Correlation />
<Execution ProcessID="1052" ThreadID="14204" />
<Channel>System</Channel>
<Computer>Burris</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="param1">Background Intelligent Transfer Service</Data>
<Data Name="param2">auto start</Data>
<Data Name="param3">demand start</Data>
<Data Name="param4">BITS</Data>
</EventData>
</Event>

Log Name: System
Source: Service Control Manager
Date: 6/20/2019 7:45:18 AM
Event ID: 7040
Task Category: None
Level: Information
Keywords: Classic
User: SYSTEM
Computer: Burris
Description:
The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="16384">7040</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2019-06-20T11:45:18.267945000Z" />
<EventRecordID>36876</EventRecordID>
<Correlation />
<Execution ProcessID="1052" ThreadID="1704" />
<Channel>System</Channel>
<Computer>Burris</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="param1">Background Intelligent Transfer Service</Data>
<Data Name="param2">demand start</Data>
<Data Name="param3">auto start</Data>
<Data Name="param4">BITS</Data>
</EventData>
</Event>

Log Name: System
Source: Service Control Manager
Date: 6/20/2019 7:44:33 AM
Event ID: 7040
Task Category: None
Level: Information
Keywords: Classic
User: SYSTEM
Computer: Burris
Description:
The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="16384">7040</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2019-06-20T11:44:33.815234600Z" />
<EventRecordID>36875</EventRecordID>
<Correlation />
<Execution ProcessID="1052" ThreadID="14204" />
<Channel>System</Channel>
<Computer>Burris</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="param1">Background Intelligent Transfer Service</Data>
<Data Name="param2">auto start</Data>
<Data Name="param3">demand start</Data>
<Data Name="param4">BITS</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-Time-Service
Date: 6/20/2019 7:42:35 AM
Event ID: 35
Task Category: None
Level: Information
Keywords:
User: LOCAL SERVICE
Computer: Burris
Description:
The time service is now synchronizing the system time with the time source time.nist.gov,0x9 (ntp.m|0x9|0.0.0.0:123->128.138.140.44:123) with reference id 747408000. Current local stratum number is 2.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Time-Service" Guid="{06edcfeb-0fd0-4e53-acca-a6f8bbf81bcb}" />
<EventID>35</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2019-06-20T11:42:35.884453000Z" />
<EventRecordID>36874</EventRecordID>
<Correlation />
<Execution ProcessID="4360" ThreadID="4716" />
<Channel>System</Channel>
<Computer>Burris</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData Name="TMP_EVENT_TIME_SOURCE_CHOSEN">
<Data Name="TimeSource">time.nist.gov,0x9 (ntp.m|0x9|0.0.0.0:123->128.138.140.44:123)</Data>
<Data Name="TimeSourceRefId">747408000</Data>
<Data Name="CurrentStratumNumber">2</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-Time-Service
Date: 6/20/2019 7:42:32 AM
Event ID: 37
Task Category: None
Level: Information
Keywords:
User: LOCAL SERVICE
Computer: Burris
Description:
The time provider NtpClient is currently receiving valid time data from time.nist.gov,0x9 (ntp.m|0x9|0.0.0.0:123->128.138.140.44:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Time-Service" Guid="{06edcfeb-0fd0-4e53-acca-a6f8bbf81bcb}" />
<EventID>37</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2019-06-20T11:42:32.250460900Z" />
<EventRecordID>36873</EventRecordID>
<Correlation />
<Execution ProcessID="4360" ThreadID="5976" />
<Channel>System</Channel>
<Computer>Burris</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData Name="TMP_EVENT_TIME_SOURCE_REACHABLE">
<Data Name="TimeSource">time.nist.gov,0x9 (ntp.m|0x9|0.0.0.0:123->128.138.140.44:123)</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-Power-Troubleshooter
Date: 6/20/2019 7:42:20 AM
Event ID: 1
Task Category: None
Level: Information
Keywords:
User: LOCAL SERVICE
Computer: Burris
Description:
The system has returned from a low power state.

Sleep Time: ‎2019‎-‎06‎-‎20T03:06:53.497302300Z
Wake Time: ‎2019‎-‎06‎-‎20T11:42:18.433977100Z

Wake Source: Device -USB Composite Device
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Power-Troubleshooter" Guid="{cdc05e28-c449-49c6-b9d2-88cf761644df}" />
<EventID>1</EventID>
<Version>2</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2019-06-20T11:42:20.223642700Z" />
<EventRecordID>36872</EventRecordID>
<Correlation ActivityID="{f7fa6778-8b8c-4f5f-83a7-5cbbea20df6b}" />
<Execution ProcessID="3580" ThreadID="14700" />
<Channel>System</Channel>
<Computer>Burris</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="SleepTime">2019-06-20T03:06:53.497302300Z</Data>
<Data Name="WakeTime">2019-06-20T11:42:18.433977100Z</Data>
<Data Name="SleepDuration">2313</Data>
<Data Name="WakeDuration">931</Data>
<Data Name="DriverInitDuration">547</Data>
<Data Name="BiosInitDuration">1127</Data>
<Data Name="HiberWriteDuration">0</Data>
<Data Name="HiberReadDuration">0</Data>
<Data Name="HiberPagesWritten">0</Data>
<Data Name="Attributes">1912624140</Data>
<Data Name="TargetState">4</Data>
<Data Name="EffectiveState">4</Data>
<Data Name="WakeSourceType">5</Data>
<Data Name="WakeSourceTextLength">20</Data>
<Data Name="WakeSourceText">USB Composite Device</Data>
<Data Name="WakeTimerOwnerLength">0</Data>
<Data Name="WakeTimerContextLength">0</Data>
<Data Name="NoMultiStageResumeReason">0</Data>
<Data Name="WakeTimerOwner">
</Data>
<Data Name="WakeTimerContext">
</Data>
</EventData>
</Event>

Log Name: System
Source: Service Control Manager
Date: 6/20/2019 7:42:20 AM
Event ID: 7040
Task Category: None
Level: Information
Keywords: Classic
User: SYSTEM
Computer: Burris
Description:
The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="16384">7040</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2019-06-20T11:42:20.068406400Z" />
<EventRecordID>36871</EventRecordID>
<Correlation />
<Execution ProcessID="1052" ThreadID="1104" />
<Channel>System</Channel>
<Computer>Burris</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="param1">Background Intelligent Transfer Service</Data>
<Data Name="param2">demand start</Data>
<Data Name="param3">auto start</Data>
<Data Name="param4">BITS</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-Time-Service
Date: 6/20/2019 7:42:19 AM
Event ID: 158
Task Category: None
Level: Information
Keywords:
User: LOCAL SERVICE
Computer: Burris
Description:
The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Time-Service" Guid="{06edcfeb-0fd0-4e53-acca-a6f8bbf81bcb}" />
<EventID>158</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2019-06-20T11:42:19.777896600Z" />
<EventRecordID>36870</EventRecordID>
<Correlation />
<Execution ProcessID="4360" ThreadID="4716" />
<Channel>System</Channel>
<Computer>Burris</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData Name="TMP_EVENT_TIMEPROV_INDICATED_UNSUPPORTED">
<Data Name="TimeProvider">VMICTimeProvider</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-Time-Service
Date: 6/20/2019 7:42:19 AM
Event ID: 134
Task Category: None
Level: Warning
Keywords:
User: LOCAL SERVICE
Computer: Burris
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Time-Service" Guid="{06edcfeb-0fd0-4e53-acca-a6f8bbf81bcb}" />
<EventID>134</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2019-06-20T11:42:19.777270000Z" />
<EventRecordID>36869</EventRecordID>
<Correlation />
<Execution ProcessID="4360" ThreadID="5976" />
<Channel>System</Channel>
<Computer>Burris</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData Name="TMP_EVENT_MANUAL_PEER_DNS_ERROR">
<Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
<Data Name="RetryMinutes">15</Data>
<Data Name="DomainPeer">time.nist.gov,0x9</Data>
</EventData>
</Event>

Log Name: System
Source: BTHUSB
Date: 6/20/2019 7:42:19 AM
Event ID: 34
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: Burris
Description:
The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x2491f7fffff, got 0xffffffff. Low Energy peripheral role functionality will not be available.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="BTHUSB" />
<EventID Qualifiers="32773">34</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-06-20T11:42:19.715098600Z" />
<EventRecordID>36868</EventRecordID>
<Channel>System</Channel>
<Computer>Burris</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>0x2491f7fffff</Data>
<Data>0xffffffff</Data>
<Binary>00000000030028000000000022000580000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: BTHUSB
Date: 6/20/2019 7:42:19 AM
Event ID: 18
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Burris
Description:
Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="BTHUSB" />
<EventID Qualifiers="16389">18</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-06-20T11:42:19.640302400Z" />
<EventRecordID>36867</EventRecordID>
<Channel>System</Channel>
<Computer>Burris</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Binary>00000800010000000000000012000540000000000000000000000000000000000000000000000000E00000000000 0000</Binary>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-WLAN-AutoConfig
Date: 6/20/2019 7:42:19 AM
Event ID: 10001
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: Burris
Description:
WLAN Extensibility Module has successfully started.

Module Path: C:\WINDOWS\system32\Rtlihvs.dll

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WLAN-AutoConfig" Guid="{9580d7dd-0379-4658-9870-d5be7d52d6de}" />
<EventID>10001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2019-06-20T11:42:19.428945000Z" />
<EventRecordID>36866</EventRecordID>
<Correlation />
<Execution ProcessID="3740" ThreadID="3768" />
<Channel>System</Channel>
<Computer>Burris</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="ExtensibleModulePath">C:\WINDOWS\system32\Rtlihvs.dll</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 6/20/2019 7:42:17 AM
Event ID: 131
Task Category: (33)
Level: Information
Keywords: (1024),(4)
User: N/A
Computer: Burris
Description:
Firmware S3 times. ResumeCount: 4, FullResume: 1089, AverageResume: 1081
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>131</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>33</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000404</Keywords>
<TimeCreated SystemTime="2019-06-20T11:42:17.675943800Z" />
<EventRecordID>36865</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="352" />
<Channel>System</Channel>
<Computer>Burris</Computer>
<Security />
</System>
<EventData>
<Data Name="ResumeCount">4</Data>
<Data Name="FullResume">1089</Data>
<Data Name="AverageResume">1081</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-Kernel-General
Date: 6/20/2019 7:42:17 AM
Event ID: 1
Task Category: (5)
Level: Information
Keywords: Time
User: N/A
Computer: Burris
Description:
The system time has changed to ‎2019‎-‎06‎-‎20T11:42:17.500000000Z from ‎2019‎-‎06‎-‎20T03:06:58.226002100Z.

Change Reason: System time synchronized with the hardware clock.
Process: '' (PID 4).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-General" Guid="{a68ca8b7-004f-d7b6-a698-07e2de0f1f5d}" />
<EventID>1</EventID>
<Version>2</Version>
<Level>4</Level>
<Task>5</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2019-06-20T11:42:17.500256700Z" />
<EventRecordID>36864</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="352" />
<Channel>System</Channel>
<Computer>Burris</Computer>
<Security />
</System>
<EventData>
<Data Name="NewTime">2019-06-20T11:42:17.500000000Z</Data>
<Data Name="OldTime">2019-06-20T03:06:58.226002100Z</Data>
<Data Name="Reason">2</Data>
<Data Name="ProcessName">
</Data>
<Data Name="ProcessID">4</Data>
</EventData>
</Event>