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

You need to login to view this posts content.

 

Got it, thanks! I'm deleting the Store on purpose because I never use it. I think you've got a really cool script, but it's a shame it's not universal. In my opinion, it is not very convenient to use because you have to use the full names of the components for removal and processing. This is not very convenient because when using a different version of the image, you have to search for all these components in the image again, which is very troublesome. I think the script shouldn't care what it's fed. Its main job is to run the script and not complain.

 

Well, this is the Dev channel, so there is no time bomb! I compiled this build version 26200.5603. Then, after a while, it was updated via the Update Center to version 26200.5622, then to version 26200.5641, and just recently it was automatically updated to version 26200.5641. According to UUP DUMP, they position it as 25H2. I have it installed on one of my computers. I'm not removing this build because I'm very interested to see what will happen in September: will MS simply change its name from 24H2 to 25H2, or will they release something new with a new kernel, as they promised at one time?

 

I am interested in trying to do the same for 24H2 as long as someone could guide how i can unpack (expand ) L1_Windows11.0-KB5043080-x64.msu and L2_Windows11.0-kb5063060-x64.msu in order to make an modded update for future use .

Regarding your script , i like it and i can use it as long as i will figure out what did you disable or remove regarding the Store in order to use it if i need to update my appx .

Today i am playing with 10.0.26100.4351 IOT to see what i can do ... but still could not unpack Windows11.0-KB5063060-x64.wim and Windows11.0-KB5063060-x64.wim

 

Try this:

Spoiler: TEXT - Original

Файл .msu, являющийся пакетом обновления Windows, можно распаковать с помощью утилиты expand или PowerShell. Также можно использовать архиватор 7-Zip для извлечения содержимого, если внутри находится CAB-файл.
Подробные инструкции:

1. 1. Использование утилиты expand (в командной строке):
   • Откройте командную строку от имени администратора.
   • Перейдите в каталог, где находится файл .msu.
   • Введите команду: expand <имя_файла.msu> -F:* <папка_назначения>. Замените <имя_файла.msu> на имя вашего файла, а <папка_назначения> на желаемую папку для извлечения.
   • Например: expand my_update.msu -F:* C:\Extracted_files.
2. 2. Использование PowerShell:
   • Откройте PowerShell от имени администратора.
   • Перейдите в каталог, где находится файл .msu.
   • Введите команду: expand-archive -Path "<путь_к_файлу.msu>" -DestinationPath "<папка_назначения>". Замените <путь_к_файлу.msu> на полный путь к файлу, а <папка_назначения> на желаемую папку.
   • Например: expand-archive -Path "C:\Updates\my_update.msu" -DestinationPath "C:\Extracted_files".
3. 3. Использование 7-Zip:
   • Откройте 7-Zip.
   • Найдите файл .msu в 7-Zip.
   • Если внутри .msu находится CAB-файл, откройте его как архив.
   • Распакуйте нужные файлы из CAB-архива.

Важно: Файлы .msu обычно содержат CAB-файлы, которые также можно распаковать с помощью 7-Zip. Если .msu содержит только один CAB-файл, то распаковка .msu напрямую через expand или PowerShell даст тот же результат, что и распаковка CAB-файла отдельно.

Spoiler: TEXT - Translation

An .msu file, which is a Windows update package, can be unpacked using the expand utility or PowerShell. You can also use the 7-Zip archiver to extract the contents if there is a CAB file inside.

Detailed instructions:

1. Using the expand utility (in the command line):
* Open the command line as an administrator.
* Go to the directory where the .msu file is located.
* Enter the command: expand <file_name.msu> -F:* <destination_folder>. Replace <file_name.msu> with the name of your file and <destination_folder> with the desired folder for extraction.
* For example: expand my_update.msu -F:* C:\Extracted_files.

2. Using PowerShell:
* Open PowerShell as an administrator.
* Go to the directory where the .msu file is located.
* Enter the command: expand-archive -Path “<path_to_file.msu>” -DestinationPath “<destination_folder>”. Replace <path_to_msu_file> with the full path to the file and <destination_folder> with the desired folder.
* For example: expand-archive -Path “C:\Updates\my_update.msu” -DestinationPath “C:\Extracted_files”.

3. Using 7-Zip:
* Open 7-Zip.
* Find the .msu file in 7-Zip.
* If there is a CAB file inside the .msu, open it as an archive.
* Extract the necessary files from the CAB archive.

Important: .msu files usually contain CAB files, which can also be extracted using 7-Zip. If the .msu contains only one CAB file, extracting the .msu directly using expand or PowerShell will give the same result as extracting the CAB file separately.

 

Juste installed, and it's running well, but M€ don't forget to bloat it...and I installed IoT entreprise. Will debloat it soon...

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You're right, the Registry Tweak Tool has long been outdated and unsuitable.

 

@SunLion Checked quite a few times PW is incorrect cannot open?

 

It's strange, why did that happen to you? Why would it suddenly stop working? Personally, I've been using RTT v.1.4.7.0 for a long time and I've never had any problems updating through Windows Update. Perhaps you are using it to delete something that shouldn't be deleted?

 

Yes, mine also says that the password is incorrect?! I wanted to ask SunLion what is the reason for this, that he uses such mind-boggling passwords ( S2}=QLl?jR%mJpyz0PnsiWzjki> ) and most importantly - why?

 

Hmm, whether it is suitable or not is all found out in testing. Personally, it does not cause me any problems at all. You think that it is hopelessly outdated and does not suit us, well, then offer it an alternative. More modern, better quality, otherwise, just talk - suitable or not suitable ...

 

Very good, but as an alternative to return the old Context Menu, you can simply add this small .reg file to your Personal Tweaks, which is what I do. The result will be the same:

Spoiler

Code:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32]
@=""