HP BIOS update broke CPU management badly

[ismatov]

After getting BIOS update F36, BIOS disabled access for Operating systems to utilize CPU properly. Windows has to use its outdated drivers to manage CPU which is very inefficient. The same thing is happening with Linux, amd_pstate driver, which heavily relies on CPPC to function is not working at all. Everything was fine until this update. The update's notes say that "Enhanced security", but it didn't enhance security, but broke the most essential functionality. I don't know whether HP releases another BIOS update to fix it. I wrote a lot of feedback about it. BIOS rollback or modifying the needed settings is impossible.

[Max3Aj]

@ismatov, Welcome to HP Support Community. 
 
Thank you for posting your query, I will be glad to help you. 
 

Here's a step-by-step guide to address the issue:

BIOS Rollback (If Possible)

You mentioned rollback is currently blocked. However, you can try the following workaround:

BIOS Recovery via USB

1. Download the previous BIOS version (if available) from the HP support site.
2. Use the HP BIOS Recovery Tool to create a recovery USB:
   • Guide: HP BIOS Recovery from USB
3. Plug in the USB, power off the laptop, then hold Win + B and press the power button for 2–3 seconds.
4. Release the keys and follow on-screen instructions.

If rollback is locked in the firmware, this method may not work. In that case, proceed to the next step.

Reset BIOS Settings to Default

Sometimes, security settings introduced in BIOS updates can interfere with CPU features like CPPC.

• Restart your laptop and press F10 to enter BIOS.
• Look for an option like "Restore Defaults" or "Load Setup Defaults".
• Save and exit.

Temporary Workarounds

Until HP releases a fix:

• On Windows, try using ThrottleStop or QuickCPU to manually manage CPU performance.
• On Linux, switch to the acpi-cpufreq driver if amd_pstate is broken:

  sudo grubby --update-kernel=ALL --args="amd_pstate=disable"

I hope this helps. 
 
Take care and have a good day. 
 
Please click “Accepted Solution” if you feel my post solved your issue, it will help others find the solution. Click the “Yes" on the bottom left to say “Thanks” for helping! 
 
Max3Aj
HP Support 

[ismatov]

@max3aj  hi , Thanks for replying. Rollback is truly impossible in any way. Also, resetting BIOS or even CMOS didn't help. I was actually using acpi_cpufreq with inefficient CPU fruquency and governors. HP should consider the bug and fix it.

[Max3Aj]

@ismatov, Thank you for your response,  

I'm sending a private message to assist you with the next action. 

  

Please check your Private message icon on the upper right corner of your HP Community profile Next, to your profile Name, you should see a little blue envelope, please click on it or simply click on this link. 

  

I hope this helps! Keep me posted. 

  

Max3Aj

HP Support 

[ismatov]

I don't think anything helps except getting a new BIOS update or a different brand of laptop. Is that so difficult to fix what HP developers broke and release another update? I feel sadness a lot, I was good, everything was working... I wish I hadn't known or updated the BIOS at all since I bought it. I took 2 moments before realizing what a BIOS update means in HP laptops (in a negative way).

[Hawks_Eye]

@ismatov 

I hear you—and I’m really sorry you’re going through this. It’s incredibly frustrating when a BIOS update, which is supposed to improve stability or security, ends up breaking something as fundamental as CPU management. 

The update you’re referring to (F.36) appears to have disabled access for operating systems to properly utilize CPU features like CPPC, which affects both Windows and Linux performance. And unfortunately, BIOS rollback is often locked on newer HP systems, making it even harder to undo the damage.

Here’s what others have tried while waiting for HP to release a fix:

• Reset BIOS to Defaults: Sometimes this can restore partial functionality.
• Use CPU tuning tools: Apps like ThrottleStop or QuickCPU on Windows may help manually manage performance.

Thanks,

Hawks_Eye

[ismatov]

Sorry for replying late, but I managed to rollback the firmware from F36 to F35 officially. I don't know how and why it happened. Maybe it is because I wrote a lot of feedback to HP support center or HP diagnostics windows client a few times or the developers took a look at this. This time the downgrader tool warned me about downgrading, but it downgraded. It went very smoothly. It just worked for only F35, not older ones. Do you think developers allowed downgrading this? If so, how?