Cumulative Update KB4056892 Windows 10 v1709 Build 16299.192

RingTailCoon said:

True, aren't wel all a bit OVERREACTING a bit, while that same bug was already present for years! And hey, all our PCs are still function, right? They haven't exploded in our faces, right?

So again, aren't we a tad bit overreacting? :)

The problem is that it's now made a buzz about it. Criminal intentions are most likely on the rise to exploit this as we speak.

Hi,

Faith said:

The problem is that it's now made a buzz about it. Criminal intentions are most likely on the rise to exploit this as we speak.

The chance of me or you being exploited by this is rather small but just imagine what could happen to banks, the industry at large ?
Now that could back fire to all of us, couldn't it ?

Cheers,

VBF said:

Nice of you to be so cheerful!
Seriously though, from some of the many postings on these bugs, it would appear that they're more likely to affect Cloud servers, with multiple users using the same code than standalone PCs. However, IMO anything that allows unauthorised access to kernel areas is a bad thing and should be fixed.

I totally agree with you. It seems that the reason for this out-of-band critical update was the following:
"Google disclosed the vulnerability yesterday on the Project Zero blog. It seems likely that Microsoft’s decision to release an out-of-band security update for Windows 10 was caused by Google’s disclosure date."

Read the full article here:

https://www.ghacks.net/2018/01/04/mi...urity-updates/

Damn. This "fix" has completely killed my SATA SSD performance:



I couldn't believe it but I reinstalled the patch and got virtually identical results.

Yet bizzarely, an NVM-based SSD on the same machine is completely unaffected. A driver thing I guess.

Very depressing.

well.. to be fair, from the outside it looks like google only disclosed stuff after it's already widely reported by media (starting with the register) everyone who hasn't got fixes out on the sly already are scrambling. whether they prompted someone else to talk about it 1st.. ask the people with tinfoil hats.

I just did a Macrium image of 16299.125, checked for updates, got a Defender update and nothing else. Tried again immediately and there it was. Installed without issue, now 16299.192