They didn't fix the Monthly Rollup package name issue i guess some MS employee was surprised that Windows 8.1's WU is not chaotic and deemed it's not acceptable so let's mess up the metadata and break the rollups chain .NET 3.5 update KB5008868 is also messed up i didn't get it via WU, and attempting to install manually gives "not applicable" i think it maybe related to the components installation format (sub-packages mum) Code: <updateComponent elevate="revision"> according to previous .NET 3.5 updates, this format is used only in dual GDR/LDR updates single branch updates use "distribution" or "install" instead "revision" (all updates since 2016 are LDR-only) KB3064209 (the only known Win7 GDR-only update) also use distribution
No but you may trick WU use NSudo to add this registry each time before running WU scan Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ApplicabilityEvaluationCache\Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20174.1.16] "ApplicabilityState"=dword:00000070 "CurrentState"=dword:00000070 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ApplicabilityEvaluationCache\Package_for_KB5008263~31bf3856ad364e35~amd64~~9600.20207.1.9] "ApplicabilityState"=dword:00000070 "CurrentState"=dword:00000070 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ApplicabilityEvaluationCache\Package_for_KB5009624~31bf3856ad364e35~amd64~~9600.20246.1.12] "ApplicabilityState"=dword:00000070 "CurrentState"=dword:00000070
I am having trouble removing .NET 3.5 Cum KB4578953 which I thought is now superseded by KB5008868 There is no permanence= in Package_for_KB4578953~31bf3856ad364e35~amd64~~6.3.1.2.mum and flag=0x20070 Code: dism /online /norestart /remove-package /packagename:Package_for_KB4578953~31bf3856ad364e35~amd64~~6.3.1.2 Deployment Image Servicing and Management tool Version: 6.3.9600.19408 Image Version: 6.3.9600.19397 Processing 1 of 1 - Removing package Package_for_KB4578953~31bf3856ad364e35~amd64~~6.3.1.2 [===========================99.7%========================= ] An error occurred - Package_for_KB4578953 Error: 0x80070032 Error: 50 The request is not supported. Is it actually superseded and if so, how do I remove it? Also, Could it be because I don't have the superseded KBs 2978122 and 4054999 included in my image which keeps 4578953 from being uninstalled?
After further investigation, the 2022-01 .NET 3.5 updates (KB5008868 or KB5008891) require one of these .NET 3.5 updates to be already installed: KB2894852, KB2966826, KB3037576, or the previous last rollup KB4578953 it was not installing for me, because i reinstalled Windows 8.1 on new machine two months ago, and have not found the passion to fully update it yet i just installed latest SSU + WU fix KB3172614 + .NET 4.8 KB4486105 + WMF 5.1 summary for the weirdness of 2022-01 .NET 3.5 updates: - require previous updates - do not fully replace last rollup KB4578953 - check for KB2919355 presence before .NET 3.5 feature packs (all previous updates including 4.x ones check for .NET packs first)
I got a tip from komm and he said maybe a few lang-packs were missing from 5008868 as compared to 4578953 which was possibly the reason 4578953 could not be removed. He suggested I try to disable feature NetFx3, remove 4578953 and then enable the feature again That worked, but I haven't managed to get NetFx3 enabled again. Code: c:\>Dism /online /enable-feature /featurename:NetFx3 /All /Source:d:\sources\sxs /LimitAccess Deployment Image Servicing and Management tool Version: 6.3.9600.19408 Image Version: 6.3.9600.19397 Enabling feature(s) [==========================100.0%==========================] Error: 14107 One or more required members of the transaction are not present. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log I tried enabling from \sources\sxs using the RTM, Update1 and Update3 ISOs and from the control panel 'programs and features' and they all indicated missing file(s). Edit: had to reinstall 4578953, otherwise re-enabling NetFx3 will fail.
As a learning experience, I finally managed to remove 4578953 with help from komm. In my case, /resetbase deleted files that later need to be present in order to remove 4578953. Since those missing files are no longer included in the latest .NET35 cuml 5008868, you are pretty much out of luck trying to remove the previous 4578953 cuml, even with 5008868 installed, without knowing what's missing. There is a trick with KUC though, that involves installing the LDR updates for .NET35 (BF_Packages). In my case, I had 12 LDR updates that needed installing. Doing that restored the needed files and I was able to remove 4578953.
Did you have KB4054999? it's the last Rollup that include all .resources_ components for all languages (hence needed for non en-us systems) it should fix KB4578953 absence later Rollups included en-us resources only and now the KB5008868 included only the updated en-us resources for this month
I only use en images with no other lang-packs. At the time I did not have KB4054999 on my system, but that was one of the things I tried installing and If I recall correctly, I still couldn't remove 4578953 with 4054999 installed. I believe the problem had something to do with a missing msil_system.configuration_b03f5f7f11d50a3a_6.3.9600.17226_none_462b765efaccb4fe.manifest