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

The fixed script ran without an error, I'm certainly not thrilled by Win11 yet, but I'm working on it! @ SunLion Thank you for your tireless work on this.

 

Hello, I am not entirely sure I understand your point regarding:

Code:

copy /y “%~dp0PersonalTweaks\REG\*.reg” “%~dp0Tweaks”

and

Code:

copy /y “%~dp0PersonalTweaks\REG\*.reg” “%~dp0OEM\$OEM$\$$\Setup\REG” >nul

Why apply the same .reg files twice? Directly to the connected image and then again when installing the OS? When .reg files are applied to the connected image and .cmd files are applied when installing the OS, it is clear and correct, in my opinion. But the way you are doing it, the purpose of these operations is not clear at all. Please explain it to me, a simple-minded person...

 

Some registry entries may not work during the installation phase

 

Got it, thanks, I didn't know that. Although it's not entirely clear how registry entries can fail to work during installation if they are already written to the registry and the installer only copies them to the disk when installing the OS and cannot change them in any way. Oh well, you probably know better...

 

SunLion's handling is reasonable because there is no restriction on adding any registry content to the image, but in reality, some registry contents may be invalid if handled in this way. The specific ones that will fail require personal accumulation. Joining twice can avoid problems.

 

I agree that SunLion's approach is very reasonable, which is why I mainly use his script ideas when working with images. Do you think that double attaching .reg files avoids problems? It may be difficult to verify this due to the large number of entries made in the registry. I'll take your word for it and add these files to the $OEM$\$$\Setup\REG folder as well.
As they say: you can't spoil porridge with butter.

 

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.

 

Typical telemetry-related documents:

Code:

\Windows\DiagTrack

\Windows\System32\AggregatorHost.exe
\Windows\System32\diagnosticdataquery.dll
\Windows\System32\diagtrack.dll
\Windows\System32\dtdump.exe
\Windows\System32\runexehelper.exe
\Windows\System32\UtcDecoderHost.exe
\Windows\System32\Windows.System.Diagnostics.Telemetry.PlatformTelemetryClient.dll
\Windows\System32\utcutil.dll

\Windows\SysWOW64\diagnosticdataquery.dll
\Windows\SysWOW64\dtdump.exe
\Windows\SysWOW64\Windows.System.Diagnostics.Telemetry.PlatformTelemetryClient.dll

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Why not working on LTSC 2019, who is far less "bloated" and lighter than 2021, for the same result, I mean a fast operating system

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Then maybe we'll go back to the plow ?

 

You need to login to view this posts content.

 

I don't want to offend you, but after reading what you wrote, it's not something to laugh about, but rather something to cry about. IMHO

 

Doesn't offend me one bit -- I think it's both hilarious and sad, I was a Windows FanBoy for decades -- but Windows 11 isn't even an Operating System anymore, it's more like Gamified Dystopian Monopoly Industrial Surveillance Malware... And literally so...