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.
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.
@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]
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.
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.
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.
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.
@donmiller what I mean was I W10UI those updates into an image, I install said image, I get this version of FxP. No restarts.
That's another way to do it, and sounds like it works for you. I haven't used W10UI to install updates to Windows or an image. I just use DISM command lines. I'll have to familiarize myself with W10UI