Windows 11 monitor drivers for HP ENVY Curved AIO 34-a051

[MasonVegas]

When using my HP ENVY Curved AIO 34-a051 as an external monitor for my new Windows 11 HP ENVY Desktop, the PC won't boot. They Num Lock key won't light up indicating the PC is stuck after BIOS. The only way to boot is to unplug the monitor, reboot, wait for the Num Lock key to illuminate, and then plug the monitor back in. The built-in speakers do work, but the built-in webcam doesn't. 

I'm using an HDMI 8K cable, which works on this AIO as an external monitor for a laptop, so I know the cable works.  

I've tried updating the driver from "Generic Monitor (HP ENVY Curved)" driver to the "HP ENVY Curved Display" driver from HP's support site here https://support.hp.com/ee-en/drivers/hp-envy-34-inch-displays/model/13083195, but that driver is from 2016 and is intended for Windows 10.  Windows 11 won't recognize the two other drivers on the same page.

What seems to be needed is an updated driver for Windows 11 in order to continue using my HP ENVY Curved AIO 34-a051 as an external monitor with webcam. Unfortunately, the AIO itself is not compatible with Windows 11 as it has a 6th gen processor.

Please provide an updated driver so that I can extend the life of this otherwise perfectly working monitor.  Surely, I'm not alone. Thank you.

[Garp_senchau]

@MasonVegas, Welcome to HP Support Community,

Thank you for posting your query; I’m here to help by guiding you through steps to resolve this issue

Your HP ENVY Desktop PC TE01-5000i is likely attempting to detect EDID (Extended Display Identification Data) or DisplayPort/HDMI handshake data during POST (power-on self test).

Some AIOs with HDMI-In ports don’t properly respond to these handshakes when used as passive monitors, and older drivers/firmware can exacerbate the issue.

The BIOS/UEFI firmware in your new desktop may be pausing or hanging due to a conflict in display initialization with the HDMI-In port on the AIO.

Use UEFI Fast Boot or Skip Display Initialization

Enter the HP ENVY Desktop’s BIOS (tap Esc or F10 repeatedly at boot).

Look under Advanced > Boot Options and try enabling:

Fast Boot

"Skip display initialization" (if available)

Save and exit. This can reduce pre-boot handshakes and get past the stuck POST state.

Change HDMI Cable Type or Port

While your 8K HDMI cable is high-quality, it may be triggering unsupported EDID modes on the old AIO.

Try a basic HDMI 1.4 or 2.0 cable instead.

I hope this helps.

Please feel free to reply here if you have any questions or if you need further clarification on any of the steps. 

Take care and have a good day. 

If my response helped, please mark it as an Accepted Solution! ✅ It helps others and spreads support. 💙 Also, tapping "Yes" on "Was this reply helpful?" makes a big difference! Thanks! 😊

Regards,

[abcd1234502]

It seems another admin changed my user name to Abcd1234502?  Anyway, thank you for your reply. What you wrote makes sense. Unfortunately, it didn't seem to work (or I'm misunderstanding).

First, I reverted the driver back to the Windows default for the monitor. Then, I tried the BIOS option with several old HDMI cables. 

For UEFI, I don't have Fast Boot or Skip display initialization options. I do have an option for POST, which is set at 0.  I tried setting it to longer durations (up to 20) to see if that would make a difference, but it didn't. I also tried to see if there was a newer BIOS version available, and there was not. My version is showing AMI F.40 dated 3/6/2025 and SMBIOS 3.6. I remember on older version of BIOS seeing a Fast Boot option, but my version doesn't seem to have it.

Any other ideas?

[MasonVegas · Accepted solution]

Using a KVM switch solved the monitor problem for me.  I'm not going to use two monitors, but I'm still going to use the KVM as a pass-through to the AIO HDMI IN port until a better solution is found. The PC boots right past the KVM and once I press the KVM switch button, the monitor comes on. Even the built-in AIO speakers work. 

That still doesn't solve the webcam. I'd need updated Windows drivers for that, which was the original subject of this post, but I'll save that for another day I guess.