Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.

Microsoft Blocks Updates for New CPUs on Windows 7 and 8.1

posted by Fnord666 on Sunday March 19 2017, @01:07AM   Printer-friendly
from the no-updates-for-you dept.

Celestial writes:

Microsoft Windows 7 or 8.1 users on Intel Kaby Lake or AMD Ryzen CPUs will not be able to download Windows updates.

Microsoft announced some time ago that new silicon as the company called it back then would not be officially supported on Windows 7 or 8.1.

This meant basically that only Windows 10 would support Intel's, AMD's and Qualcomm's new processors, while Windows 7 or 8.1 would not.

This does not mean that Windows 7 or 8.1 won't install on machines running these new processors, but that Microsoft (and the manufacturer) won't offer any form of support for those devices.

A new support page on the Microsoft website suggests that users who run an unsupported processor on an older version of Windows -- read Windows 7 or Windows 8.1 -- won't be able to scan for or download Windows updates anymore.

Users will get the following error message when they run the scan:

Unsupported Hardware
Your PC uses a processor that isn't supported on this version of Windows and you won't receive updates.

It looks like I'll be moving to BSD or Linux sooner than I planned.

Original Submission

 
This discussion has been archived. No new comments can be posted.
Microsoft Blocks Updates for New CPUs on Windows 7 and 8.1 | Log In/Create an Account | Top | 102 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: -1, Flamebait) by Anonymous Coward on Sunday March 19 2017, @03:45PM (1 child)

    by Anonymous Coward on Sunday March 19 2017, @03:45PM (#481175)

    nobody was talking about installing virtualbox on fucking windows. the whole point of the question was how to use some slaveware on linux, ffs.

    Starting Score:    0  points
    Moderation   -1  
       Flamebait=1, Total=1
    Extra 'Flamebait' Modifier   0  
    Total Score:   -1  

  • (Score: 2) by NotSanguine on Sunday March 19 2017, @04:40PM

    by NotSanguine (285) <{NotSanguine} {at} {SoylentNews.Org}> on Sunday March 19 2017, @04:40PM (#481198) Homepage Journal

    nobody was talking about installing virtualbox on fucking windows. the whole point of the question was how to use some slaveware on linux, ffs.

    Actually, OP requested steps to install on Linux or Windows:

    Been meaning to ask this for a while now but never felt motivated. I've never run a VM. I know what a VM is, I've used Windows since the 3.1 days, used Unix since 82 or so, was a sysadmin for a couple years, have code in the Linux kernel (couple of drivers).

    That said, what are steps 1-5 of setting up and running a VM on either a Linux box or a Win10 box (I've got both).

    For the record, since you appear to only be semi-literate, I didn't give any instructions for installing on Windows.

    If you're going to attempt trolling/flaming, you could at least direct your moronic drivel at the right person. I could point you at the post you were likely aiming at, but I''ll leave that as an exercise for you.

    I do feel pity for you, since you're either not so bright, new to this sort of thing, or both.

    I'm betting on both.

    Toodles, honey!

    --
    No, no, you're not thinking; you're just being logical. --Niels Bohr