Critical BIOS Update Regression with No Local HP Support: Microphone Failure, CPU Locked at Base Clo

[Slasherxe]

Dear HP Support Team,

I am reporting a critical firmware issue caused directly by a recent BIOS update released for my HP laptop model, and I require escalation due to the absence of active HP support in my country.

After installing the latest BIOS version, the system exhibits the following problems:

1. Microphone failure

   • The internal microphone no longer works in any application.

   • The device is detected by Windows, but no audio input is captured.

2. Severe CPU underperformance

   • The CPU is locked at its base clock speed and does not boost under load.

   • This causes constant lag, stuttering, and major performance degradation in all games and even normal system use.

   • Power plans, thermal conditions, and Windows performance settings are correctly configured.

3. Blocked BIOS rollback

   • Downgrading or recovering to a previous BIOS version is blocked on this HP model.

   • This leaves the system permanently affected by a faulty firmware update with no user recovery option.

These issues did not exist prior to the BIOS update and appeared immediately afterward, indicating a BIOS regression affecting CPU power management (P-states / turbo behavior) and audio initialization.

I have already completed the following troubleshooting steps:

• Clean Windows installation

• Full driver reinstallation (audio, chipset, power management)

• BIOS reset to default settings

• EC reset / power drain

None of these resolved the issue, confirming this is not a software or driver-related problem, but a firmware defect.

Additionally, there is no active HP service center or official HP technical support in my country.
This makes it impossible to receive local assistance, BIOS recovery, or on-site servicing, leaving firmware-level resolution as the only viable solution.

I am therefore requesting one of the following actions:

• An urgent corrected BIOS release that restores microphone functionality and normal CPU boosting
  OR

• An official method to unlock and perform a BIOS rollback for this specific model
  OR

• Direct escalation to HP engineering / firmware team for investigation and resolution

This BIOS update has significantly degraded core system functionality, and due to the lack of local HP support, remote escalation is essential.

System model, BIOS version, and serial number can be provided immediately upon request.

Regards,
David Azubuike

[VikramTheGreat]

Hi @Slasherxe,

Welcome to the HP Support Community.
 

Thank you for posting your query. I will be glad to help you.

I’m really sorry you’re going through this. From what you’ve described, the issues began immediately after flashing the latest BIOS, and you’ve already done a clean OS install, reinstalled drivers, reset BIOS to defaults, and performed an EC/power drain. That points strongly to a firmware regression impacting CPU P‑states/turbo behavior and the audio device’s initialization path.

1) Capture model, BIOS, and system identifiers (for engineering triage)

Please provide (or collect) the exact identifiers from the HP System Information screen:

• Press Fn + Esc in Windows to open HP System Information and note: Product Name, Product Number, System Board ID, BIOS Version/Date, Feature Byte, Build ID. These are required to match the BIOS package and platform family correctly.

If Windows is not usable, you can also find these in BIOS Setup: power on → repeatedly tap Esc → F10 (HP Computer Setup) → Main tab (lists BIOS version, product, board ID, etc.)

2) Check whether your platform uses HP Sure Start (affects rollback paths)

On many recent business platforms, HP Sure Start protects the BIOS and blocks manual rollback/USB recovery methods. Sure Start automatically repairs corruption from its onboard backup and prevents unsupported downgrades. You’ll see “HP Sure Start” on the logo screen at boot, or in product specs. If your device has Sure Start, manual Win+B recovery/USB crisis methods are not supported; if it does not have Sure Start, Win+B recovery may be available.

3) Attempt a BIOS recovery (only if your model is without Sure Start)

If your notebook does not use Sure Start:

• Try Manual BIOS Recovery: Power off, connect AC, press and hold Windows + B, then press Power for 2–3 seconds (keep Win+B held) until you see a BIOS recovery screen. Follow on‑screen prompts to restore from the recovery partition. This can revert a recent flash or reload a clean image if the update is corrupt, though it will not bypass policy‑blocked downgrades on models that disallow it.

If your platform does have Sure Start, this path won’t be offered; Sure Start will already be enforcing the current signed firmware image and repair only corruption paths, not regression rollbacks.

4) Collect hardware diagnostics (to attach to escalation)

Run HP PC Hardware Diagnostics UEFI outside Windows to confirm the microphone codec and CPU tests (CPU stress, thermal, power) pass or show anomalies:

• At boot: Esc → F2 → run Component Tests (CPU, Audio input if available) and System Tests.
• If any test returns a 24‑digit Failure ID, save it. This code allows HP to route your case to repair/engineering immediately.

I hope this helps.

Take care and have an amazing day!
 

Did we resolve the issue? If yes, please consider marking this post as "Accepted Solution" and click "Yes" to give us a helpful vote - your feedback keeps us going!

Regards,

VikramTheGreat

[Slasherxe]

Hi,

Thank you for the detailed response and for acknowledging that the behavior strongly indicates a BIOS/firmware regression.

Please find my responses below, aligned with your requested steps.

1) System identifiers for engineering triage
I have collected the required identifiers from HP System Information (Fn + Esc) and BIOS Setup (Esc → F10). I can provide the following immediately:

• Product Name - Victus by HP Gaming Laptop 15-fa0xxx

• Product Number - 68U87UA#ABA

• System Board ID - 8A50

• BIOS Version and Release Date   F.32

• Feature Byte -   fdkF  m9mz  ncpn  pqpr  qjqt  .ae

• Build ID  -   3K5F  6b7K  aBap  aqas  awbh  cbfp

Please confirm the best and secure way to submit these details for escalation to the firmware/engineering team.

2) HP Sure Start status
This platform does use HP Sure Start, which explains why:

• Manual BIOS downgrade is blocked

• Win + B / USB recovery paths are unavailable

• The system enforces the currently signed BIOS image

Because Sure Start prevents user rollback and local recovery, this confirms that end-user remediation is impossible and that resolution must come from HP via:

• A corrected BIOS release

• Or an engineering-approved rollback path

3) BIOS recovery attempt
As expected on a Sure Start–protected platform, manual BIOS recovery options are not presented. The firmware enforces the current image and does not allow regression rollback, even though the regression is functional (CPU and audio).

4) Hardware diagnostics
I will run HP PC Hardware Diagnostics UEFI (Esc → F2) and complete:

• CPU tests (including stress/thermal where available)

• Audio / microphone tests

If any Failure ID is generated, I will include the 24-digit code immediately.
However, I want to note that these issues only appeared after the BIOS update, and no hardware symptoms existed prior, reinforcing that this is firmware-level.

Additional critical context
There is no active HP service center or official HP technical support in my country. This makes physical servicing or local firmware recovery impossible. Because HP Sure Start blocks rollback, the system is effectively locked in a degraded state unless HP engineering intervenes remotely.

Request
Given the above, I am requesting:

• Formal escalation to HP firmware/BIOS engineering

• Confirmation that this issue is logged as a BIOS regression for my platform family

• Guidance on whether a fixed BIOS or engineering rollback is planned

The CPU being locked at base frequency and the microphone failing system-wide significantly impacts usability, and the lack of local HP support makes escalation essential.

I appreciate your assistance and look forward to next steps from the engineering team.

Regards,
David Azubuike

[VikramTheGreat]

Hi @Slasherxe,

Thank you for getting back and letting me know. Related to the issue, support is limited on our end.

Please help us with your HP unit serial number or the product number in a private message for further assistance.
 

Here is the link to find the product Serial number: - Click here

To access your private messages, simply click the private message icon on the upper right corner of your HP Support Community profile, next to your profile and send a private message to me with the serial number because we value your privacy.

VikramTheGreat

HP Support

[Slasherxe]

Hi Vikram,

Thank you for the update.

I understand the need for privacy. I will send my HP unit serial number via private message as requested.

For clarity and to ensure this case is handled correctly, I would like to restate the scope of the issue before submission:

• The problem began immediately after installing BIOS F.32

• The system now exhibits:

  • CPU locked at base frequency (no turbo / boost under load)

  • Internal microphone non-functional system-wide

• Clean OS install, driver reinstallation, BIOS reset, and EC reset have already been completed

• This platform uses HP Sure Start, which blocks rollback, leaving no end-user recovery path

• There is no active HP service center or official HP support in my country

Because of the above, I understand that standard support options may be limited. However, this is a firmware regression, not a configuration or hardware failure, and it requires BIOS/firmware engineering review, not local servicing.

When submitting the serial number internally, please ensure the case is categorized as:

• BIOS regression introduced in F.32

• CPU power management / P-state / boost behavior affected

• Audio device initialization failure

• Sure Start–blocked rollback

I am requesting confirmation that:

• This case will be escalated to the HP BIOS / firmware engineering team

• The regression will be logged against the Victus 15-fa platform family

• I will be informed if a corrected BIOS or engineering-approved rollback becomes available

I will now send the serial number via private message.

Regards,
David Azubuike

[VikramTheGreat]

Hi @Slasherxe,

Thank you for the detailed explanation and for outlining the issue so clearly.

To proceed further, I will need the complete printer/PC serial number and also the region/country you are contacting us from. This is important because the device appears to be a US-region model, and region details are required to correctly review the product configuration and available support options.

Based on what you have shared, I understand that:

• The issue started immediately after installing BIOS F.32
• CPU performance behavior has changed (no boost beyond base frequency)
• The internal microphone is no longer detected or functioning
• OS reinstall, driver reinstallation, BIOS reset, and EC reset have already been completed
• BIOS rollback is blocked by HP Sure Start
• There is no local HP service presence in your country
   

I want to set the right expectation:
While I can document and forward all the technical details exactly as shared, I cannot guarantee a specific BIOS update, rollback approval, or timeline for a firmware release. BIOS availability and changes depend on internal validation and platform-level decisions, and there may or may not be a revised BIOS issued for a specific version.

Once you share the serial number and region, I can ensure the information is reviewed accurately against your device model and platform family, and you will be informed if any official update or supported option becomes available in the future.

Please send the serial number via private message when ready.

Take care and have an amazing day!
 

Did we resolve the issue? If yes, please consider marking this post as "Accepted Solution" and click "Yes" to give us a helpful vote - your feedback keeps us going!

Regards,

VikramTheGreat

[Slasherxe]

Hi Vikram,

Thank you for explaining the process and for continuing to assist.

I will send the complete serial number via private message as requested.

For reference, here are the additional details:

• Region/Country: Nigeria

• Device origin: US-region model

I understand that BIOS changes and release timelines depend on internal validation and that a revised BIOS or rollback option cannot be guaranteed. I appreciate you setting that expectation clearly.

My goal with this case is to ensure the issue is accurately documented and reviewed at the firmware level, since:

• The behavior began immediately after installing BIOS F.32

• The CPU no longer boosts beyond base frequency

• The internal microphone stopped functioning system-wide

• HP Sure Start prevents rollback, leaving no end-user workaround

• There is no local HP service presence in my region

I am seeking guidance on any supported or official options available for this platform, and to ensure the information is correctly reviewed against the Victus 15-fa platform family.

I agree this issue is not yet resolved, but I appreciate your help in reviewing and documenting it properly. I will share the serial number shortly via private message.

Regards,
David Azubuike

[VikramTheGreat]

Hi @Slasherxe,

Thank you for sharing the details and for taking the time to clearly explain the situation.
 

We confirm that the information you’ve provided, along with the system details, will be forwarded internally to the relevant HP team for further review and documentation. This will help ensure the behavior you’re experiencing is evaluated at the appropriate firmware and platform level.
 

At this stage, we truly appreciate you sharing the PC details and context, as this allows the concern to be reviewed accurately. While changes such as BIOS revisions or rollback options depend on internal validation and cannot be guaranteed, your feedback and system data are important for ongoing analysis.
 

If there are any updates or supported options identified after the internal review, they will be communicated accordingly. In the meantime, please feel free to continue engaging with the community if you need assistance or have additional observations to share.
 

Take care and have an amazing day!
 

Did we resolve the issue? If yes, please consider marking this post as "Accepted Solution" and click "Yes" to give us a helpful vote - your feedback keeps us going!

Regards,

VikramTheGreat