Display brightness at max after 1803 update

Three times on a row caused Windows 10 update 1803 me this screen brightness bug:

On a Lenovo T410, an old HP Probook and a younger model HP DV7.

Search results show many laptops users encounter this brightness bug and even worse;

it seems Microsoft has not released a proper solution or fix.

Instead Windows 10 users must experiment using old drivers, mess with registry settings or even rollback to the previous build...

(Especially wonderful for owners of a 16Gb or 32Gb Emmc device, where storage capacity forces to perform a new installation.)

How can it be that Windows 10 Version 1803 causes this screen brightness bug, on such a large scale, affecting many users?

Before official release it passed all kind of tests, Insider (fast, slow and release preview) rings;

was Microsoft unaware of this bug before official Version 1803 rollout ?!

Wishing good luck to all with this and any other energy and time consuming bug.

Due to a severe nerve illness I enjoy my good moments to help people with computer (Windows) problems. In other case I sure would consider using Linux on PC and laptop.

With excuses for my poor English, I am Dutch

I didn't understand the language you used, but thanks for answering.

Thank you Riccardo.

For anyone having problems with this, here is what worked for me. My Intel HD Graphics driver couldn't install due to the "This operation returned because the timeout period expired" error (0x000005b4).

Symptoms:

• Intel driver can't be installed from Windows Update, manually nor from Intel installer
• Advanced GPU features are not working (video acceleration, brightness can't be adjusted)

First solution to this problem is increasing the timeout period through Group Policy Editor (works only in Pro and higher editions): https://techjourney.net/change-device-installation-timeout-in-windows-fix-0x000005b4-error/

If that doesn't work (it didn't work for me), try this (tested on Windows 10 1803):

1. Open C:/Windows/INF. This is a driver store where Windows copies all the drivers that were installed at some point. In my case, the driver store was containing a corrupted copy of the Intel HD Driver which was overriding the new files - that's why I couldn't install new drivers.
2. Open this file: setupapi.dev.log.

This is a logfile of all driver installations, scroll to the bottom (for most recent entries) and look for this line: "<<<  [Exit status: FAILURE(0x000005b4)]"

Then scroll up and look for these - these lines confirm that the log entry is from installing Intel HD Graphics driver - here the driver installer decides to install the Intel driver over the generic Microsoft one:

"    dvi:                {Select Best Driver}

dvi:                     Class GUID of device changed to: {4d36e968-e325-11ce-bfc1-08002be10318}.

dvi:                     Selected Driver:

dvi: Description - Intel(R) HD Graphics Family

dvi:                          InfFile     - d:\downloads\inteldrivergen\graphics\igdlh64.inf

dvi:                          Section     - iHSWM_w10

dvi:                     Skipped Basic Driver:

dvi:                          Description - Microsoft Basic Display Adapter

dvi:                          InfFile     - C:\WINDOWS\INF\display.inf

dvi:                          Section     - MSBDA

dvi:                {Select Best Driver - exit(0x00000000)}"

Under these lines, there should be this section:

"     ndv:      Driver package 'C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_8237dc5d3c101a63\igdlh64.inf' is already imported.

sto:      {Setup Import Driver Package: d:\downloads\inteldrivergen\graphics\igdlh64.inf} 18:27:58.774

sto:           Driver package already imported as 'oem7.inf'.

*sto:      {Setup Import Driver Package - exit (0x00000000)} 18:27:58.868"*If you've found this, it means that installation continued from the driver store, not from wherever you're installing your driver. If you can't find this line, your problem is different than mine, so don't proceed with my solution.It's OK if the file contains more than one section looking like this, each one represents one failed attempt to install the driver. 3. Note down the filename from previous step

"sto:           Driver package already imported as 'oem7.inf'." 4. Find the file at C:/Windows/INF, open it and make sure that it contains: "Installation INF for the Intel Corporation graphics adapter" to make sure that you are going to delete the right driver. If the file contains names of other companies than Intel or it doesn't state it's for the graphics adapter, return to the previous step and check that you have the right file name and that you opened the right file. Don't proceed if you can't find INF file for your graphics adapter. 5. Open Command line with administrator privileges (Open Search, type "cmd", right-click Command Line and select Run as administrator).

Type this command and replace the <drivername.inf> with a file name from the previous step: "pnputil  /delete-driver <drivername.inf>"

Example: "pnputil  /delete-driver oem7.inf"

This will delete the Intel HD driver from the driver store. 6. Try to install your driver again, it should work now.

I will be very happy if I helped anyone with a similar problem. Good luck!

feature test control not found

1. Navigate to the following key:
   • HKEY_LOCAL_MACHINE/SYSTEM/ControlSet001/Control/Class/ 4d36e968-e325-11ce-bfc1-08002be10318 /0000
2. Double-click the item of FeatureTestControl, set the hexadecimal value to "fb20", and click OK.
3. Reboot your computer to reflect the changes.

:(

Try this location instead:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class{4d36e968-e325-11ce-bfc1-08002be10318}\0001