Slashdot Mirror
Microsoft Locks Ryzen, Kaby Lake Users Out of Updates On Windows 7, 8.1 (kitguru.net)
Artem Tashkinov writes: In a move that will shock a lot of people, someone at Microsoft decided to deny Windows 7/8.1 updates to the users of the following CPU architectures: Intel seventh (7th)-generation processors (Kaby Lake); AMD "Bristol Ridge" (Zen/Ryzen); Qualcomm "8996." It's impossible to find any justification for this decision to halt support for the x86 architectures listed above because you can perfectly run MS-DOS on them. Perhaps, Microsoft has decided that the process of foisting Windows 10 isn't running at full steam, so the company created this purely artificial limitation. I expect it to be cancelled soon after a wide backlash from corporate customers. KitGuru notes that users may encounter the following error message when they attempt to update their OS: "Your PC uses a processor that isn't supported on this version of Windows." The only resolution is to upgrade to Windows 10.
Windows 7 is almost 10 years old at this point. how long should MS support it for?
It's one thing to put up a disclaimer saying the chip is not supported and any trouble/bugs/crashes you run into are at your own risk, it's quite another to block the install completely.
Seven puppies were harmed during the making of this post.
you have to move to W10 one day, so why not to-day?
No, that's the thing you see. You don't have to move to W10. Microsoft wants to FORCE you to move.
Seven puppies were harmed during the making of this post.
From now on I'll be running Windows in a virtual CPU I think.
The tipping point where it's worth getting everything I need working on Linux has arrived. I'm off to look for ScanSnap drivers.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
No, they said they would not support new cpus - thats fine, if they dont want to supply new drivers for new hardware, but thats not what they doing now, they block access to ALL windows updates if you have installed (and obviously got it to work) windows 10 on a new cpu. how is this not simply blackmail?!
Not having the sheep running spyware 10 costs them advertising revenue and must be blocked.
No, that's NOT the only resolution.
Anyone who's the least bit tech-savvy can use WSUSOffline to draw down all the updates.
The only issue you have there is that Microsoft's update servers are randomly peppered with corrupted manifest files which prevent fresh WSUSOffline setups from downloading anything. So you have to do multiple attempts on multiple networks (sometimes) before getting a pristine manifest.
Once you have it, it's fine from there on out.
But yeah, this is major bullshit on Microsoft's part. And Nadella and his crew need to be drawn and quartered for this.
Chas - The one, the only.
THANK GOD!!!
You're one of several shills posting that bullshit here.
Windows 7 extended support (security patches) is guaranteed until January of 2020. They're pulling the plug on that early for anyone with a Ryzen or Kaby Lake CPU. This isn't about those CPUs not being supported - Windows 7 runs on them just fine. This isn't about the patches needing more testing or development - the patches don't care what CPU you're running and MS hasn't tested a patch before deploying it in 3 fucking years.
FUCK SATYA NADELLA!
Use Linux, no one forcing you to do anything ever again.
*cough*systemd*cough*
Try FreeBSD.
Because that's not what the word blackmail means.
So what exactly did you think "support" was?
Up until now, nobody thought that "support" was the logical inverse of "sabotage".
From now on I'll be running Windows in a virtual CPU I think.
I switched to Linux Mint a while back and have no complaints. I'm also looking at Chapeau (chapeaulinux.org) but so far Mint works great.
Microsoft just can't help fucking people over and then bragging about it. Incredible.
Just cruising through this digital world at 33 1/3 rpm...
Actually, the word you are looking for is "sabotage".
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
"No support" means: "You are running on unsupported hardware. Do you want to continue anyways? y/n".
What they are doing is "Your hardware is unsupported. Be fucked." That one is called "sabotage".
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
You wrote that? Here?
I'm not sure if that was brave or stupid, but in tens of thousands of cases it's just going to be plain wrong. Assembly makes you special? I even did it as early as High School like thousands of others here.
Then isn't it lucky for you that other people are doing that for you.
um, no. enterprises are still buying new hardware and installing corporate approved images with win7 while they continue to work on win10 deployment plans. enterprises rely on the extended support dates published by MS to drive priorities and planning for massive roll outs like win10. Win10 is not a trivial update due to the new management needs for store, updates, telemetry and privacy settings, third party app updates, user training, etc...
> you have to move to W10 one day
I'm also going to die someday too, but that doesn't mean I want it today.
So, BZZZT, no, but thanks for playing! I _already_ have multiple boxes with Windows 7 that work perfectly fine thank-you-very-much. There is no software that runs "only" on Windows 10 that "I need."
I've already migrated my personal dev work to OSX and Linux, so no, Microshaft can go fuck themselves, because I don't want nor need their Spyware they mis-label as Windows 10.
Hell, even at my day job we've been using OSX for the past 5 years and we're a Fortune 50 company. I also know many devs who use Linux. Seriously, there are WAY more OSX and Linux machines then I would have thought possible.
The harder Microsoft tries to force customers to Windows 10, the harder the pushback will be. In Microsoft's quest to force everyone to use Windows 10 -- they forgot the most important thing:
Customers don't NEED it.
There is only 1 name for people who run Windows 10.
Idiots.
Because they sold themselves out. M$ has no respect for you. All they care about is exploiting you. For some of us, MS has stepped over the line.
fully supported != updates blocked. Ignoring the CPU and just assuming it will work would be better than this. They don't actually need to add support for anything that isn't already in there.
Ryzen is a new feature
Ryzen has new features. It doesn't require ANY for it to work on Windows 7. Windows added a new feature to detect and block the architecture from updates - that's the only "new feature" that's relevant here.
If you DON'T stay current, then you have as little choice as to what happens to your linux kernel and distro as any Windows user has over their OS.
Not quite true. I don't care about kernel release notes and distro package changes until they matter. That is, it either breaks something I care about, or adds something I care about. When it comes to things I care about, I have complete control over my own computer.
And that's all that matters to me. (By definition) If I can't configure one distro to suit my needs, there has always been another one available.
No one has time to go through every single fucking line of code for every driver, utility, application, etc. So you end up "trusting" the open source community.
Open source doesn't mean the code is perfect. I don't think anyone believes that. There will always be security holes, whether added maliciously or accidentally, in virtually every operating system I am aware of. But that's not the same as having the vendor introduce unwanted features, or deliberately degrade user experience, or preventing the user from modifying their own settings, or preventing them from running software that didn't come from an approved app store. ...all of which have been done in recent years. It's gotten to the point where it's debatable who actually owns the computer, you or the OS vendor.
I have not seen this to the same extent in open source OSes, even including Android.
Some of us would rather skip the illusion of safety and open-ness and get on with our lives without kidding ourselves.
Safety is never guaranteed with code of any significant complexity. Openness can be.
It can't be that, because Windows 10 supports lots of older CPUs and GPUs that are not capable of PlayReady 3.0.
I wonder what happens if you try to play back a Bluray on a non-PlayReady 3.0 system. I heard that they would limit you to inferior quality audio. Doesn't seem to stop the rippers.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC