Slimdown11 – turn Windows 11 or LTSC 2024 into classic/legacy Windows

i will do some test now with 22621... looks more easy close to 10 .. i can not sleep ...hahahah

 

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?

 

You need to login to view this posts content.

 

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 ...

 

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 ...

 

We are very happy that everything is great with you. But we would also like to be happy in our reality, in the 24H2 version. How can we use this knowledge base for our purposes?

 

The new update of the 24H2 is totally different , it can be done but takes more time to modify first 1742 and the one you update , before the new update replace the old one and it was easy to modify the mum files updating only what you want.

I manage to do same for 22621 cause it still has the same layout of updating the mum (and manage the same procedure with 678 packages in services ...which is wow and fast ..) but i give up because of the User Choice Protection (my a....) which changes all the modification you would like to make to registry , applications , pdf and even to add your favorite browser .

i will not continue with windows 11 cause i do not find it yet ready for day to day operation specially when i am going away with my job 6 months , it is hard to fix problems .

Maybe latter when i will have time i will play again ... but not for a while ...

 

You need to login to view this posts content.

 

Can you explain how to use these .mum files?

TIA.

 

SunLion

which test can I do? with what script version?

I am eager to see if new change works on SD10, in size, in functionality.


Thanks,

 

I am glad that i give a reason for people to start modifying the mum files , as in my opinion is the easiest way to debloat as you follow microsoft way but delete from the mum what it does not make you happy ..
As a basic information , màke sure you ðo not remove the basic packages included in each edition ...
I will be back after 10 days from my cruise in the morning and hope i will find more people bringing some input and specially to find a way for 24H2 after you remove user choice the Store it does not update anymore ..it works but the downloads are blocket by this new clever (stupid in my opinion) decision from Microsoft that they want to force you update only ussing theyr stupid update ..
Have a nice weekend and hope to hear good news soon