Stories
Slash Boxes
Comments

SoylentNews is people

posted by cmn32480 on Friday April 21 2017, @11:08AM   Printer-friendly
from the update-this! dept.

Submitted via IRC for TheMightyBuzzard

Microsoft blocked the delivery of Windows Updates recently to Windows 7 and 8.1 devices powered by a next-generation processor.

The company announced the support change in January 2017. Broken down to the essentials, it means that Intel Kaby Lake and AMD Bristol Ridge processors are only support by Windows 10, and not older versions of Windows.

To hammer that home, Microsoft made the decision to block Windows Update on Windows 7 or 8.1 PCs with those next generation processors.

The company introduced patches, KB4012218 and KB4012219 for instance, which introduced process generation and hardware support detection on Windows 7 and 8.1 systems.

Windows users who run Windows Update get the unsupported hardware error prompt when they try to scan for and download the latest patches for their -- still supported -- operating system.

GitHub user zeffy made the decision to take a closer look at how the actual blocking is done on the operating system level.

Details on exactly what was done are available in the article.

Source: https://www.ghacks.net/2017/04/18/bypass-for-windows-update-lock-for-modern-processors-found/

This will be especially handy for those whose machines were entitled to updates but were mistakenly blocked from receiving them.


Original Submission

 
This discussion has been archived. No new comments can be posted.
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: 3, Interesting) by DannyB on Friday April 21 2017, @02:55PM (4 children)

    by DannyB (5839) Subscriber Badge on Friday April 21 2017, @02:55PM (#497427) Journal

    Why would Microsoft consider it to be a problem for old versions of Windows to merely run on newer processors? Unless the new processors are so incompatible with the old ones that it requires significant effort to make old Windows run on new processors.

    Oh, I get it. To force people off of older OSes. So they can get pwned by Windows 10.

    --
    The lower I set my standards the more accomplishments I have.
    Starting Score:    1  point
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 0) by Anonymous Coward on Friday April 21 2017, @04:43PM (1 child)

    by Anonymous Coward on Friday April 21 2017, @04:43PM (#497483)

    Or as one colleague of mine said, "It's a lot of work to update an older OS to work with newer software! Why should companies have to support that?" So just buy the new version! I mean, its so HARD for Apple and MS to patch the old OS with code theyve already written...

    • (Score: 2) by bob_super on Friday April 21 2017, @05:34PM

      by bob_super (1357) on Friday April 21 2017, @05:34PM (#497502)

      To be fair (because at least one person has to), spending engineering time figuring out why something broke on an old product is neither fun nor necessarily productive. Many times, the problem has been solved already in the newer version, and porting the fix's dependencies is a lot of redundant work...

      BUT, that's what "supported" is supposed to mean.

  • (Score: 2) by SomeGuy on Friday April 21 2017, @05:35PM (1 child)

    by SomeGuy (5632) on Friday April 21 2017, @05:35PM (#497504)

    Seriously. Why?... Why?... Why?....

    In the past, older OSes would usually still run on newer PC hardware. This was even expected of the hardware, although ocasionally things would genuinely break. The catch usually came in the form of drivers that required a later OS, or some fancy lame new features that required functionality not present.

    Run Windows 98 on a dual CPU system? Sure, but it just would only use one. Run Windows 2000 on an Athlon X2? Sure, but you probably would be stuck in basic VGA mode. Run Windows 95 on a 5ghz machine? Yea, that is going to crash and burn without some hacks. Run Windows XP with some fancy-shmancy built-in goofy SATA controller? Well, if it doesn't offer IDE emulation or slipstreamable drivers you might have a problem - or slap in an IDE PCE card.

    But it never said "you are not allowed to try this".

    Congratulations, Microsoft. You have turned the PC industry in to a distributed version of Apple.

    • (Score: 2) by DannyB on Friday April 21 2017, @08:11PM

      by DannyB (5839) Subscriber Badge on Friday April 21 2017, @08:11PM (#497565) Journal

      Too bad Apple didn't patent this business method so that they would be the only one doing it.

      --
      The lower I set my standards the more accomplishments I have.