What is this Preview of Cumulative Update for .NET Framework 3.5 and 4.7.2 for Windows 10 Version 1809 for x64 that now appears in WU?
Security Update for Adobe Flash Player for Windows 10 Version 1809 for x64-based Systems (KB4477029) Update for Windows 10 Version 1809 for x64-based Systems (KB4465664) Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4467708) Update for Adobe Flash Player for Windows 10 Version 1809 for x64-based Systems (KB4462930)
Not quite correct Current list for 1809 updates = https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-352#post-1488250 Code: SSU: KB4470788 (17763.164) Flash: KB4471331 CU DotnetFX: KB4469041 CU KB4469342: (17763.168.1.10) Integration order and progress: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-353#post-1488492
Today got served KB4469342 on Retail even though it was already installed (with DISM). I am pretty sure WU did the same with a previous update that I also manually installed. It doesn't even ask for a reboot, it just looks to download it, check for installed state and then I guess, be happy about it. You'll get the KB listed in the "normal" WU list afterwards. This is what the Event Viewer is saying: "Initiating changes for package KB4469342. Current state is Installed. Target state is Installed. Client id: UpdateAgentLCU." "Package KB4469342 was successfully changed to the Installed state." Unsure why WU does this.
I have the same "problem" with toyo. The difference is that I have integrated CU and SSU with W10UI 5.6. OS: Win 10 LTSC x64 17763.1 + SSU kb4470788-x64 + CU kb4469342-x64 (17763.168.1.10). I had the same "problem" with Win10 LTSB 14393.
UUP side effects and in 1809 they added LCU reservicing feature meaning, Update Stack (aka Update Orchestrator) check and initiate LCU reinstall whenever you install new feature or language, or possibly any servicing operation previously, only WU would offer and install LCU if you installed new components (e.g. .NET 3.5)
@abbodi1406 On my main system, which got all the different 17763.167 and 17763.168 CU versions, i didn't get 17763.168.1.10 re-offered but on my test install based on this integration, it gets offered 17763.168.1.10 again. I just noticed W105.6 doesn't re-integrate the normal CU after enabling dotnetfx3: Code: Enabling feature(s) [==========================100.0%==========================] The operation completed successfully. ============================================================ Reinstalling .NET cumulative update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17763.1 Image Version: 10.0.17763.168 Processing 1 of 1 - Adding package Package_for_KB4469041~31bf3856ad364e35~x86~~10.0.1.2251 [==========================100.0%==========================] The operation completed successfully.
So it could have been me turning On (and later Off) the Windows Hypervisor Platform feature? I played a bit with TPM and VBS and ultimately decided they don't do anything useful for my use case and ditched them. And then WU "reinstalled" the update.