Windows 10 Hotfix Repository

Discussion in 'Windows 10' started by Tito, Oct 1, 2014.

  1. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,668
    103,485
    450
  2. Windows 10 User

    Windows 10 User MDL Guru

    Feb 2, 2017
    2,005
    122
    90
    #7042 Windows 10 User, Dec 7, 2018
    Last edited: Jul 13, 2023
    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?
     
  3. Ahsan

    Ahsan MDL Addicted

    Dec 3, 2009
    838
    171
    30
    why don't you upgrade to 17763.168 ?
     
  4. Krager

    Krager MDL Senior Member

    Jan 9, 2017
    396
    233
    10
    Yes 17763.168 (kb4469342) seems pretty solid to me, system is working well so far.
     
  5. stass

    stass MDL Junior Member

    Mar 6, 2008
    88
    9
    0
  6. Error_801

    Error_801 MDL Junior Member

    Jul 31, 2009
    87
    28
    0
    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)
     
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,668
    103,485
    450
    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
     
  8. z110110

    z110110 MDL Junior Member

    Apr 15, 2017
    54
    12
    0
    It's not a Microsoft standard program
    I never rely on DISM+
     
  9. toyo

    toyo MDL Senior Member

    Aug 14, 2009
    472
    313
    10
    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.
     
  10. KedarWolf

    KedarWolf MDL Addicted

    Mar 17, 2016
    977
    874
    30
    You had installed an older version of that CU, maybe, been a few new versions of the same CU.
     
  11. Nikos

    Nikos MDL Novice

    Jul 20, 2010
    27
    11
    0
    #7056 Nikos, Dec 9, 2018
    Last edited: Dec 9, 2018
    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.
     
  12. toyo

    toyo MDL Senior Member

    Aug 14, 2009
    472
    313
    10
    .1.10 or something from a few days ago. I think that was the latest.
     
  13. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,206
    90,780
    340
    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)
     
  14. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,668
    103,485
    450
    #7059 Enthousiast, Dec 9, 2018
    Last edited: Dec 9, 2018
    @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.
     
  15. toyo

    toyo MDL Senior Member

    Aug 14, 2009
    472
    313
    10
    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.