The CU and ssu were handled by UUP the last few weeks, the former one too. To be able to install the jan. 3. 2018 CU by WU you need a regkey to be present, the qualitycompat regkey. It's the same for both x86 and x64, but on my mainsystem i installed the jan. 3. 2018 CU by MSU and the ssu is not installed.
Thanks, I have already figured out those details about the CU. I am only mentioning the SSU that I find its behaviour unusual. To clarify this matter even more, it did not cause any problems.
You're right (nice find)- the latest SSU doesn't include permanence="permanent" in it's .mum file (making it uninstallable). previous SSU: Code: <package identifier="KB4054022" releaseType="Update" restart="possible" selfUpdate="true" permanence="permanent"> <parent buildCompare="EQ" integrate="separate" disposition="detect"> latest SSU: Code: package identifier="KB4058702" releaseType="Update" restart="possible" selfUpdate="true"> <parent buildCompare="EQ" integrate="separate" disposition="detect">
Might want to put some notes about W19UI 3.7 vs 4.1 difference in the description post. Which one do I want for LTSB 2016?
Thanks for your detailed reply @abbodi1486 I am not entirely clear what is the meaning of CU is handled by UUP instead of WU, although I read this from you here and in few other places which we both follow. This may be because I use mostly WSUS and less WU. I use WU only to double check for consistency with WSUS, like in the situation of Security Only patches for the other older OS and choose only what is available on WSUS and WU at the same time. On WSUS, the CU KB4056892 and SSU KB4058702 come as decoupled and not bundled. This may be because WSUS uses traditional BITS or in my case DO set to 99. Before asking more questions, I guess I should go back to your older posts linked in you post and the replies over there for clarification. If you can provide more information or additional relevant links to this subject being discussed in the past, I would appreciate it a lot.
delivery.mp.microsoft.com/filestreamingservice have been used for insider builds and store apps since RTM 10240 i think is just a delivery datacenter, it can provide full or partial content maybe some sort of telemetry to evaluate upgrade/update compatibility, or just a restriction from Microsoft to forces users to enable telemetry generated WindowsUpdate.log on 16299 shows that a lot of device info is checked with update search Code: ProtocolTalker DeviceAttributes: App=WU;AppVer=10.0.16299.15;AttrDataVer=29;BranchReadinessLevel=CB;CurrentBranch=rs3_release;DeviceFamily=Windows.Desktop;FirmwareVersion=6.00;FlightRing=Retail;InstallationType=Client;InstallDate=1515360924;InstallLanguage=en-US;IsDeviceRetailDemo=0;IsFlightingEnabled=0;OEMModel=VMware Virtual Platform;OEMName_Uncleaned=VMware, Inc.;OSArchitecture=x86;OSSkuId=48;OSUILocale=en-US;OSVersion=10.0.16299.15;PonchAllow=0;ProcessorManufacturer=GenuineIntel;TelemetryLevel=1;UpdateManagementGroup=2;WuClientVer=10.0.16299.15;
For my understanding, normally how many number of update files (msu/cab) in place to W10UI? I guess 3 but, Plz guide me. TIA
For 16299.15 to be updated to 16299.192: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-254#post-1401604