skip wim2swm is to prevent errors in the process for when the wim is already <4GB, wim2esd will always be able to run.
I wonder if they are offering these to reduce the chances of FPs that have been fixed since the main build was finalized.
KB4023057 = Sediment Pack = Windows Update Resetter = Upgrade Enabler = Remediation Shell = Update Health Tools = Reusable UX Interaction Manager it's Microsoft way of reverting the users "tampering" with WU, so they can continue pushing updates regadless
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?