I don't see any point in installing the outdated NET Framework 3.5. Because after installing the OS, it will automatically update to NET Framework 4.1. That's why I never install NET Framework 3.5. It would be interesting to see your version of the script. What do you think should be removed from my script and what should be added? If you want, send me your Created.cmd file in a private message.
Everyone has different tastes. I adjusted it to my needs. Some applications require .NET Framework 3.5. That's why I asked. 2.Does the update work?
It should work. I can't check, because I was building image 26220.7271 with this script for myself. When there will be an update for it then I will check it.
How to upgrade to 25H2 from 24H2? I have downloaded windows11.0-kb5068861-x64.msu (3.5GB), left it inside \Win_Optimizer_v.1.6.5\Data\UUP\Insider. but in my two tests, what I obtained was still 24H2 26100.1742. am I missing anything? I wish it was 25H2 26100.7171. I am moving it upto \Win_Optimizer_v.1.6.5\Data\UUP and testing , , ,
Here's an example: when using the image install.wim 26100.1742 IoT Enterprise LTSC image and moving the Windows11.0-KB5066383-x64.msu and Windows11.0-KB5070307-x64.msu updates to the “UUP” folder, we get version 26220.7271 IoT Enterprise LTSC:
Thanks, Still in testing. it's really long (only 69,0% done in one hr) Processing 1 of 1 - Adding package Package_for_ServicingStack_7010~31bf3856ad364e35~amd64~~26100.7010.1.8 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_7010 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.2454 Image Version: 10.0.26100.1742 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.7171.1.16 [===========================69.0%======== ]
Well, I can't help you there. The rest depends on the performance of your PC. In my case, on my PC configuration, the whole process of install.wim image processing by the script takes about 15 minutes.
Thank sainfo for clarification. I am hunting for Windows11.0-KB5070307-x64.msu and Windows11.0-KB5066383-x64.msu. Update: My last one has got 26220.7171. (still NOT 26220.7271). This run took 25-min. Its install.wim is bulky. 4.64 GB, much bigger than 24H2 2.34 GB. Its installed OS is 12.0 GB. NOT too bad. Outlook has been removed. edge and all classic apps working fine. (snipping paint calculator notepad MS-DOS). For somehow, its C: drive name is Win10. NOT Win11. can be renamed easily.
================== 2xH2_Creator_14.5 ================== Updated to 26x00.7171 https://forums.mydigitallife.net/th...ic-legacy-windows.86552/page-120#post-1872013 Enjoy!
You did wonders this time, SunLion. The size of the install.wim file is under 4.00GB without using NtLite. Thank you wholeheartedly for your unique work.