That's probably why i didn't get it offered on WU (17763.346), i thought i saw it on UUP at the release time of the dotnetfx CU, on UUP, but it was .346
I need glasses Code: [HEADER] CHECKING WINDOWS RETAIL RELEASE CHANNEL [ 13 ] Architecture: amd64 [ INFO ] NAME : Cumulative Update for Windows 10 Version 1809 (17763.348) [ INFO ] BUILD: 17763.348 [ INFO ] UUPID: 2f42f148-0417-44ab-a12c-102aa6b95234 [ 14 ] Architecture: x86 [ INFO ] NAME : Cumulative Update for Windows 10 Version 1809 (17763.348) [ INFO ] BUILD: 17763.348 [ INFO ] UUPID: e780ec3b-6065-4d50-9b3e-e083a09593fb [ 15 ] Architecture: arm64 [ INFO ] NAME : Cumulative Update for Windows 10 Version 1809 (17763.348) [ INFO ] BUILD: 17763.348 [ INFO ] UUPID: 6cb84f84-2c75-4b9c-81d1-bdf9ef4fc08e [ USER ] [N]ew Search or [B]ack ?:
So here's what I ended up integrating using W10UI: 1/6: Windows10.0-KB4470788-x64_SSU_164.cab 2/6: Windows10.0-KB4480056-x64_DotNet_Jan2019.cab 3/6: Windows10.0-KB4482886-x64_DU.cab 4/6: Windows10.0-KB4482887-x64_CU_Mar19.cab 5/6: Windows10.0-KB4486553-x64_DotNet_Mar19.cab 6/6: Windows10.0-KB4487038-x64_Flash_Fev19.cab Result on a test windows 10 pro VM:
This explanation is accurate for .NET Framework updates. However if we look at WSUS (or Catalog I suppose) and KB4482887, which is 2019-02 CU for Windows 10 1809 and is an Update (non-security), we find that KB4482887 replaces in metadata Security Updates like KB4487044. I understand that the replacement also happens at the package name, but in this case it happens in metadata as well. So this rule of non-security update does not replace security update in metadata is not applied consistently across the board.
That's a post from 2016, you can find the latest W10UI here: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-105#post-1216064 And here is all @abbodi1406 has to offer: https://forums.mydigitallife.net/threads/abbodi1406s-batch-scripts-repo.74197/#post-1343297