Read more.Last night Intel sought to deflect sole liability for the security issues. Was it correct?
Read more.Last night Intel sought to deflect sole liability for the security issues. Was it correct?
Can you include the note about the patch negatively affecting AV products leading to crashes? Microsoft put that out just now: https://support.microsoft.com/en-us/help/4072699/important-information-regarding-the-windows-security-updates-released
mtyson (04-01-2018)
Be interesting how AMD/Intel benchmarks work out after the patching.
For those with the latest windows 10 (creators update) you're probably going to want KB4056892
http://www.catalog.update.microsoft....px?q=KB4056892
Look at it this way guys. Intel will have to sell the new chips and chipset motherboards at a very low price. Good times ahead!
Intel are airily dismissing performance hit as a trifle, but in recent years new products from them have boasted minimal improvements over 3 yo predecessors.
Anything remotely resembling a 30% hit is a giant step back.
A reddit user mentioned how this has probably been known, used, and abused by the intelligence community for years. It's why it went unpatched and unannounced; it's an absolute goldmine of an opportunity to take action against an enemy state. And it makes sense too, there's no way Intel didn't know about this from the get-go.
Do we have a list of compatible AV ?
Whilst I appreciate that they have built in a checker, I don't want to run the risk of killing my system...
Society's to blame,
Or possibly Atari.
Going off-topic, but from the MS link in the article: "Microsoft recommends all customers protect their devices by running a supported anti-virus program". I thought they'd stopped recommending that recently with w10, and claiming defender was enough?
Defender *is* a supported anti-virus program, but it's not the only supported anti-virus program. If you run a 3rd party anti-virus, Defender disables itself: https://docs.microsoft.com/en-us/win...-compatibility
Last edited by scaryjim; 05-01-2018 at 11:06 AM. Reason: typo
There are currently 1 users browsing this thread. (0 members and 1 guests)