I meant LTSC 2021 vs Pro 22H2 and if there is any difference between them (after using this tool obviously)
What counts is the build number, all 1904x are the same, minus few minor details, mostly estetics (I meant this about the update level) The differences between LTSC and releases for the cattle, aside few missing/added packages the differences are in the kernel policies.
I have found only three real life differences: 1. Support lifetime: 2025-10-14 (Pro) vs 2027-01-12 (LTSC) vs 2032-01-13 (LTSC activated with IoT key) 2. Licensing. You probably already have license for Pro, so you do not need to buy any additional license if you want to stay in legal terms. 3. Some multimedia features (like Dolby Atmos - surround sound technology) are lacking in LTSC by default (read this and this).
So performance wise, it shouldnt really matter, right? (apart from the mentioned differences which make sense) I have been daily using for a while the patch/script with Pro 22h2 and it feels great Thanks!
Performances are (more or less) the same starting from vista sp2 ending to win11, *if in the same conditions*. One installs LTSC because privacy concerns, the resource occupation of Pro can be easily tamed removing packages/disabling things, something we started to to when it made sense (in 2015 when LTSB was not a thing, or at least wasn't yet known)
Exactly. Tested both and I see no noticeable differences in performance, behavior, privacy. They share the same codebase, updates, APPX packages (yes, you can even enable Microsoft Store on LTSC). LTSC is really different from Pro only when we are talking about original unmodified version, but as long as you use this script they are really the same. Yes. Windows XP was faster on low-end machines. But starting from Vista, all debloated Windowses behaves quite similarly. All performance issues that users complain on, are due to bloatware. Microsoft, Google and other big corporations love bloatware to make additional money, but users are not necessarily happy with it.
I would like to give feedback: I ran Slimdown 1.60 with Windows 10 21H2 LTSC x64, installed it, swapped the key to IoT and activated it with MAS 1.8 without any problems. Everything worked straight away without me having to do anything else. The system runs great, thank you wkeller
Hi Did you use any updates, and if yes, which one ? Downloaded by the program or out of the 'hotfixes'-folder ? Thanks in advance
Don't ask why, but I like "kms 38" better and that's only possible with the manual change. I'm just doing this to learn, almost all of my computers have pro licenses
what manual change? You mean manually inserting the gVLK to have it switch to unactivated status instead of the auto HWID?
@Enthousiast: I entered the gVLK to switch from Enterprise LTSC to IoT Enterprise LTSC for KMS 38 activation. This is not necessary for HWID activation.
Yes. Use PreDownloadAllUpdates.cmd tool which is included and then you will no longer need internet connection at all.
V 1.60 is working perfectly here thank you. A suggested inclusion in the registry as follows: Code: Windows Registry Editor Version 5.00 ; Created by: MC [-HKEY_CLASSES_ROOT\*\shell\TakeOwnership] [-HKEY_CLASSES_ROOT\*\shell\runas] [HKEY_CLASSES_ROOT\*\shell\TakeOwnership] @="Take Ownership" "Extended"=- "HasLUAShield"="" "NoWorkingDirectory"="" "NeverDefault"="" [HKEY_CLASSES_ROOT\*\shell\TakeOwnership\command] @="powershell -windowstyle hidden -command \"Start-Process cmd -ArgumentList '/c takeown /f \\\"%1\\\" && icacls \\\"%1\\\" /grant *S-1-3-4:F /t /c /l' -Verb runAs\"" "IsolatedCommand"= "powershell -windowstyle hidden -command \"Start-Process cmd -ArgumentList '/c takeown /f \\\"%1\\\" && icacls \\\"%1\\\" /grant *S-1-3-4:F /t /c /l' -Verb runAs\"" [HKEY_CLASSES_ROOT\Directory\shell\TakeOwnership] @="Take Ownership" "AppliesTo"="NOT (System.ItemPathDisplay:=\"C:\\Users\" OR System.ItemPathDisplay:=\"C:\\ProgramData\" OR System.ItemPathDisplay:=\"C:\\Windows\" OR System.ItemPathDisplay:=\"C:\\Windows\\System32\" OR System.ItemPathDisplay:=\"C:\\Program Files\" OR System.ItemPathDisplay:=\"C:\\Program Files (x86)\")" "Extended"=- "HasLUAShield"="" "NoWorkingDirectory"="" "Position"="middle" [HKEY_CLASSES_ROOT\Directory\shell\TakeOwnership\command] @="powershell -windowstyle hidden -command \"Start-Process cmd -ArgumentList '/c takeown /f \\\"%1\\\" /r /d y && icacls \\\"%1\\\" /grant *S-1-3-4:F /t /c /l /q' -Verb runAs\"" "IsolatedCommand"="powershell -windowstyle hidden -command \"Start-Process cmd -ArgumentList '/c takeown /f \\\"%1\\\" /r /d y && icacls \\\"%1\\\" /grant *S-1-3-4:F /t /c /l /q' -Verb runAs\"" [HKEY_CLASSES_ROOT\Drive\shell\runas] @="Take Ownership" "Extended"=- "HasLUAShield"="" "NoWorkingDirectory"="" "Position"="middle" "AppliesTo"="NOT (System.ItemPathDisplay:=\"C:\\\")" [HKEY_CLASSES_ROOT\Drive\shell\runas\command] @="cmd.exe /c takeown /f \"%1\\\" /r /d y && icacls \"%1\\\" /grant *S-1-3-4:F /t /c" "IsolatedCommand"="cmd.exe /c takeown /f \"%1\\\" /r /d y && icacls \"%1\\\" /grant *S-1-3-4:F /t /c"
When I use the PreDownloadAllUpdates.cmd tool, I'm always getting an error message: The last download was "Windows10.0-KB5029244-x64-baseless.psf" and then it removed all files, one by one: WARNING! Removed incorrectly downloaded file: "[filename]" (repeats for all downloaded files) ERROR! Some files has NOT been downloaded correctly! Please re-run the script and try again! Any idea why? Haven't done any changes to the script
With the newest version of the tool, PIN or Fingerprint (Windows Hello) doesn't seem to be working. I set up a password and afterwards I'm trying to set a PIN and it says that this option is not available right now. What could be wrong?