@abbodi1406 meant that a CU can be re-offered because they are managed by UUP now. It has nothing to do with the install of windows itself.
Why do I get this error with the UUP ISO with W10UI v4.4? Error: 769 Compression is disabled for this volume. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Why integrating old flash MS Catalog says its superseded by kb4074595 also does kb4077944 "Dynamic Update" is needed for integration. cant find info about it on catalog
In KB4074595 Update Details the update replaces the following updates including KB4056887 was Jan-2018 flash patch. but if you integrated KB4074595, WU still push KB4056887 to your system. so i decided do not integrate both of them and wait Mar flash patch comming.
Which Windows 10 ISO do you extract for the sources folder etc. to use in W10UI v4.4? When I make one from the UUP files I get an error 'Compression not enabled' and I think the 'Clean Image' and 'Reset Base' doesn't work.
It doesn't matter if you use correctly converted UUP>ISO or official MVS iso's. My example is from extracted 16299.15 OEMRET client MVS iso + Enterprise (+N) indices exported to it.
KB4092077 is CU, can be safely installed or ignored you also need to hide Update Assistant tool KB4023814
thanks abbodi, about KB4023814, atm I dont get that kb. I means dont show in wu. Currently running windows 10 1703 so maybe I can confirm about this update is "upgrade" to new windows version? Code: KB4023057 upgrade KB4033631 upgrade KB4056254 upgrade KB4073543 upgrade KB4023814 upgrade
@abbodi1406 could let the enable netfx3 feature be the first step if enable .net framework 3.5? because now using w10ui 4.4 to patch ltsb 1607 10.14393 the step is: 1:servicing stack 2:cumulative 3:.netfx3 4:cumulative (re-patch twice)
netfx3 sets the pending flag which prevent image cleanup (if activated or possible) the cumulative reinstall will only add netfx3 related components
Is this Reset PC feature still broken in insider builds after 1709? And is it known why it is broken?
It's not broken the porpose of the feature is to uninstall updates and revert to fresh OS install when you resetbase the OS and remove rtm components, how do you expect the feature to work in that case?
after successfully installing on the 10th, today offered again with the same kb number KB4092077 on the 13th. previous kb number is different but same 15063.936. now even though it is installed, was offered again to install with KB4092077 which on the previous 10 already installed. what's wrong with microsoft? what else also receive update notice windows 1703? Spoiler: success install at 10th Spoiler: Offered again today in 13th