Microsoft disables Windows Update when Meltdown/Spectre registry key isn't set

Post by Arnavion » Tue, Jan 09, 2018, 9:53 PM UTC

bomb199 wrote: post #64

epistasis wrote: post #50

Earlier quoted context omitted.

that seems like a fairly questionable blame-shift for MS. If they don't have the guts to provide even that level of protection, yet more reason to shift away from them except for trivial things like gaming.

So if you edit the Kernel on your version of Ubuntu, then Canonical should be held responsible? That seems like a crazy thought process. You're running software that modifies Window's internal functionality. The vendor knows it's unsupported. How can you blame the company who just made the platform you compromised? Might as well set your root password to "password" and open it to the public then complain that the sec…

Post by untog » Tue, Jan 09, 2018, 9:57 PM UTC

craftyguy wrote: post #53

untog wrote: post #27

Earlier quoted context omitted.

It isn't relying on it - MS recommends people use Defender, which works fine. But unfortunately not everyone is doing that.

Seems like the EU and/or the FTC would want to talk to microsoft about microsoft requiring microsoft's AV to be installed before microsoft will update the OS.

Post by Karnickel » Tue, Jan 09, 2018, 10:06 PM UTC

mesofile wrote: post #52

It's worth noting that Windows Update may also fail to apply the Meltdown/Spectre patch if other conditions aren't met. Some are mentioned on the KB page [1] but they don't mention another common scenario, which is that if your system firmware is not ready to accept the update, Windows Update will not apply it, and _it won't tell you_ that it's not applying it -- it will simply say 'Your device is up to date'. I had…

  Windows OS support for branch target injection mitigation is present: True
  Windows OS support for kernel VA shadow is present: True
  Windows OS support for kernel VA shadow is enabled: True

Post by sambe » Tue, Jan 09, 2018, 10:25 PM UTC

cube2222 wrote: post #32

sambe wrote: post #4

Earlier quoted context omitted.

You can’t just stop using AV software I’m told. The key is checked for everyone, including people with no AV. Contrary to the sensational headlines, it is implied to be a temporary measure. It’s not really clear whether you’d have to only do this manually once, or on every subsequent update.

If you do it once, it may be that your AV isn't compatible with the patch and will cause your system to bluescreen and maybe not even turn on, so no, you really shouldn't do that.

Post by scholia » Tue, Jan 09, 2018, 11:12 PM UTC

mulmen wrote: post #54

JustSomeNobody wrote: post #40

Earlier quoted context omitted.

But I don't have to go get them installed myself. So it's Audi's problem, not mine.

Right, but MS provides AV or you can install a third party option instead. Just like you can install aftermarket brakes, suspension, ECUs or even seats and seatbelts in your Audi.