Recent content by johnblue

Now I am going to need to find out what an Enablement Package is! :D Thanks for the tip however I am not in a hurry to start running any non-LTSC version to be honest. I am consistently shocked when I see other peoples install of Windows. The only reason why I am here is because I figured it...

Special thanks to @garlin and @hsehestedt for all of the help in answering questions about the offline updating process after ignoring it for over 10+ years. Given how long it took me to understand it I dont blame you if you didnt want to directly answer my final few questions. :-) So I went...

Using the Windows Update Catalog keyword search of "Windows 11 version 24H2" x64 2026-03 .. it returns two results: 1. March 2026 LCU 2. March 2026 Safe OS DU Since I am updating a 26100.1 image I need the February 2026 Setup DU .. agreed?

So the answer, at this time, for March 2026 is yes I will need to use the February 2026 Setup DU since there is none for March 2026, correct?

Okay .. feel like this is the last question that I have for this thread. :D Today. Patch Tuesday. At this time, since only the LCU and the Safe OS DU are listed, this means that I do not need to fetch the Setup DU from the previous month, correct?

Anyone know what keyword is needed to surface OOBE ZDP updates for 24H2 on the Windows Update Catalog website? I was able to isolate the following: # Cumulative Update https://www.catalog.update.microsoft.com/Search.aspx?q=%22Windows%2011%20version%2024H2%22%20x64%20Cumulative%20Update # Safe...

Suspected but thanks for the comments.

Also .. anyone know the backstory on why the copy and rename of bootmgfw.efi to bootx64.efi in line 688? Why two different names for the same file is probably a better question to ask.

Serious technical question. When calling:DISM /image:"c:mounted\image\here" /cleanup-image /StartComponentCleanup the option .. /ResetBaseis not used. Is that because it is not needed due to the unmount commit option doing the same thing?

An eye watering 4k lines of script code! wow. :D Thanks for sharing the link.

Thank you for the effort expended and, I agree, your code should work for best for you first and foremost. :-)

No worries .. team effort. (y) ;-)

Thanks for the reminder. (y) As mentioned at the beginning of the thread and in a couple of other places .. I am exclusively working with 26100.1.

So. :-) The way my brain is wired to learn is to actually do things instead of simply kicking off a script. I found it by manually issuing each command of the script in sequence and then checking the result. That said, I recommend that you keep using DISM in your script instead of trying to...

.. and running the code by hand on the February 2026 update you can see that UTF8 encoding matches that of WIM: