Insider KB5040557 Windows 11 Insider Dev build 26120.1340 (24H2) - Aug. 5

fg2001gf11F · Aug 7, 2024

JGToy said:
@fg2001gf11F

Used those options, Cleanup / ResetBase set to 1 and it was almost 3GB less.

Question though... Do you know of any downside on doing it?

None that I know of.
It is supposed to affect only superseded components, and they just get compressed not deleted.
I don't have any more details on what exactly they do.
It doesn't make much difference for me, because all the USB flash I used for clean install are 32GB. It could be an issue when using 8GB USB flash.
Anyway, in both cases I have to split the install.wim into install.swm and install2swm if it is above 4GiB when I use FAT32.

JGToy · Aug 7, 2024

fg2001gf11F said:
None that I know of.
It is supposed to affect only superseded components, and they just get compressed not deleted.
I don't have any more details on what exactly they do.
It doesn't make much difference for me, because all the USB flash I used for clean install are 32GB. It could be an issue when using 8GB USB flash.
Anyway, in both cases I have to split the install.wim into install.swm and install2swm if it is above 4GiB when I use FAT32.

View attachment 103450

View attachment 103451

Thanks for the input!

I do not have space problem either (have 6 SSD 2TB each), but it is more about making it smaller.

fg2001gf11F · Aug 7, 2024

JGToy said:
Thanks for the input!

I do not have space problem either (have 6 SSD 2TB each), but it is more about making it smaller.

I wish they came up with a quicker way of building the ISO, the converter takes way too long.

rseiler · Aug 7, 2024

fg2001gf11F said:
I wish they came up with a quicker way of building the ISO, the converter takes way too long.

You mean faster even after making the change for Cleanup and Resetbase? I don't know about on a modern rocket system, but on an older steam-powered one, not adjusting those two settings adds a LOT of time relative to the way that it used to be, say, last year. Those extra 3GB take a lot of extra time to process and write. I also wonder if it affects time installing Windows (I doubt it, but it's possible).

I don't know why they made the change in the first place. All I could find about changing them back is that it's usually not recommended for "non-retail builds" but should be fine if you are "not going to switch your branch to retail or release preview." I'm not quite sure what this retail/non-retail stuff is getting at.

BTW, the "setup.exe /product server" mystery is now solved. It was because I had "Skip_TPM_Check_on_Dynamic_Update.cmd" active. That never used to be a problem but now is (for ISOs). I hope the WU CU issue which set me on this path in the first place was a fluke. I guess I'll see next week.

fg2001gf11F · Aug 8, 2024

rseiler said:
You mean faster even after making the change for Cleanup and Resetbase? I don't know about on a modern rocket system, but on an older steam-powered one, not adjusting those two settings adds a LOT of time relative to the way that it used to be, say, last year. Those extra 3GB take a lot of extra time to process and write. I also wonder if it affects time installing Windows (I doubt it, but it's possible).

I don't know why they made the change in the first place. All I could find about changing them back is that it's usually not recommended for "non-retail builds" but should be fine if you are "not going to switch your branch to retail or release preview." I'm not quite sure what this retail/non-retail stuff is getting at.

BTW, the "setup.exe /product server" mystery is now solved. It was because I had "Skip_TPM_Check_on_Dynamic_Update.cmd" active. That never used to be a problem but now is (for ISOs). I hope the WU CU issue which set me on this path in the first place was a fluke. I guess I'll see next week.

Glad you could get "setup.exe /product server" working.
I think they are making it more difficult to run Windows Update on machines that don't meet the requirements. Most of the known hacks no longer work.
Machines that meet the requirement are pretty cheap now days anyway.

As for the time to Build the ISO, there is no difference using those 2 options Cleanup and Resetbase or not.
It takes too long one way or the other, the whole process used by the uup converter adding the Apps and then processing the updates is way too long.
That is added to the time it takes to download all the required files which can vary depending on the download speed of the service provider.
It would be much easier and quicker if we could download an ISO already built.
Unfortunately, that is not the case with uupdump.

JGToy · Aug 8, 2024

As for the time to Build the ISO, there is no difference using those 2 options Cleanup and Resetbase or not.
It takes too long one way or the other, the whole process used by the uup converter adding the Apps and then processing the updates is way too long.
That is added to the time it takes to download all the required files which can vary depending on the download speed of the service provider.
It would be much easier and quicker if we could download an ISO already built.
Unfortunately, that is not the case with uupdump.

On another machine (older one) I downloaded an iso of Office 2024 (for test purpose) from those free site and it took almost 1 hour for about 3.15 GB but I think that was more related to the host.

Revenge · Aug 8, 2024

Iam still using Dev Build 23606.1000 that will expire at 15 of September.

What happens if i let it end?

PS: Every time i updated to a new version, i got issues, like very slow build, so i always revert back to this version.

Mooly · Aug 8, 2024

fg2001gf11F said:
I use Minitool Partition Wizard to expand the Recovery partition when I need to.
After I shrink the C: volume partition I expand the recovery using the free space created at the end on the C: volume and then reboot.
I assume AOMEI can do the same. Good luck.

I muddled through as a first time partition shuffler but it had its moments

Used AOMEI and took a few minutes to realise that I couldn't just move the partition at will. I had to move the Dell partition first (which is one I created originally, its not an OEM one) and then move the recovery partition. I took the opportunity to increase its size at this point to 1.5GB.

So it looks like this now:

The above shows the C drive back at its original size but that is where the fun and games started. I like to see partitions appear as exact numbers in File Explorer (This PC) and it 'aint always easy to get right. Anyhow I though I would use AOMEI to expand the partition into now unallocated space rather than using Windows Management Console and although it seemed easy enough I was told step #1 of the process would be to turn off Bit locker. Up to this point there had been no issues.

I let it go ahead and it seemed to take a long time (about ten minutes) to complete which was puzzling but then as soon as I opened File Explorer all became clear, Bit Locker Off is not like 'Suspend'. I had lost access to the second drive. Bit Locker off meant it has decrypted the drive which is why it took so long.

Bit Locker off on C and D here and F and M locked out.

Now what... well fortunately I had squirred away the keys and so could unlock them. It also took me a moment to realise that you also have to enable 'Auto Unlock this Drive' so it opens correctly each time without a key.

Bitlocker on the main drive was off at this point and so was re-enabled. All this means the recovery keys are now different and so new records had to be made and I also remembered they are available on my MS account. I took the opportunity to clean all the old keys up (delete them) and made sure the current ones replaced them.

I do wonder if I had used the Disk Management Console whether this would have happened. I guess it would if Bit locker has to be off to alter a partition size.

And back to the OS which was a repair install and I find I still have the 7.85GB in disk cleanup that seems not to delete. Would that be expected from a repair install... I don't know. Is that clue as to what is happening I wonder.

Anyhow, bit of a learning curve all in all.

fg2001gf11F · Aug 8, 2024

Mooly said:
I muddled through as a first time partition shuffler but it had its moments

Bit locker is sure an extra complication for resizing the Volumes.
I don't use it.

Mooly · Aug 8, 2024

fg2001gf11F said:
Bit locker is sure an extra complication for resizing the Volumes.

Yes, it certainly did work out that way but having said that it was still all a 'good learning experience' and very interesting.

rseiler · Aug 8, 2024

Point of information: I looked at several recent Lenovo laptops to see how a major vendor sets the recovery partition these days.

Size: 2GB

fg2001gf11F · Aug 8, 2024

rseiler said:
Point of information: I looked at several recent Lenovo laptops to see how a major vendor sets the recovery partition these days.

Size: 2GB

When I do a clean install, I prepare the partitions in advance for the size I want.
The size of the recovery partition made by windows setup default is too small and may run out of space after a few updates.
I use this as found on a MS site. I boot from the installation media and go to command prompt.

UEFI/GPT-based hard drive partitions

learn.microsoft.com

Deployment lab sample scripts

The following scripts are used in the lab.

learn.microsoft.com

rem == CreatePartitions-UEFI.txt ==
rem == These commands are used with DiskPart to
rem create four partitions
rem for a UEFI/GPT-based PC.
rem Adjust the partition sizes to fill the drive
rem as necessary. ==
diskpart
select disk #
clean
convert gpt

rem == 1. System partition =========================
create partition efi size=260
rem ** NOTE: this size will also work for Advanced Format 4KB sectors drives,
format quick fs=fat32 label="System"
assign letter="S"
rem == 2. Microsoft Reserved (MSR) partition =======
create partition msr size=128
rem == 3. Windows partition ========================
rem == a. Create the Windows partition ==========
create partition primary
rem == b. Create space for the recovery tools ===
rem ** Update this size to match the size of
rem the recovery tools (winre.wim)
rem plus some free space.
shrink minimum=2000
rem == c. Prepare the Windows partition =========
format quick fs=ntfs label="Windows"
assign letter="W"
rem === 4. Recovery Tools partition ================
create partition primary
format quick fs=ntfs label="Recovery Tools"
assign letter="R"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
list volume
exit

Shutdown and reboot from the installation media and proceed to install.

brummyfan · Aug 9, 2024

I have switched to this build from RP build and it's working fine, it runs faster.

Brink · Aug 9, 2024

KB5041871 Windows 11 Insider Dev build 26120.1350 (24H2) - Aug. 9

Windows Blogs: Source: Check Windows Updates UUP Dump: 64-bit ISO download: https://uupdump.net/selectlang.php?id=377a7b26-456f-488a-8382-48061fc9c877 ARM64 ISO download: https://uupdump.net/selectlang.php?id=5b2e43db-1567-4539-93b8-58905a58acab...

www.elevenforum.com