While I was gone this morning, WU did an auto update with KB4457128 (again). I came home to a system waiting on a restart. I clicked RESTART and the system is now at bld. 17134.285. There are two separate entries for KB4457128 in the update history display. One is dated 09/11/2018 (bld. 17134.254) and the other is dated 09/13/2018 (bld. 17134.285).
Last edited by jamis; 13 Sep 2018 at 16:17. Reason: added info.
I now have the results of leaving my test machine running and letting it auto-check for and install updates. Update History says KB4457128 was installed twice, once on 12th Sept. and again on the 13th September. The Event log however tells the complete story. The sequence was as follows (UK date format)...
12/09/2018 12:32:31 Event ID 44, Windows Update started downloading an update.
2018-09 Cumulative Update for Windows 10 Version 1803 for x86-based Systems (KB4457128)
12/09/2018 12:33:43 Event ID 43, Installation Started: Windows has started installing the following update:
2018-09 Cumulative Update for Windows 10 Version 1803 for x86-based Systems (KB4457128)
12/09/2018 12:33:51 Event ID 19, Installation Successful: Windows successfully installed the following update:
2018-09 Cumulative Update for Windows 10 Version 1803 for x86-based Systems (KB4457128)
(The report at 12:33:51 cannot be correct as a restart has not yet taken place to complete the install.)
13/09/2018 10:59:55 Event ID 44, Windows Update started downloading an update.
2018-09 Cumulative Update for Windows 10 Version 1803 for x86-based Systems (KB4457128)
13/09/2018 11:17:50 Event ID 43, Installation Started: Windows has started installing the following update:
2018-09 Cumulative Update for Windows 10 Version 1803 for x86-based Systems (KB4457128)
13/09/2018 18:33:43 Event ID 12, The operating system started at system time 2018-09-13T17:33:42.485483800Z.
13/09/2018 18:37:07 Event ID 19, Installation Successful: Windows successfully installed the following update:
2018-09 Cumulative Update for Windows 10 Version 1803 for x86-based Systems (KB4457128)
This second report of 'success' is the true and only successful install of KB4457128, the restart at 18:33 being an automatic restart outside Active Hours. The Event log correctly shows all the other 'Patch Tuesday' updates being successfully installed on 12th Sept. as well as the regular Defender definitions updates at other times. I have attached a filtered event log in a .zip file so you can see for yourself.
It would appear that the prematurely logged 'success' also prevented a restart being scheduled, leading to the update being downloaded and installed again the following day. This was on a machine left to its own devices with the whole process running on automatic under the control of Windows Update.
On my other machines where I manually clicked 'Check for updates' in Windows Update it too prematurely said 'successfully installed' but also said 'pending a restart'...
Cumulative Update KB4457128 Windows 10 v1803 Build 17134.285 Sept. 11 - Windows 10 Forums - post #7
...and after a restart said installed twice. In this case though I can be sure there was only the one download and install as I was watching and controlling the process manually.
Cumulative Update KB4457128 Windows 10 v1803 Build 17134.285 Sept. 11 - Windows 10 Forums - post #9
Last edited by Bree; 16 Sep 2018 at 14:54.
Interesting. Soooo, I'm a bit confused. Was the first iteration of KB4457128 somehow defective and it took a second attempt (or version) to make things right? I ask as my update history has two separate entries on two different dates for KB4457128.
No, KB4457128 was install successfully in one attempt on all the machines where I checked for updates on Tuesday 11th. What seems to have been 'defective' was just that it recorded a successful update before the install had completed and another one after the restart that finished the install.
For the machines where the check was started manually, this led to the update being listed twice in Update History, though it was only downloaded once. For the machine that was left to automatically check for updates the premature 'success' entry seems to have prevented the automatic restart required to complete the install. Windows update then repeated the download and successfully installed the following day. Either way, KB4457128 was listed as installed twice in update history.
This all seems to have changed since about the 14th though. Having ended my testing I restored my test machine's 17134.228 image and updated that to KB4457128, I have also clean-installed 1803 on another machine then updated it. MS seem to have changed something, as KB4457128 now records a successful install just the once on both those machines.
The update itself appears to be unchanged, MS seem to have just altered the way windows update reports on the successful install. There would seem to be nothing to worry about in the way of a defect in what has been installed, just a confusing glitch in the reporting mechanism.
Reminded of the old song/conundrum: "Who's keeping time with the timekeeper's keeper, while the timekeeper's out keeping time?" Cross between an elephant and a rhinocerous: elefino!
--Ed--
At about 7:30PM today, WU did an auto update with KB4100347 (a Quality Update) and was waiting on a restart. I clicked RESTART and the system is still at bld. 17134.285. KB4100347 was applied here on 08/24/18, so this must be a new version.
KB4100347 is the Intel Microcode update. This is regularly reissued as Intel release microcode for more processors. It is normal to see it listed as installed several times, each one being for a different revision. This KB does not alter any of the windows system files so the build does not change when it installs, only a Cumulative Update changes the build number.
KB4100347 Intel microcode updates for Windows 10 v1803 - September 13 - Windows 10 Forums
I had tried and failed to install KB4457128 manually.
I had to use MiniTool, which installed it successfully.
See Windows Update keeps finding an already installed cumulative update. - Windows 10 Forums
Yes, I knew this was the microcode update (again), but I was posting as this was listed as a "Quality" update, not an "Important" one (or a security update), and thus by previous definitions, WU would not have automatically done the update. The web page for the KB also did not list it as a security update. I noted that the bld. number did not change as information only. I'm glad WU did the update. I'm coming to the thought that WU will do the updates whenever MS wants it to and that it is working correctly, even though I don't understand. Thanks.
Quote
