Intel 13th and 14th gen cpu BIOS update due for omen 45L desktops

[TheRedGoose]

I've been running my PC for approximately 9 months now, and I haven't bumped into any apparent issues so far. I've used HWINFO to put a close eye on my CPU vitals (maximum core voltages or VIDs) and I also went out my way to use OMEN Gaming Hub to underclock my processor core ratios.

One crucial thing I haven't been able to do was undervolt my CPU since apparently OMEN desktops have disabled the option to undervolt, ridiculously it lets you overvolt.

It's honestly embarassing how a reputable brand like HP has not informed or responded to this issue anywhere as of now, makes me wonder if they are even aware of this.

[OmenUser7]

I am still using old pc.

My experience just trying to get it up n runnning without using anything stressful.

Put hdd into the hard drive bay and it overheats on HP Omen 45L (runs nice and cool on my old system).

Windows login auto-encrypts all drives on Win11 Home.  No prompts to let you know.

Wondering why the usb drive didn't enumerate I unplugged and plugged it back in.  The drive is now toast.

Shut down pc and windows corrupted to an unrecoverable state.

I was told to download the HP cloud recovery tool on old machine.  Did so and that stick failed to install.

HP sent me a USB stick stating the image I downloaded maybe corrupt and theirs is "official".

I asked for an expedited shipment and said they only ship the standard shipping speed.

I wait 3-5 days on day 4 now, hope it comes today.

Bought Costco so have return window, but this is the last thing to check or have to return it.

Shame the hdd slot doesn't cool the HDD and the pc inoperable for 1 month.

I was told I would receive a call for an extended warranty and other arrangements.  That never happened.

[Alec_K]

I have the same issue and contacted HP support. Unfortunately, HP did not answer me clearly about the BIOS update schedule and extended warranty.
 
Other vendors, like ASUS and MSI, have already released BIOS updates. However, I cannot find any official information from HP's side. 
 
I don't understand why such a big vendor like HP ignores this problem. This is a serious issue that can physically damage the CPU. A huge number of the latest HP PCs are affected. It is a serious problem, really. As an HP community, we cannot ignore it.

[_m_1]

Intel issued the update on the 9th August and I find it ridiculous that other manufacturers like ASRock, Asus, MSI and Gigabyte released the update within 1 day after intel issued it. Even Dell (a manufacturer with a number of computers to update like HP) released the update after a week (16th August). Now almost a month, still waiting from HP. The discord server has HP employees who say mid September is what they are targeting.

[_m_1 · Accepted solution]

Good news, on the discord server someone said that they had done an optional update from settings > windows update > advanced options > optional updates titled HP Inc. - Firmware - 15.25.0.0 which includes microcode 0x129 as the microcode version can be checked in hwinfo64.

[Jasubuusteri]

Thank you so much for this dude!

Apparently, you can get better help from the forum than from HP's own support.

I didn't have that "HP Inc. - Firmware - 15.25.0.0" update in my optional updates list, only "HP Inc. - Firmware - 15.26.0.0" and "HP Inc. - Firmware - 15.27.0.0" updates. It wasn't on my installed driver updates list either.

After the "HP Inc. - Firmware - 15.27.0.0" update, the processor microcode version remained the same as before ("11D"), but the "HP Inc. - Firmware - 15.26.0.0" update updated the bios and firmware from 16.1.30.2264 to 16.1.32.2418 and the microcode version had changed to "129" after the update.

HP has decided to handle this update apparently via Windows Update.

It's strange, however, that according to the Microsoft Update Catalog "HP Inc. - Firmware - 15.26.0.0" was last updated on April 25, 2024, while Intel released that 0x129 microcode update only on August 9, 2024. Additionally there is no information available about what those updates contain. You have to install the update and see what has changed.

HP support has not been of any help in solving this issue. When I talked to the support person about the subject, she said that it is really rare that someone asks and is interested in such complex issues and that he appreciates my knowledge on the matter. However, everyone has been waiting for this update like the reincarnation of Jesus, lest the processor burn!

The only benefit or information that I got from HP's support was that they passed the information on and the support person assumed that "our experts are probably already aware of this problem and explaining it".

[Jasubuusteri]

Thank you so much for this dude!

Apparently, you can get better help from the forum than from HP's own support.

I didn't have that "HP Inc. - Firmware - 15.25.0.0" update in my optional updates list, only "HP Inc. - Firmware - 15.26.0.0" and "HP Inc. - Firmware - 15.27.0.0" updates. It wasn't on my installed driver updates list either.

After the "HP Inc. - Firmware - 15.27.0.0" update, the processor microcode version remained the same as before ("11D"), but the "HP Inc. - Firmware - 15.26.0.0" update updated the bios and firmware from 16.1.30.2264 to 16.1.32.2418 and the microcode version had changed to "129" after the update.

HP has decided to handle this update apparently via Windows Update.

It's strange, however, that according to the Microsoft Update Catalog "HP Inc. - Firmware - 15.26.0.0" was last updated on April 25, 2024, while Intel released that 0x129 microcode update only on August 9, 2024. Additionally there is no information available about what those updates contain. You have to install the update and see what has changed.

HP support has not been of any help in solving this issue. When I talked to the support person about the subject, she said that it is really rare that someone asks and is interested in such complex issues and that he appreciates my knowledge on the matter. However, everyone has been waiting for this update like the reincarnation of Jesus, lest the processor burn!

The only benefit or information that I got from HP's support was that they passed the information on and the support person assumed that "our experts are probably already aware of this problem and investigating it".

[TheRedGoose]

thank you @_m_1, youre a legend!

[_m_1]

Thank FuBunny on Discord who told me about this!

[Jasubuusteri]

How long do you think it will take for HP to release the new 0x12B firmware update?

If you hear anything about this, I'm super interested...


https://www.guru3d.com/story/intel-again-to-release-microcode-update-0x12b-to-address-vmin-offset-in...