-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Video, Display and Touch
- Brightness controls not working after Windows 24H2 update

Create an account on the HP Community to personalize your profile and ask a question
03-21-2025 09:47 AM - edited 03-21-2025 09:49 AM
Hello,
I am currently facing issues with my brand new HP Probook 465 G11. When I got it I updated all the neccessary drivers using Windows Update and also the HP Support Assistant app and everything worked perfectly, However, the second day Windows Update offerd me a new version of Windows (24H2), so I downloaded it and installed it and presumably after that my brightness controls stopped workeng. The function keys work properly and control the Windows brightness slider, but the brightness of the internal screen of the laptop does not change and always stays at 100% no matter what (even though I specifically remember it working when I first got the laptop.
So firstly, I went and made sure all the drivers were up to date, which they were (Both according to Windows Update and HP Support Assistant), then I made sure BIOS (UEFI) was up to date, which it aslo was. I tried different diagnostics offer by HP Support Assistent and the UEFI and they were all successful. So then I tried reverting to the previous build of Windows using Windows Update, but that did not fix the issue, so I tried reseting the computer to factory settings, but that also didnt fix the brightness issue.
So currently I am on Windows 11 23H2 (Windows Update doesnt even offer me 24H2 now), I have all the latest drivers, the latest UEFI version, but the brightness is still stuck at maximum level even if I change the brightness level in Windows.
I wonder if it could be an issue with the latest AMD drivers or perhaps with HPs ACPI tables. Is there anything I could do right now to fix this?