4 ms·
For anyone that does not want to switch to linux LTSC is a good alternative to avoid issues like these: https://github.com/massgravel/massgrave.dev/blob/main/d
by kachapopopow 11mo ago
For anyone that does not want to switch to linux LTSC is a good alternative to avoid issues like these:
https://github.com/massgravel/massgrave.dev/blob/main/docs/windows_ltsc_links.md https://github.com/massgravel/massgrave.dev/blob/main/docs/w...
I recommend IoT Enterprise LTSC and you can use https://get.activated.win https://get.activated.win to activate it.
If you are using it in a business setting it's $30/month per license (there are unfortunately no non subscription licenses for windows 11 IoT).
Alternatively you can install AtlasOS and disable automatic updates and rely on maintaining a strong firewall or/and switching every application to run sandboxed using sandboxie for security. Take note that for an average person you can run without updates as long as your computing device never leaves your home and your local network / networks you trust, use external tool for driver updates.
- mapontosevenths 11mo agoI feel like if you're going to use LTSC there is no point in using 11. Windows 10 LTSC will still get updates for years, and uses less than half the resources that 11 does.
- kachapopopow 11mo agoit's also using the exact same kernel, the only difference is explorer.exe and default apps funny enough. But I have to admit that the file explorer (not to be confused with explorer.exe the desktop), is nicer with the new tab functionality.
- mapontosevenths 11mo agoI know it's subjective, but I care less about the tabs and more about the missing right click options. I'm also annoyed that 11's explorer uses literally double the memory to perform the same function with less options. I know you can add the missing right click options back. I just shouldn't have to.
- mapontosevenths 11mo agoJust to double check... I loaded the same folder in Windows 10 IOT LTSC and Windows 11 Pro retail. Explorer.exe used ~500Mb peak working memory. In Windows 10 it was less than 200Mb. In windows 10 it also loaded about 2x faster, despite the system I'm using being objectively worse hardware in every single measurable way. With Windows 11 you get less, and pay more.
- vel0city 11mo agoOh no, its going to use 1.8% more of my system's memory, what a nightmare, totally unusable. Why is 200MB acceptable but peaking to 500MB just totally unacceptable and problematic? The original Macintosh had a graphical desktop with 128KB of RAM, shouldn't anything more than 50KB be unacceptable? EDIT: Just checked on a couple of my Windows 11 machines, all of them have Explorer using <200MB of memory. So no, explorer.exe isn't necessarily using 500MB of memory. Something else is going on with that system.
- kachapopopow 11mo agobecause the same thing applies to the new terminal, new settings app, new everything, it slowly adds up.
- hulitu 11mo ago> Why is 200MB acceptable but peaking to 500MB just totally unacceptable and problematic? Because only 200MB are reserved for this application. /s That 300MB may be taken from another app (CAD) which needs it badly.
- vel0city 11mo agoShouldn't you then also complain that explorer.exe is consuming 200MB when previous graphical desktops managed it in handfuls of kilobytes? Once again, why is 200MB OK, but 500MB, oh boy, that's just far too much. Couldn't that CAD software also make use of that other 200MB? Why not demand 20MB? Or 2MB? Or 20KB? How much of that extra 300MB is paged out and not actually in active memory? On both systems, how much of the total is actually paged out and not in current system memory? Are you trying to run a modern CAD system on a device with only 512MB of RAM or something?
- hackernudes 11mo agoThere are two issues to consider: security updates and software compatibility. The LTSC version is good for security updates, but I worry that software could stop supporting Windows 10 despite the LTSC version existing. Coincidentally I am about to install Windows 10 Enterprise LTSC! I was experimenting (and struggling) with PXE boot with iSCSI. An update broke iscsi boot in Windows 11 25H2 (26200.6901 works, 26200.7019 fails) as well as LTSC (26100.6905 works, 26100.7178 fails). There were other issues with iscsi boot on the LTSC version - the network hardware needs to be enumerated before the first boot, but can't boot because it needs network (a chicken-and-egg style problem).
- deltoidmaximus 11mo agoTo expand upon the second issue: I believe Nvidia stopped releasing driver updates for the version of Windows 10 a still supported version of LTSB was based upon at one point leaving users with no further driver updates for a Microsoft supported system. I don't know how common of a problem this is but it did seem to happen once. I also use LTSC but this is a potential pitfall.
- verall 11mo agoI use W10 LTSC (which is pretty old at this point) and have no problem installing the latest NV drivers