I'll wait until you're done treating the latest CU and flash update, I always forget to save the output but when I compared it to yours was exactly the same. I might have saved it to a .txt file but don't think so.
I just reported it here: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-279#post-1418018
btw... did you patch the boot.wim using w10ui 4.4? 1709 patched was fine, but LTSB 1607's boot.wim batch updated can not use.
I may have found the issue. I was integrating the KB4090007 CU instead of just the microcode update. Making an ISO now. Will report the progress and results.
Yeah, you're right. I wonder why it's called a CU in the first listing. I downloaded the second one this time.
@KedarWolf The "feature updade to windows 10, version 1709" suggests you're on a previous build. How do you install the newly created iso (Win10_16299.309_2018-03-13.iso)? It doesn't matter from what source the files come from (UUP>ISO, ISO, ESD>ISO), as long as they're not corrupted or created with errors, during the conversion process.
I posted the output as well. It was a 16299.15 ISO as I used made from the OEM 16299.15 OEMRET CONSUMER CLIENT ESD
That's how you created the install media, i asked how you install it, do you boot from the USB (clean install) and delete/format all existing system partitions or do you run setup from a running windows (inplace upgrade)
Yes, clean install, deleted the four GPT partitions and created them again in the Windows installer. And after making the ISO I checked to see all the updates were installed and they were.when only the EN-GB language pack as I used that ESD file.
Right after installing run this command in an elevated cmd: Code: dism /online /get-Packages /format:table >"%userprofile%\Desktop\Packages.txt" And post the output here in code tags
Last part is hard to understand . Did you install a lang pack after the update integration (that would explain the offered updates)?