Can anyone upload the features on demand parts 1 & 2 from msdn? or an svf? I.E. en_windows_10_features_on_demand_part_1_version_1809_updated_sept_2018_x64_dvd_a68fa301.iso and en_windows_10_features_on_demand_part_2_version_1809_updated_sept_2018_x64_dvd_6b49dcfa.iso I can find part one but part two i can't. Note to mods: Please do not move this. It only gets thrown in and ignored.
If a clean install (or an inplace upgrade from 17134) is done, the CU kb4464330 appears immediately, may be that CU is no longer paused or that "pause" only applies specifically to some HP machines.
Ok found it. Didn't notice that link. part_2 has a package or two that part one doesn't for remote admins.
It seems nothing has been paused at the updates level, never seen any official announcement, only indirect info. The CU/SSU is still available at UUP and WU.
https://forums.mydigitallife.net/posts/1472204/ Maybe that MS support agent was referring to the CU being paused (as I said before) specifically on some HP (and DELL) machines.
Interesting thing, the Twitter Accounts of the Insider Team was quite active until last Friday. Since then their Twitter Accounts have been silent.
For Enthousiast Could you please answer my query If you have the time The post is no: 2067 as your knowledge & experience is much valued by me & many others thank you
Yes but it's not necessary for usb creation when upgrading from 17134.345, just update the iso to 17763.55 by using @abbodi1406 his W10UI and put the uptodate iso on the desktop of the current install and open it in explorer ("mount"), run setup.exe. PS: Would also work with extracted ISO (unpacked to a folder) or burned dvd(9).
Well I don't have the problem if to update my main system for now. Windows 1809 doesn't allow me to do it: "0xc190010-0x4001e the installation failed in the second_boot phase with an error during pre oobe operation". 0xc190010 should be a driver problem? I can however clean install with all drivers I also have on my main system and 1809 works stable until now. The only difference is that my main system is on a Samsung Evo SSD with Magician installed. Running MS SetupDiag gives me no error. Quite weird.