This is exactly my experience - I have a Lenovo W530 from 2013, it has an i7, 32gb RAM and SSDs (RAID0 for performance, backups are off-device) - and it is STILL lightning fast.
However - EVERY single trick I have tried... the above command, LTSC, Enterprise edition, etc, results in a situation where after installation a few days (or hours) and some updates get installed, and... blue-screen-of-death on every boot.
Gave up, installed Linux - still working through some issues (GPU driver compatibility), but overall it is a much better experience...
I think at a certain point you need to just call it quits with that sort of bullshit. I have my dignity. I'm a fucking grown adult. I'm not going to spend my spare time haplessly looking online to unfuck the new current set of fuckery. Just take the fucking bullet. Learn linux. Congrats you're playing whack-a-mole with a trillion dollar corporation and prolonging your misery. This is stupid.
Yeah, microsoft will never change otherwise. People and companies continue to willingly allow themselves to get abused, and then wonder why Microsoft never changes and continues to abuse them.
So long as said abuse never results in a loss of marketshare and revenue, it will continue. Why would they stop if there's no negative repercussions?
Win8.1 x64 required double-width compare and exchange instruction support, so people who bought Win8 for a CPU or motherboard that didn't support it had to downgrade to the 32-bit version or lose support in 2016.
Win7 updates from 2018 onwards required SSE2 with no warning.
Win11 24H2 and later won't install on x86 processors that don't support the x86-64-v2 baseline.
From my experience it seems to happen all the time. Settings reset, uninstalled apps reinstalled, firewall settings erased. I went looking for the Windows 10 patch that deleted the Documents folder if you had remapped it to another drive, and it was hard to find an article due to all the other times their updates have also deleted people's Documents folder. This was the first time I recall it happening: https://www.engadget.com/2018-10-09-windows-10-october-updat...
That's, e.g., how I would determine what these commands do
I have had HN replies in the past that argued Windows is open source and thus comparable to UNIX-like OS projects where _the public_ can read the source code and make modifications, _for free_
Absent the source code, we can read Microsoft's documentation
The other thing to tell you is that this is not a live version of windows with all the features of the full desktop. It is the windows that runs the windows installer application, so enough windows to do that and no more.
Whenever I see an unexplained command I don't understand from a random internet forum, I hop onto the production server and run it, just in case it might boost performance. Wouldn't want to miss out on that.
Been doing it since I was 12. It taught me all about the ins and outs of `rm`.
Sounds like me back in the early 80s when I used to war dial, and people used to share "active" prefixes. I learned all about the 911 prefix when I set my dialer and went to sleep. About 20 minutes later the cops were banging on my front door. True story; I was in 6th grade, got arrested for it.
I got taken to juvenile hall, put in a holding area with kids that had stolen cars and stabbed other kids in fights. The funny thing is all these "bad kids" were really cool; we talked about video games (Donkey Kong!). I remember one kid got into a fight with his football coach and broke both the coach's legs. He was a big kid, looked like a grown man. He was pretty much in charge of the holding area. But he was cool as hell, cracked jokes with me. I actually kinda enjoyed the holding area.
Anyway, the officials thought I had just called 911 over and over, like to play a prank. They wouldn't hear anything about my computer or whatever (it was the early 80s). They were pissed. I was kept in the holding area for a few hours, then they let me go home. I was ordered to a bunch of community service, cleaning the parking lots of local parks, stuff like that.
Some of the checks are around CPU features that they don’t currently use but may use in the future. And CPUs don’t typically respond super gracefully to being asked to execute instructions they don’t understand.
