[DISCUSSION] Windows 10 Final Build 19041>>>19045 (PC) [20H1>>>22H2 vb_release]

Discussion in 'Windows 10' started by Enthousiast, Dec 10, 2019.

  1. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream

    Dec 21, 2012
    5,710
    6,268
    180
    Maybe you mis-clicked, 21H1 vs. 21H2? The former is 19043, the latter 19044.
     
  2. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    42,832
    78,835
    450
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream

    Dec 21, 2012
    5,710
    6,268
    180
    *shrugs*

    Maybe he re-used the old directory with the old Enablement package still in it.
     
  4. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    42,832
    78,835
    450
    I dunno, all is possible, i just gave up.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. farmers

    farmers MDL Senior Member

    Nov 20, 2011
    331
    159
    10
    I searched for 19044 builds only, then selected 19044.1706 Feature Update.
     
  6. nosirrahx

    nosirrahx MDL Expert

    Nov 7, 2017
    1,134
    540
    60
    Not sure if it was 1739 or the previous update but MS has re-fixed the failure to sleep issue some NUC systems were having.
     
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    42,832
    78,835
    450
    #9407 Enthousiast, May 24, 2022
    Last edited: May 24, 2022
    (OP)
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream

    Dec 21, 2012
    5,710
    6,268
    180
    Hope it won't take that long every time, now. Is the Standalone background engine still out?
     
  9. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    42,832
    78,835
    450
    Afaik, all is back to normal now.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. donmiller

    donmiller MDL Addicted

    Jun 4, 2016
    621
    404
    30
    #9410 donmiller, May 25, 2022
    Last edited: May 25, 2022
    The Windows 10 Feature Experience Pack (FxP) does not appear to be upgrading as expected.

    Yesterday, I updated from 19044.1708 to 19044.1739 and the Feature Experience Pack stayed at version 120.2212.4170.0 (instead of upgrading to 120.2212.4180.0). I rebooted a couple of times, and cleaned up component store with DISM and it still didn't upgrade.

    I checked to make sure that none of the following updates were installed as described in:
    https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-675#post-1720650

    KB4601906
    KB5000967
    KB5001460
    KB5003345
    KB5004393

    I finally got to 120.2212.4180.0 after an inplace-upgrade, componenent store cleanup, and reboot. But it seemed a bit tedious.
     
  11. shhnedo

    shhnedo MDL Expert

    Mar 20, 2011
    1,405
    1,881
    60
    @donmiller
    Code:
    1/8: defender-dism-x64.cab
    2/8: Windows10.0-KB5003791-x64_PSFX.cab [Enablement]
    3/8: windows10.0-KB5007401-x64_crit_du.cab
    4/8: windows10.0-KB5010524-x64_setup_du.cab [Setup DU]
    5/8: windows10.0-KB5011577-x64_safeos_du.cab [WinPE]
    6/8: Windows10.0-KB5013624-x64-NDP48.cab [NetFx]
    7/8: Windows10.0-KB5014023-x64.cab [LCU]
    8/8: Windows10.0-KB5014035-x64.cab [SSU]
    upload_2022-5-26_2-35-0.png
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. donmiller

    donmiller MDL Addicted

    Jun 4, 2016
    621
    404
    30
    #9412 donmiller, May 26, 2022
    Last edited: May 26, 2022
    As I said, I was finally able to get the correct Feature Experience Pack installed. I think that the component store on 19044.7608 was corrupted. So reinstalling Windows 19044.1288, and then updating to 19044.1739 got me to FxP 120.2212.4180.0. It's all good now.

    EDIT: Upon further inspection, I'm seeing that KB5004393 was actually embedded in 19044.1288. That would explain the FxP not updating.
     
  13. nosirrahx

    nosirrahx MDL Expert

    Nov 7, 2017
    1,134
    540
    60
    #9413 nosirrahx, May 26, 2022
    Last edited: May 26, 2022
    Noticing the same thing. Just installing SSUs and CUs for a while now on a few systems and Feature Experience Pack is out of date. Seems I am stuck on Windows Feature Experience Pack 120.2212.3920.0.

    EDIT: going to do an in place install and see what happens.
     
  14. nosirrahx

    nosirrahx MDL Expert

    Nov 7, 2017
    1,134
    540
    60
    In-place install fixes the issue but I am seeing that this is very inconsistent. I checked a 2 other PCs and one of them is on 120.2212.4180.0 as it should be but another does not even have Feature Experience Pack listed at all on system information even though it is on 19044.1739.
     
  15. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    42,832
    78,835
    450
    #9415 Enthousiast, May 26, 2022
    Last edited: May 26, 2022
    (OP)
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. donmiller

    donmiller MDL Addicted

    Jun 4, 2016
    621
    404
    30
    In a previous post, there is mention that if you have a manually installed FxP, you might have to remove it, and reboot, for the FxP version to update after installing a later SSU/LCU combo (like 1737/1739). Here is the link to that post:
    https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-675#post-1720650

    You could try a batch file with the following lines to remove traces of previously installed FxPs:
    wusa /uninstall /kb:4601906 /quiet /norestart
    wusa /uninstall /kb:5000967 /quiet /norestart
    wusa /uninstall /kb:5001460 /quiet /norestart
    wusa /uninstall /kb:5003345 /quiet /norestart
    wusa /uninstall /kb:5004393 /quiet /norestart

    Plus I'm suspicious that KB5007401 (found in UUPDUMP) might affect this issue, but I'm only speculating here...

    I changed my version key to 19041.1 and then did an inplace-upgrade to 19044.1288. Then I installed 1737/1739 and rebooted. It stayed on 120.2212.3920.0 until I cleaned up component store and then rebooted:
    DISM /Online /Cleanup-Image /StartComponentCleanup

    'Hope this helps.
     
  17. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    14,189
    72,526
    340
    KB5007401 is .NET 3.5 update, not related
     
  18. donmiller

    donmiller MDL Addicted

    Jun 4, 2016
    621
    404
    30
    I wasn't sure about this. Thanks for the information.
     
  19. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    42,832
    78,835
    450
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...