Your Intel based computer is (probably) going to get slower this month (along with the whole world).

Comments

I think you'd have to go back to sometime around 2007 or thereabouts to find one without the bug. My Dell XPS which is just two years old surely has it, so bad news for me on the one hand. On the other, the new laptop I ordered during their Boxing Day sale has AMD chips. Guess I was lucky that even on sale the Intel laptops were out of my league budget-wise.

"I have not updated my main WIN 8 pc for 3-4 years. It runs my music DAW, and ever since I started the DAZ hobby it runs DS too. I always disable any external interference in my workstation rig, keeping it stable and predictable."

Anyone else notice that we're starting to get almost weekly news stories about the latest catastrophic software/hacking bug that's going to affect the entire universe? And they're getting worse and worse?

I read that Fox News article although I try to avoid reading any news from any news organization and those people buying unfiltered water are basically being swindled. People have built countless behavioural, envirnmental, and nutritional filters to grow old satisfied and safely and yet they throw it out the window to be hipsters? Not smart and I don't care where their degrees came from.

"Intel believes these exploits do not have the potential to corrupt, modify or delete data...........Intel has begun providing software and firmware updates to mitigate these exploits.......Check with your operating system vendor or system manufacturer and apply any available updates as soon as they are available.

This misreported issue, which doesn't exist, affects our rivals, we've got it in hand, patch as soon as possible, because everything is fine (and it wasn't us).

I dearly love how they try to imply this is a problem with AMD processors after AMD already clearly stated it isn't. Shady.

There's a lot of shifting weight in that statement, it's very PRbot3000. I would like to know how this bug could have flown under the radar for over twenty years though, it's all very strange.

I think this bug happened because of feature creep. The basic function still works but can by used to trigger exploits of features added on later and Intel and AMD and others have been adding plenty of new features. I think the AMD person claiming that AMD doesn't have a problem doesn't know what they are talking about.

It's sort of like some jurisdictions have those wierd old laws about horses and hitching and riding since they were basically cars that need to be stricken from the law books to avoid hurt.

"Intel believes these exploits do not have the potential to corrupt, modify or delete data...........Intel has begun providing software and firmware updates to mitigate these exploits.......Check with your operating system vendor or system manufacturer and apply any available updates as soon as they are available.

This misreported issue, which doesn't exist, affects our rivals, we've got it in hand, patch as soon as possible, because everything is fine (and it wasn't us).

"Intel believes these exploits do not have the potential to corrupt, modify or delete data...........Intel has begun providing software and firmware updates to mitigate these exploits.......Check with your operating system vendor or system manufacturer and apply any available updates as soon as they are available.

This misreported issue, which doesn't exist, affects our rivals, we've got it in hand, patch as soon as possible, because everything is fine (and it wasn't us).

Classic.

This is all I thought of when I read your post!

A Star Wars Quote -
"Uh, we had a slight weapons malfunction, but uh... everything's perfectly all right now. We're fine. We're all fine here now, thank you. How are you?"

I dearly love how they try to imply this is a problem with AMD processors after AMD already clearly stated it isn't. Shady.

Is it? They do point out that there is an issue (though from what I gather not identical) with ARM64, so the Intel spokesperson may be assuming that AMD is trying to deflect attention from a bug with their chips.

I dearly love how they try to imply this is a problem with AMD processors after AMD already clearly stated it isn't. Shady.

Is it? They do point out that there is an issue (though from what I gather not identical) with ARM64, so the Intel spokesperson may be assuming that AMD is trying to deflect attention from a bug with their chips.

Yes. This phrasing is absolutely not accidental.

Based on the analysis to date, many types of computing devices — with many different vendors’ processors and operating systems — are susceptible to these exploits. Intel is committed to product and customer security and is working closely with many other technology companies, including AMD