Thanks, unfortunately I will not be able to create updated cabs, as my computer has gone AWOL, meaning broke. I'm typing this on my Android tablet, and using it to update the update Lists (ulz) for WUD (which is extremely awkward to do.) Unless there's a app that will allow me to create cabinet files, I won't be able to create cabs for awhile sadly.
Hard Drive failure, can hear it constantly clicking when it's trying to read and write. Luckily I have a backup of my data on my external hard drive, as I always make backups every month. It will be awhile until I buy a SSD for my system. I have released updated fake cab files, which are zip renamed to cab. I don't know if this will work, but it was the only way to update.
I made a cab from the unzipped files, using cabmaker, and now test running it: Code: ============================================================ [1] Target (x86): "D:\W10UI\19041_Work_x86_US" [2] Updates: "D:\W10UI\19041.1_Updates_x86" [3] DISM: "Windows 10 ADK" [4] Enable .NET 3.5: YES [5] Cleanup System Image: NO [7] Update WinRE.wim: YES [8] Install.wim selected indexes: 1 / [K] Keep indexes: Selected [M] Mount Directory: "c:\W10UImount_24848" [E] Extraction Directory: "c:\W10UItemp_2694" ============================================================ Change a menu option, press 0 to start the process, or 9 to exit: Code: ============================================================ Running W10UI v9.2 ============================================================ ============================================================ Extracting files from update cabinets (.cab) *** This will require some disk space, please be patient *** ============================================================ 1/9: defender-dism-x86_TEST.cab [Setup DU] 2/9: windows10.0-kb4562830-x86__20H2_EP_681.cab [Enablement / EdgeChromium] 3/9: Windows10.0-KB4580325-x86_Flash.cab [Flash] 4/9: windows10.0-kb4586858-x86_DU_SafeOS.cab [WinPE] 5/9: Windows10.0-KB4598481-x86_SSU_740.cab [SSU] 6/9: windows10.0-kb4599861-x86_DU_Sources_785.cab [Setup DU] 7/9: Windows10.0-KB4601050-x86-NDP48_CU_4330.6.cab [NetFx] 8/9: Windows10.0-KB4601319-x86_PSFX_LCU_804.1.4.cab [LCU] W10UI recognizes it as setup du now. ps, your file was a .zip, after renaming to .cab it's not recognized at all by W10UI.
Thanks for testing, I had a feeling that it wouldn't work but I had to try. Hopefully it won't be to long before I can provide real updated defender cabs. I will now remove the test versions for both x64 and x86.
It looks like 2021-02 Servicing Stack Update for Windows 10 Version 1507 KB4601390 and 2021-02 Servicing Stack Update for Windows 10 Version 1607/Server 2016 KB4601392 all versions have been removed. Can someone please confirm and provide possible reasons.
gone from catalog. too. It could have to do with this: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-585#post-1644218 Maybe something is not correct for the future plans to finally package the ssu with the LCU in one package, for which the feb ssu is a prerequisite?
https://forums.mydigitallife.net/members/rcstar6696.874338/ Is there any update on when the 21H1 Enablement Package will be released to Insiders ?
Thanks for replying so quickly. If you remember our posts not long ago about other updates, KB4601390/KB4601392 are what I call "expired" updates, using WSUS terminology while normally they get removed at the same time from WU and Catalog. I am aware of the discussion to which you pointed and you are likely right about the reasons behind the Microsoft action. On the other hand, we have an out of band CU for 1909 which may indicate a bunch of other issues still to be identified with the 2021-02 releases in general.
Why would you want to install it so desperately? It will be on WU when needed, it's just a WU settings reset/preparation update. ps, that file set is just an example, probably not even for 20H2, i just posted an example.
My Plans I am running 1909 Plan to Update to 2004 (19041) 1909 Out of Support soon. 20H2 (19042) Update to 21H1 (19043) Dev_Channel Waiting to Test "Sun Valley"
It is not typical to configure the use of Express updates in WSUS, although Microsoft recommended this configuration a while ago. From my experience it is more reliable not to use the Express files, but full update files, which are the same with the regular .cab files. Is this the first time when we have a documented SSU failure? I don't remember any other upfront buggy SSU. There were few instances when there were v2 for SSUs, but those were released long after the original release and were only improved versions, not meant to fix obvious faults.
Express updates is the only option for regular WU 1903 built-in servicing stack (and two released SSUs) were causing WinPE updating to fail 1507 & 1607 (x86) has known issue were you cannot offline integrate CU they don't want to fix it
It is being reported that KB4023057 has been released BUT not showing up on WU. Is there a Download for it yet ?