@Enthousiast Where are you downloading all your install .cab files from? Also, I see some of what I was getting in 8.4 during cleanup. The echo box message from the 20% complete looks like it's hidden and I can't tell what that dism was for. Spoiler Code: ============================================================ Resetting OS image base ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.329 Image Version: 10.0.19041.450 [===== 10.0% ] [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.329 Image Version: 10.0.19041.450 [=========== 20.0% ] The operation completed successfully. ============================================================ Adding .NET Framework 3.5 feature ============================================================
Okay, I thought you were downloading the cab files directly from somewhere to save you from downloading the bigger msu files. Like the .NET 48 cab file.
CAB is inside the MSU and is not really smaller: MSU: Code: Name: windows6.1-kb4571729-x64_62b8672a50cebb4bfcd4fb16e18a39ab472a5269.msu Size: 364804372 bytes (347 MiB) CRC32: AE1C474F CRC64: 0D1B8A11FD9369AE SHA256: 064EF223BEA8120C4A6AA4BE2FD1F84A4D4235B5390F5026DA824F5B3642C3FC SHA1: 62B8672A50CEBB4BFCD4FB16E18A39AB472A5269 BLAKE2sp: 7A8EC88E9C8D7B29FE9620F3F271223B18F90A24488D4FE514E5F95E4E4F5E8B CAB (extracted from MSU): Code: Name: Windows6.1-KB4571729-x64.cab Size: 365236354 bytes (348 MiB) CRC32: 130B9CC1 CRC64: FE2C22C05B92E9E6 SHA256: F8E45F9979A7D9F80F6BB4DBD16790DF59A5F0CB5147E575A3FFAB1F8931D638 SHA1: A4E4A71804EB19D8D750BE79DE2598DE551BCB25 BLAKE2sp: C75E699A14F88F3EE0B247A679BB81EF493C24C8B4904C6B406F86559F069AED CAB is even bigger CABs can be directly download at UUP dump, only not the dotnetfx cu and flash updates
Ahhh yes, I was relating my mistaken thinking to the WMF 5.1 files I have for Win7 and thought cab files were smaller, but never checked. So what's the advantage of using the cab files with W10UI? Code: Windows6.1-KB3191566-x64.msu 68054745 Windows6.1-KB3191566-x64.cab 22131780
When there is one cab, like the du for sources (is cab only), i extract all to cab, for unity in the logs
Okay I see now what was confusing me about the 2 dism calls in the "Resetting OS image base" part of W10UI. I was under the impression that /resetbase actually did the Component Cleanup compression stuff too and always thought only /resetbase option was needed to handle everything. Is this not the case? Code: 2020-08-14 15:48:06, Info DISM DISM.EXE: Executing command line: "u:\$W0\ADK_6\amd64\DISM\dism.exe" /English /NoRestart /ScratchDir:"d:\cab_1193" /image:"d:\W10UImount_6511" /Cleanup-Image /StartComponentCleanup 2020-08-14 15:53:16, Info DISM DISM.EXE: Executing command line: "u:\$W0\ADK_6\amd64\DISM\dism.exe" /English /NoRestart /ScratchDir:"d:\cab_1193" /image:"d:\W10UImount_6511" /Cleanup-Image /StartComponentCleanup /ResetBase ============================================================ Resetting OS image base ============================================================ 15:48 Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.17763.1397 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.17763.1397 [==========================100.0%==========================] The operation completed successfully. ============================================================ Adding .NET Framework 3.5 feature ============================================================ 15:53 . .
= cleanup by compressing superseded components removes superseded components entirely but @abbodi1406 made W10UI so that with 1903 and up, it doesn't completely run /resetbase when selected, it leaves the CU stuff intact, else resetpc will be broken.
So if resetbase is specified, why are superseded files being compressed to only be deleted afterwards since I'm using 1607 and 1809?
It should only delete them when /resetbase is used in W10UI, afaik. On <1903 builds it will break the resetpc option.
I thought you said on 1903 and up, it gets broken. I don't have a problem with Reset PC being broken because I never use it. Backups are much better IMHO. The ini file states that component cleanup must be set to 1 in order to use resetbase. Why not just allow resetbase by itself, if a broken Reset PC is unimportant to the user?
No, i said for all under 1903, it will break resetpc, but for 1903 and up @abbodi1406 made it so that resetbase will skip CU components, so it won't break and there were some other psfx related reasons, iirc. /resetbase is an addition to the /cleanup-image dism command. /cleanup-image can run without /resetbase, not the other way around.
I did not mean resetbase by itself, I meant instead of running 2 separate commands only use the one that included the resetbase option. One command instead of 2.
Component Cleanup compression does not occur in builds prior to 1903. The 2 calls to dism occur because it is a workaround to allow resetbase in an offline image: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-251#post-1396708
That post was about the workaround for the disabling of resetbase, a few weeks after 15063 (1703) was released. On 1809 and up, when resetbase is enabled, and ran, it breaks resetpc, that's why the new workaround was introduced on 1903 (and because psfx updates already do some sort of rebasing), to do the resetbase for the other components (flash/dotnetfx) and exclude the CU ones.
Aside from the info, @AeonX linked at, there are still two options, because one offers only compressing of superseded components, takes longer and slightly less decreasing of wim size, and the other offers full resetbase, faster and slightly more decreasing of wim size, all depending on the amount of superseded components.
The problem with broken resetpc does not come since 1607 (or maybe even before) where is the reg trick DisableResetbase = 0 necessary to do the ResetBase? And the new workaround in 1903 was to avoid breaking future CU installations: https://forums.mydigitallife.net/threads/abbodi1406s-batch-scripts-repo.74197/page-39#post-1530461 From 1903 onwards ResetBase is no longer needed for Cumulative Updates but is needed for other updates. Although this will break future CU installation. So the workaround used by @abbodi1406 was to use the reg tweak SupersededActions = 3 to do CBS delta-compress of the superseded components. So from what I understand they are not removed but compressed. The /ResetBase done afterwards may be to mark the updates as permanent as explained in the other link I posted. More information here: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-419#post-1532957
@AeonX And still the resetbase option, when ran with 1809 will brake resetpc and cleanup won't. that's all i need to know about it all
Sorry for being dense, I'm new to this... If I get the latest localized LTSC iso and want to integrate all available updates using W10UI, do I need to download the x64 SSU, CU, flash, dotnet and LP files from this post only? Is this enough?