Slimdown10 – turn Windows 10 22H2 or LTSC 2021 into classic/legacy Windows

Yes, modifying the winsxs folder is difficult and can result in a non-operational system.

I continue to research these possibilities, but so far I have not received any convincing answers...

 

Retain the following files and folders

\Windows\WinSxS\amd64_microsoft-windows-deployment_*
\Windows\WinSxS\amd64_microsoft-windows-g..ntservice.resources_*_zh-cn_*
\Windows\WinSxS\amd64_microsoft-windows-international-core_*
\Windows\WinSxS\amd64_microsoft-windows-p..ing-lpdprintservice_*
\Windows\WinSxS\amd64_microsoft-windows-p..ntservice.resources_*_zh-cn_*
\Windows\WinSxS\amd64_microsoft-windows-p..rtmonitor.resources_*_zh-cn_*
\Windows\WinSxS\amd64_microsoft-windows-p..ting-lprportmonitor_*
\Windows\WinSxS\amd64_microsoft-windows-printing-powershell_*
\Windows\WinSxS\amd64_microsoft-windows-security-spp-ux_*
\Windows\WinSxS\amd64_microsoft-windows-servicingstack_*
\Windows\WinSxS\amd64_microsoft-windows-shell-setup_*
\Windows\WinSxS\amd64_microsoft-windows-tapicore.resources_*_zh-cn_*
\Windows\WinSxS\amd64_microsoft-windows-tapicore_*
\Windows\WinSxS\amd64_microsoft-windows-unattendedjoin_*
\Windows\WinSxS\amd64_microsoft-windows-userdeviceregistration_*
\Windows\WinSxS\amd64_microsoft.vc80.*
\Windows\WinSxS\amd64_microsoft.vc90.*
\Windows\WinSxS\amd64_microsoft.windows.c..-controls.resources_*_5.82.*_zh-cn_*
\Windows\WinSxS\amd64_microsoft.windows.c..-controls.resources_*_6.0.*_zh-cn_*
\Windows\WinSxS\amd64_microsoft.windows.common-controls_*_5.82.*
\Windows\WinSxS\amd64_microsoft.windows.common-controls_*_6.0.*
\Windows\WinSxS\amd64_microsoft.windows.gdiplus_*
\Windows\WinSxS\amd64_microsoft.windows.i..utomation.proxystub_*
\Windows\WinSxS\amd64_microsoft.windows.isolationautomation_*

\Windows\WinSxS\wow64_microsoft-windows-printing-powershell_*
\Windows\WinSxS\wow64_microsoft-windows-tapicore.resources_*_zh-cn_*
\Windows\WinSxS\wow64_microsoft-windows-tapicore_*

\Windows\WinSxS\x86_microsoft.vc80.*
\Windows\WinSxS\x86_microsoft.vc90.*
\Windows\WinSxS\x86_microsoft.windows.c..-controls.resources_*_5.82.*_zh-cn_*
\Windows\WinSxS\x86_microsoft.windows.c..-controls.resources_*_6.0.*_zh-cn_*
\Windows\WinSxS\x86_microsoft.windows.common-controls_*_5.82.*
\Windows\WinSxS\x86_microsoft.windows.common-controls_*_6.0.*
\Windows\WinSxS\x86_microsoft.windows.gdiplus_*
\Windows\WinSxS\x86_microsoft.windows.i..utomation.proxystub_*
\Windows\WinSxS\x86_microsoft.windows.isolationautomation_*

\Windows\WinSxS\Manifests\amd64_microsoft-windows-com-dtc-runtime_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-coreos-revision_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-deployment_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-enhancedstorage-adm_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-explorer_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-g..ntservice.resources_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-i..national-core-winpe_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-international-core_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-p..ing-lpdprintservice_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-p..ntservice.resources_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-p..rtmonitor.resources_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-p..ting-lprportmonitor_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-printing-powershell_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-r..-service.deployment_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-security-spp-ux_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-servicingstack_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-setup_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-shell-setup_*
\Windows\WinSxS\Manifests\amd64_microsoft-windows-unattendedjoin_*
\Windows\WinSxS\Manifests\amd64_microsoft.vc80.*
\Windows\WinSxS\Manifests\amd64_microsoft.vc90.*
\Windows\WinSxS\Manifests\amd64_microsoft.windows.c..-controls.resources_*_5.82.*_zh-cn_*
\Windows\WinSxS\Manifests\amd64_microsoft.windows.c..-controls.resources_*_6.0.*_zh-cn_*
\Windows\WinSxS\Manifests\amd64_microsoft.windows.common-controls_*_5.82.*
\Windows\WinSxS\Manifests\amd64_microsoft.windows.common-controls_*_6.0.*
\Windows\WinSxS\Manifests\amd64_microsoft.windows.gdiplus_*_1.0.*
\Windows\WinSxS\Manifests\amd64_microsoft.windows.gdiplus_*_1.1.*
\Windows\WinSxS\Manifests\amd64_microsoft.windows.i..utomation.proxystub_*
\Windows\WinSxS\Manifests\amd64_microsoft.windows.isolationautomation_*
\Windows\WinSxS\Manifests\amd64_microsoft.windows.systemcompatible_*
\Windows\WinSxS\Manifests\amd64_policy.8.0.microsoft.vc80.*
\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.*
\Windows\WinSxS\Manifests\wow64_microsoft-windows-printing-powershell_*
\Windows\WinSxS\Manifests\wow64_microsoft.windows.gdiplus.systemcopy_*
\Windows\WinSxS\Manifests\x86_microsoft.vc80.*
\Windows\WinSxS\Manifests\x86_microsoft.vc90.*
\Windows\WinSxS\Manifests\x86_microsoft.windows.c..-controls.resources_*_5.82.*_zh-cn_*
\Windows\WinSxS\Manifests\x86_microsoft.windows.c..-controls.resources_*_6.0.*_zh-cn_*
\Windows\WinSxS\Manifests\x86_microsoft.windows.common-controls_*_5.82.*
\Windows\WinSxS\Manifests\x86_microsoft.windows.common-controls_*_6.0.*
\Windows\WinSxS\Manifests\x86_microsoft.windows.gdiplus_*_1.0.*
\Windows\WinSxS\Manifests\x86_microsoft.windows.gdiplus_*_1.1.*
\Windows\WinSxS\Manifests\x86_microsoft.windows.i..utomation.proxystub_*
\Windows\WinSxS\Manifests\x86_microsoft.windows.isolationautomation_*
\Windows\WinSxS\Manifests\x86_microsoft.windows.systemcompatible_*
\Windows\WinSxS\Manifests\x86_policy.8.0.microsoft.vc80.*
\Windows\WinSxS\Manifests\x86_policy.9.0.microsoft.vc90.*

 

A very concise commentary on the proposed material ...

I don't quite understand what you're talking about? What did you mean: for the system to work properly, this is the only thing that can be left in folder WinSxS or are you suggesting that you remove it from it?

 

left in folder WinSxS,Others can try to delete

 

Got it, thanks, we'll edit WinSxS. Let's see what comes of this...

 

If you do, you must accept the following result
Probably the system installation must use Unattend.xml
After installation the system can no longer be updated and update patches cannot be installed
Cannot adjust enable or disable feature page content

 

You need to login to view this posts content.

 

I tested this WinSxS, yes, everything is as you write:
Once installed, the system can no longer be updated and update patches cannot be installed.
You cannot configure whether feature page content is enabled or disabled.

That's why this is not my version of WinSxS. I need this to work.

 

Everyone's needs are different.
If you want the installation image to be around 1G, you have to make a choice.

 

Nobody argues about it. Personally, I would be satisfied with the size of the .iso image of about 1.8-2.2 Gb and I do not strive for its size of 1 Gb at all. So I'm looking for a way to get the image I want, but without losing the basik functions of the system. By the way, my SSD drive of the "C" partition is 256 Gb, so my desire to reduce the image size is also not connected with this.

 

hi this only makes system restore enabled.
repair my computer still is missing when using usb in install set up screen

 

You need to login to view this posts content.

 

Hello everyone, a question for the audience: changing the image edition of Windows Enterprise LTSC to Windows IoT Enterprise LTSC is very simple,

Spoiler

Code:

echo.
ECHO.
ECHO =============================================================
ECHO Upgrade to IoTEnterpriseS
ECHO =============================================================
dism /Image:"%~dp0mount" /Set-Edition:IoTEnterpriseS

but can anyone tell me what command to use to change the image edition of Windows IoT Enterprise to Windows IoT Enterprise LTSC ?

 

Got it, thanks, then I'll have to resort to black magic. I'll have to get out my old "tambourine" and dance around the SKU with it.

 

Actually, that's why I asked: in order to change the edition from IoT to IoT LTSC on the installed OS, it's enough to change the product key. That's why I thought that maybe they'd share a script here for changing the edition from IoT to IoT LTSC on the connected image. Well, if not, then no, I'll figure it out myself...

 

I'll tell you more: I've been doing PCs for a long time and my first OS was Windows 98. I've been building Windows builds since Windows 10. So I have some experience in this business. As a test, I tried changing the product key in the installed OS and in other editions (except Home) to the IoT LTSC key and they activated as IoT Enterprise LTSC. Therefore, I think it is still possible to change the edition from IoT Enterprise to IoT Enterprise LTSC in the connected image. I will think, experiment, and I think I will solve this problem. While I'm looking for ...