Intel has news – good, bad and ugly – about Raptor Lake bug patch. Here's what to know

Intel released information Friday about a patch for the microcode bug affecting 13th- and 14th-generation Intel Core processors, and the chipmaker’s news is a mix of good, bad, and ugly.

Also: If Intel can’t come up with a Qualcomm-killer soon, it’s game over for x86 PCs

The good news

According to Intel, the patch is being distributed to all its partners and is specifically aimed at K, KF, and KS processors. Intel is also investigating possible mitigations for systems already showing symptoms and expects to have an update by the end of August. If your processor shows signs of damage, Intel advises getting it exchanged. 

Intel’s testing also indicates that the patch does not adversely affect system performance, so that’s good news for gamers and those who want the fastest system possible.  

Intel says that “all future products will not be affected by this issue.”

The bad news

There is no word yet on whether mobile (laptop) chips from these generations are affected, leaving owners in a wait-and-see situation. Additionally, there is no straightforward way for owners of affected chips to determine if their processor is flawed and requires an update, other than manually checking their CPU model (using one of the methods I outlined here). 

Furthermore, there is no official method for owners of crashing systems to determine definitively whether their chip has been damaged or if the system crashing is due to another factor.

Also: What CPU and motherboard do I have? Here are some fast and easy ways to find out

And then there’s the bit where Intel cautions about overlocking these chips, stating that the update “will not prevent users from overclocking” but also that “overclocking may void their warranty and/or affect system health” and that it recommends owners “utilize the Intel default settings.”

The ugly news

The patch will only be available as part of a BIOS update, meaning owners will need to find, download, and install the correct patch themselves. Distributing the patch via Windows Update would have made it accessible to a broader range of PC owners, not just those aware of the problem.