Microsoft Blocks Windows 7/8 Updates on AMD Ryzen and Intel Kaby Lake Systems

Post by cptskippy » Thu, Mar 16, 2017, 1:42 PM UTC

joosters wrote: post #63

josteink wrote: post #48

Earlier quoted context omitted.

> automatically downloading of Windows 10 by Microsoft and bricking devices Downvote for falsely claiming PCs can be bricked[1], even more so by simply using Window-update, which at worst might require a reinstall if the install is botched. [1] The definition of a brick is that something is now completely non-functional, beyond repair and thus "as useful as a brick". Something which can be recovered is by definition…

You are splitting hairs. My dad's PC was as useful as a brick to him after it downloaded Windows 7 and then wouldn't boot. If you think 'reinstall' is an acceptable or realistic solution for average users, you are badly mistaken.

Post by reacweb » Thu, Mar 16, 2017, 1:53 PM UTC

jimmies wrote: post #4

The recent pop-up ads, automatically downloading of Windows 10 by Microsoft and bricking devices by Microsoft's friends seems like a good indication of the tipping point for many people. Stallman was right, then? About 10 years ago I made the jump from Windows to GNU+Linux. It was quite annoying because at the time I was still heavily invested in web design and such, so not having photoshop was quite a loss. Nowadays…

Post by cptskippy » Thu, Mar 16, 2017, 1:57 PM UTC

rincebrain wrote: post #39

This seems like they have enormous pressure from on high to make sure Windows 7 doesn't become another XP that they have to support for 15 years By Any Means Necessary. If circumstances were different, I might even be applauding them for taking strong corrective actions against another XP doomsday scenario, or for moving to rolling release, both of which seem like great plans. The reason I'm not is that Windows 10 fe…

Post by 0x4a42 » Thu, Mar 16, 2017, 2:00 PM UTC

ThrowawayR2 wrote: post #90

iliketosleep wrote: post #28

Earlier quoted context omitted.

Microsoft's willingness to actively disrupt its users (whether it's through forced updates or artifical limitations) is indeed a tipping point for me. I always chose Windows for its convenience, and the fact that I could use it on my own terms. Clearly, this is no longer the case. As for Stallman, there's a fine line between a madman and a genius. Reality has shown us that he definitely is not a madman.

Ah, yes, how absolutely shocking that Microsoft should choose not to support a processor that didn't even exist at the time that version of Windows was released. Why, everyone knows, especially on HN, that updating and retesting software costs nothing at all and so that's why we all eagerly go back and retrofit all versions of software we've ever released, no matter how old, to support the latest hardware just as soo…

Post by jimmies » Thu, Mar 16, 2017, 2:01 PM UTC

cptskippy wrote: post #98

jimmies wrote: post #72

Earlier quoted context omitted.

>bricking devices by Microsoft's friends I didn't say it bricked the PC -- but they literally did brick shit that gets plugged in to the PC. It's a binary blob that comes with windows update and it breaks your hardware, intentionally. http://hackaday.com/2016/02/01/ftdi-drivers-break-fake-chips... It is a brick, because (1) It was working before, it doesn't work now, (2) The hardware is fucked, you plug into another…

So it's Microsoft's fault that a vendor supplied drivers that were designed to keep fake competitor's devices from using their tech by disabling them? Microsoft isn't doing code reviews of drivers and it would be outrageous to expect them to do so.