floof.org

TundraWolf mastodon (AP)

Windows 10 has now reached its official end of life and will not be updated further.

It still does not work properly, but the lack of updates does at least mean it will now remain broken in a consistent way with no prospect of another update breaking yet more of Windows.

1 1
Unless you're on LTSC or have ESM enabled, in which case you can look forward to more vibe-coded updates breaking Windows in hopefully less destructive ways than state-sponsored threat actors are almost certainly in the process of trying to do. :)
1
Fox mastodon (AP)

Yus, Windows 10 will keep on working just like any other older OS versions. Use a nice anti-virus [1], a decent firewall [2], a "no you cannot do this and/or that"- software [3] and do not visit websites you don't want your mother to know about. (yes, there are many more factors)

But broken? What is broken exactly? I am using my w10 install since forever and this machine is literally always on, up to 100 days at the time. It's working properly! Not an attack btw, just curious. :)

[1] No link, because AV choice is as fickle as an amphibian having to choose between duc(k)tape and frog tape
[2] https://github.com/henrypp/simplewall
[3] https://github.com/hellzerg/optimizer/releases

#w10 #windows10

EDITS because it is super busy at work x3

This entry was edited (2 weeks ago)
TundraWolf mastodon (AP)
@fox The whole list is quite long, but I can start with it cannot schedule for nuts. It's memory management sucks. Random boot failures that occur after the software has control of it. Its inability to schedule I/O so that the whole GUI does not hang because one device is not responding. Far too much runs in supervisor mode for no reason. Its ability to just forget it is on a network, while using that network. The deliberate breaking of agreed standards to try to force it to only interact with other versions of Windows. The Spyware, particularly when it brings down part of the OS. They way it just moves devices around at random. It determination not to process some interrupts. The need to constantly re-run sfc to get it back into a state where it will boot. It rewriting configuration files to be what it wants, not what the host machine needs. That's before I get into all the mindless and idiotic things it has done atw the user level.
@Fox
Fox mastodon (AP)
That's quite a bit! I have no knowledge of many of the stuff, but the boot issues - are you sure that's not a sneaky hardware issue?
TundraWolf mastodon (AP)
@fox Absolutely. Reproduced on 50+ machines from a mix of suppliers.
@Fox
Pippin friendica
Ooooh. So after I let it do one final update, that'll be it? I'll be free of having to have a calendar entry on my phone at all times to remind me when my laptop's current "update pause" is coming to an end and that I need to schedule a time to shut everything down to allow it to do updates and reboots before I put it on hold again and move the phone calendar entry another 6 weeks into the future and repeat the whole process again… Phew!