@ytb222, Even KB3176938 number is same for build 103 and 105 but they are different SHA1 and size. A few days ago I updated to 103 with it (old) and on yesterday I updated again with it (new).
The insider CU kb3176938 = 14393.103 but lacked some language dependend files. This new CU with the same kb nr = 14393.105 and seems to have a full packages of language files. I just got this new CU offered on WU, installing atm.
Yes unfortunately, that's expected, W10UI is designed to detect updates by there KB numbers not sub-version either use dism to install the new package like Prosto said or goto Control Panel - Programs and Features - Installed Updates, and uninstall KB3176938
Integrating it to a boot.wim with the former CU "KB3176938" already in it: Code: An error occurred - Package_for_RollupFix Error: 0x80070032 Error: 50 The request is not supported.
Why? For testing purposes (i just as well could have tested it with the winre.wim (all updates have state: installed)) For creating an uptodate/working windows install iso Etcetc....
Well if they didn't fix that, and released it public and WSUS, and ignored the feedbacks and forum posts about it, I guess it's about to be SHTF. Everything on my network stays at 14393.82 until this is resolved. Edit: got a chance to test it, .103 breaks SYSVOL connectivity, but bypassing it straight to .105 doesn't. The machines I had tested .103 on had to be in-place upgraded using the 14393 ISO to clear it up.
Thank you, this works perfectly Now I was finally able to finish writing and testing a script blocking such update