I rather suggest Win 11 LTSC. The Windows 11 IoT Enterprise 2024 LTSC supposedly:
- doesn't have the tpm requirement
- no copilot, recall, edge browser, ms store
- allows local setup
- no feature updates, only security
- built-in options to disable telemetry
Keys go for $300 in some stores, or, one can use an activation emulator, or massgrave.
Scripts can be good for one-time use, but it's swimming against the current. As soon as you stop swimming, the current wins. With the LTSC, you don't swim against the current, but rather choose a different current. In its case, it's MS themselves who provide the debloating.
No need if you use the IoT version and the massgrave activation script. It uses the built-in activation mechanisms in Windows to activate until 2038 or something.
I'm using the Windows 11 Enterprise IoT LTSC with activation until 2038 right now.
The best way to debloat Windows is to switch to Linux. I think that GNOME3 is now more polished than either Windows or Mac, and 95% of Windows games just run out of the box through Proton.
While the 95% figure is possibly correct when considering all games since the beginning of Windows, the remaining 5% includes most modern multiplayer games.
This isn't remotely true, it only really includes AAA "competitive" games. My solution here is to do without them; I would have probably bought BF6 had it supported Linux, but now that there are thousands of other games that work perfectly on Linux, it's a very minor loss. With Linux quickly becoming too big to ignore, sooner or later game studios will simply no longer be able to ignore that market. For now, it's only a few %, but it's growing, and still represents millions of sales. When lost revenue will exceed the cost of developing a compatible anti-cheat, Linux will be suddenly supported.
I would've expected this kind of inane take on Reddit or X, not here. Or on SO where somebody asks "How do I do X?" and is told "X sucks, you want to use Y".
This is not about "X sucks", but the very first questions from an engineering perspective should be whY? What do you want to accomplish? Is X actually a good approach towards Y?
If it turns out that trying to shoehorn X into kinda accomplishing Y is very hard work, then suggesting to use X2 instead is a perfectly sensible suggestion.
If you have a hard constraint that you must use X, even if it does not fit well to Y, fair enough. Then you add that as a reply or state it in the beginning.
- I am thinking of writing a very detailed post right here on HN on testing all the windows 11 debloat tools within a VM. My only question is how do I determine or say benchmark or measure which of these debloat tools works the best at the end?
Keep a spreadsheet of all the optional features / bloat you’re looking to remove, rate each solution as a percentage of how many of those columns it ticks, and maybe also do a review on boot time and idle RAM usage?
is there a tool that i can use to say stress test the OS as a whole that ll give me a score like how we do apache bench http tests because what is bloat might be very subjective on my part. is there a more objective measure?
Personally I gave up a long time ago and just installed Debian Linux. But it’s wild to me that the average non-technical/casual windows user has to put up with so much bs… it’s an atrocious ux
- doesn't have the tpm requirement
- no copilot, recall, edge browser, ms store
- allows local setup
- no feature updates, only security
- built-in options to disable telemetry
Keys go for $300 in some stores, or, one can use an activation emulator, or massgrave.
Scripts can be good for one-time use, but it's swimming against the current. As soon as you stop swimming, the current wins. With the LTSC, you don't swim against the current, but rather choose a different current. In its case, it's MS themselves who provide the debloating.
I'm using the Windows 11 Enterprise IoT LTSC with activation until 2038 right now.
https://en.wikipedia.org/wiki/XY_problem
This is not about "X sucks", but the very first questions from an engineering perspective should be whY? What do you want to accomplish? Is X actually a good approach towards Y?
If it turns out that trying to shoehorn X into kinda accomplishing Y is very hard work, then suggesting to use X2 instead is a perfectly sensible suggestion.
If you have a hard constraint that you must use X, even if it does not fit well to Y, fair enough. Then you add that as a reply or state it in the beginning.