3 ms·
Windows 7 is still supported. Geez. It came out in >>2009<<. Also, Windows 10 bricks every one of my lower end computers. Windows Defender, Telemetry, and more
by katastic 9y ago
Windows 7 is still supported. Geez. It came out in >>2009<<.
Also, Windows 10 bricks every one of my lower end computers. Windows Defender, Telemetry, and more eat 100% disk usage. It's indefensible. Worse, Windows 10 refuses to let you CORRECT the problem. They make new user accounts that are ABOVE the user's top permissions so you have to go to insane lengths to disable a service.
And I say all of this as someone who professionally supports Microsoft installations. There's NO need to defend Microsoft in places that don't need it. They're big boys. They should just get their shit together and handle criticism.
Like why did it take 15+ years to get proper rescalable command prompt, or virtual desktops? I've got literally dozens upon dozens of stories of Microsoft products being half invented, half completed and half reliable, and MSDN documents that companies rely on for $$$ decisions that end up being erronious or conflicting with other KB articles.
- aspenmayer 9y agoI don't get this recent usage of "brick." Unless it cooks the CPU or is otherwise non-bootable after installing 10, persisting even through other boot media, that isn't a brick. I've seen upgrades fail due to many issues including prior OS corruption and failing storage media, but clean installs of Windows 10 work nearly every time on nearly any hardware that supports ACPI. Driver issues notwithstanding, I don't see anything to support your assertion that Windows 10 bricks lower end PCs. And if the hardware is older than that, it isn't worth your time to even install any other OS on, is it? Diminishing returns. Not meant to be a criticism, I'm just curious what specific issues you were having that you articulate as bricking.