Maybe i was not explaining in the right way : First i remove the packages with dism command , (or Toolkit_v13.7) and the list i show you is the general list for all the core, pro, ltsc which i use it Second i use some prerequisite setup files with NTlite paid in order to reduce and make reg changes Third i use Winreducer to clean the left over and add some tweaks for speed , security and stability .. Everyone is free to use any of the ways ... this are my ways , like it or not ... I am not here to judge anyone as i had some bad experience before and i left the forum for a while , because some people just talk and judge instead of giving help , as this is the main reason why we are here on this knowledge forum . As i said from the beginning , i am just a normal guy , collecting and learning from this forum how to make a stable , safe and lite version of windows , as i manage in my way since 2007 . Thanks and God Bless you all...
as i made before custom updates for windows 10 , last one did it last week , i would like to know if someone have a clue how to avoid installing on an update a specific package Example : Code: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved."> <assemblyIdentity name="Microsoft-Windows-EditionPack-Core-Package" version="10.0.26100.4202" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> <package identifier="Microsoft-Windows-EditionPack-Core" releaseType="Feature Pack"> <update name="1f7d4a23a5421d808344b0e767cd6a8f"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Win2-MSXML6-Feature" version="10.0.26100.3624" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="a268519c0dba6407387434dd5376c8bb"> <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3"> <mum2:noAutoMerge /> </mum2:customInformation> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-All-Client-Ge-Beta-Version-EKB-Package" version="10.0.26100.4202" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="017db9b3d2d84badc56c70bbd5452e05"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Desktop-BCDTemplate-Client-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="30216fc1cfad5e362e77e795e233ca54"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Internet-Browser-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="30fa5e666c33b022e89f1847d91e8071"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-NetFx3-OC-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="a0533726923739b66e429ed866733ab4"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-NetFx4-US-OC-Package" version="10.0.26100.4202" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="09f59eca91676e87c2981297087eb548"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-PhotoBasic-Package" version="10.0.26100.3912" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="4adcf748ed2ba1e95f745a9656835fd9"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Printing-LocalPrinting-Home-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="4261451b8fcdcaeb4eb124c451d3b4f0"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-SecureStartup-Basic-Package" version="10.0.26100.4202" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="5a969c6b50d3fdfc687d69c32d6ae67b"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-SMB1-Package" version="10.0.26100.4202" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="56cfc4fe803d0ec437a31a7d18e95832"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-SMB1Deprecation-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="1faa976a33c07b6bf27c2970976a29ab"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-IIS-WebServer-Package" version="10.0.26100.4202" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="a0b6e5ae00e8fe168ba89533abd7f340"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-IIS-WebServer-AddOn-Package" version="10.0.26100.4202" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="6da022bc5a599dc918d1f28b37bfd9f5"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Browser-Package" version="10.0.26100.3624" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="7c46aeb48a4e512282f2bfc1365afbee"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-MSMQ-Client-Home-Premium-Package" version="10.0.26100.4202" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="7c598aad9dacde61f5988107c55da1c0"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-NetFx3-WCF-OC-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="a3ef0f91a5e67285cd823c3118c4dc25"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-NetFx4-WCF-US-OC-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> </package> </assembly> I modified like this : Code: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved."> <assemblyIdentity name="Microsoft-Windows-EditionPack-Core-Package" version="10.0.26100.4202" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> <package identifier="Microsoft-Windows-EditionPack-Core" releaseType="Feature Pack"> <update name="1f7d4a23a5421d808344b0e767cd6a8f"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Win2-MSXML6-Feature" version="10.0.26100.3624" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="017db9b3d2d84badc56c70bbd5452e05"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Desktop-BCDTemplate-Client-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="30fa5e666c33b022e89f1847d91e8071"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-NetFx3-OC-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="a0533726923739b66e429ed866733ab4"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-NetFx4-US-OC-Package" version="10.0.26100.4202" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="09f59eca91676e87c2981297087eb548"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-PhotoBasic-Package" version="10.0.26100.3912" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="4adcf748ed2ba1e95f745a9656835fd9"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Printing-LocalPrinting-Home-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> </package> </assembly> And this was updated and i was not using anymore remove pack with Dism command . I can do it also for Windows 11 , but there are too many packages to take in consideration in order to be modified
For Windows 11 24H2, Dism or Toolkit, from the perspective of reducing size, it basically cannot achieve the expected goal. Because MS packets are interwoven together, they cannot be processed as easily with commands as before.
I think it mainly uses them. And what difference does it make, in the grand scheme of things, what methods NTLite uses to perform its tasks? The main thing is that they perform the tasks set before this program. The only thing is, you need to work with this program very, very carefully, without fanaticism, so as not to harm the future image. In general, there is nothing new here: without certain knowledge and experience, it is better not to get involved in this topic at all. This applies to programs, scripts, and operating systems. If the user does not have certain experience working with operating systems, it is better to stick with something like Windows 7 and not mess around...
In general, in my opinion, Windows itself is simply an amazing system as a project. It's just a shame that MS doesn't work for the benefit of the user, but pursues its own corporate goals. Hence the unreasonably bloated OS distribution. Which, in all fairness, could be reduced by at least half without harming the system itself. IMHO
I would also like to know how to do this. Do you edit update.mum? I was curious about the message in your script to replace any .mum files before proceeding with the update. Thanks for your help!
This was the main reason i modify every release of W10UI in order to have the opportunity to modify the mum files before update To modify 26100 is a little tricky , cause you need to modify also the base of 1742 which is installing ... it can be done but takes time to dig for the files after they are expanded before start the update process.. For the moment i give up using HOME edition because it is not booting ... even the original one ... maybe there is something with my laptop .. After my holiday i will start to dig more because i found the way how to remove the packages easier .. Code: "Windows Core Edition" name="Microsoft-Windows-Foundation-Package" name="Microsoft-Windows-EditionSpecific-Core-Package" Microsoft-Client-License-Platform-Upgrade-Subscription-Core-Package Microsoft-Client-License-Platform-Windows-Upgrade-Package Microsoft-Windows-Help-ClientUA-Client-Package Microsoft-Windows-Security-SPP-Component-SKU-CoreSingleLanguage-License-Package Networking-MPSSVC-Rules-HomePremiumEdition-Package Server-Help-Package.ClientHomePremium name="Microsoft-Windows-Client-Desktop-Required-Package" name="Microsoft-Windows-Client-Desktop-Required-WOW64-Package" name="Microsoft-Win4-Feature" name="Microsoft-Win4-WOW64-Feature" name="Microsoft-Windows-Client-Features-Package" name="Microsoft-Windows-Client-Features-WOW64-Package" name="Microsoft-Windows-EditionPack-Core-Package" Microsoft-Windows-Internet-Browser-Package Microsoft-Windows-Browser-Package Microsoft-Windows-MSMQ-Client-Home-Premium-Package Microsoft-Windows-MSMQ-Client-Home-Premium-WOW64-Package Microsoft-Windows-COM-MSMQ-Package Microsoft-Windows-SMB1-Package Microsoft-Windows-SMB1Deprecation-Package Microsoft-Windows-IIS-WebServer-AddOn-Package Microsoft-Windows-IIS-WebServer-Package Microsoft-Windows-NetFx4-WCF-US-OC-Package Microsoft-Windows-NetFx3-WCF-OC-Package Microsoft-Windows-SecureStartup-Basic-Package name="Microsoft-Windows-EditionPack-Core-WOW64-Package" name="Microsoft-Windows-RegulatedPackages-Package" Microsoft-Windows-WebcamExperience-Package Microsoft-Windows-WebcamExperience-Package-WOW64-Package Microsoft-Windows-WinSATMediaFiles-Package name="Microsoft-Windows-RegulatedPackages-WOW64-Package" name="Microsoft-Windows-Not-Supported-On-LTSB-Package" name="Microsoft-Windows-Not-Supported-On-LTSB-WOW64-Package" name="Microsoft-Windows-Required-ShellExperiences-Desktop-Package" name="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package" i just need to fill up the packages which can be removed without many issues...
Thanks for responding. Enjoy your vacation! I hope you share your discoveries upon your return. Cheers
I'm updating your .mum files to Windows 10 version 5917. I hope I did everything correctly... Let's see what happens...
Yes, these are really great applications, but as far as I understand, they cannot be included in the shell of our Integrator in the same way as we included the install_wim_tweak.exe application?
My goal is to be fast, small in size, and try to delete any conflicts, including updating functions. windows11 24H2 26100， At present, the image is unfolded, and the C drive is about 4.2GB (note that it is not a compressed system drive), which is completely sufficient for ordinary users.
Very interesting, I would like to look at your complete tool for working with the image, to test it on 24H2 ...
Hi @balanadi So, I finished editing the .mum files and I'm testing them. With version 19044_EnterpriseS, using the modified .mum files, I got these results: - Captured CurrentBuild = 19044 (image CurrentBuild.png) - KB5003791 was installed (image Packages.png) - But in the end it shows as 19041.5917 and not 19044.5917 as it should be (image ListINFO.png) I still don't know where this can be fixed... But the positive effect was on the image size: - Without using the modified .mum files: install.wim = 3,768,882 KB (image Files2.png) - Using the modified .mum files: install.wim = 3,178,994 KB (image Files.png) I'm still going to test the installation in VirtualBox... Confirmed. Shows 19041.5917 when installed (image VBoxTest.png) If you can help me with this, I would be very grateful! Here is the package with the modified files: 19041.5917_mum.7z In psw
I forget to tell you that ... sorry , I removed also the enablement from the modified mum ... the fix is this : Code: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved."> <assemblyIdentity name="Microsoft-Windows-EditionPack-Professional-Package" version="10.0.19041.5678" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" /> <package identifier="Microsoft-Windows-EditionPack-Professional-en-US" releaseType="Language Pack"> <parent disposition="detect"> <assemblyIdentity name="Microsoft-Windows-EditionPack-Professional-Package" version="10.0.19041.5678" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </parent> <update name="4022694452405df4e5c77d173c415045"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-NetFx3-OC-Package" version="10.0.19041.4842" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="284b538631400412906f5288c424c8b2"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-NetFx4-US-OC-Package" version="10.0.19041.4842" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="3bae9b785577f06f8d43acacef762e5b"> <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3"> <mum2:noAutoMerge /> </mum2:customInformation> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Product-Data-21h2-EKB-Wrapper-Package" version="10.0.19041.3636" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="1c0e6f10d3b27ad37acf6be7ab5303a5"> <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3"> <mum2:noAutoMerge /> </mum2:customInformation> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Product-Data-EKB-Wrapper-Package" version="10.0.19041.3636" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="1cea2dad1090379f3dd3eda1bb001145"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Enterprise-Desktop-Shared-Package" version="10.0.19041.5915" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> </package> </assembly> do not forget to modify also the language mum !! I am playing with 22621 and it is similar to windows 10 ..left 678 packages only in the same way like we do it here ... BUT ....there is a BUT also and gives me a headache User Choice Protection is blocking Windows Sore from updating ... and i am nervous because i can not find a fix for that ...