Thank you very much for helping me, it worked for me.
that does not mean that the problem is the
Windows Update April 10, 2018 (version 1803)
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello!
I upgraded my laptop over the weekend to Windows 10 1803. I noticed my display was set to max brightness. I am unable to use the F keys to lower the brightness. I am also unable to change the brightness in the display settings. My drivers are all updated. Any suggestions on how to fix this?
I have a Toshiba Satellite with the Intel (R) HD Graphics.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Thank you very much for helping me, it worked for me.
that does not mean that the problem is the
Windows Update April 10, 2018 (version 1803)
This solution from Ferdz Amp solved my problem.
For those still encountering this issue, I recommend that you follow these steps and see if the issue persists:
- In Windows start search box, type in regedit and hit Enter.
- Navigate to the following key:
- HKEY_LOCAL_MACHINE/SYSTEM/ControlSet001/Control/Class/ 4d36e968-e325-11ce-bfc1-08002be10318 /0000
- Double-click the item of FeatureTestControl, set the hexadecimal value to "fb20", and click OK.
- Reboot your computer to reflect the changes.
Registry Disclaimer: The steps mentioned here includes system registry modification. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow the steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: Article ID 322756.
Let me know how it goes.
The written location for FeatureTestControl was different on my system. The location was:
Please be aware that after doing this edit, selecting the lowest level of brightness will turn off your screen. This also means that if you are running on battery (laptop) and you select the power mode "Best battery life" or Windows automatically switches to "Best battery life" upon unplugging the charger, your screen will be turned OFF! This is not a major concern since you can just turn up the brightness to the next lowest level via the FN+F3 (key combo might differ on other laptop brands) keyboard control shortcut and the screen will be turned back ON.
Taken from here:
OS Name Microsoft Windows 10 Pro
Version 10.0.17134 Build 17134
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-JAFO621
System Manufacturer Dell Inc.
System Model Vostro 3300
System Type x64-based PC
System SKU To be filled by O.E.M.
Processor Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz, 2394 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date Dell Inc. A12, 08/04/2014
SMBIOS Version 2.6
Embedded Controller Version 1.02
BIOS Mode Legacy
BaseBoard Manufacturer Dell Inc.
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Mobile
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United Kingdom
Hardware Abstraction Layer Version = "10.0.17134.1"
Username DESKTOP-JAFO621\Muneeb Ejaz
Time Zone Pakistan Standard Time
Installed Physical Memory (RAM) 6.00 GB
Total Physical Memory 5.80 GB
Available Physical Memory 3.58 GB
Total Virtual Memory 7.43 GB
Available Virtual Memory 5.41 GB
Page File Space 1.63 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualisation-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not InstantGo, Un-allowed DMA-capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualisation Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
yo tengo el mismo problema él hizo todo y el problema sigue igual.
Nombre del SO Microsoft Windows 10 Pro
Versión 10.0.17134 compilación 17134
Descripción adicional del SO No disponible
Fabricante del SO Microsoft Corporation
Nombre del sistema ESCRITORIO-29V5QAJ
Fabricante del sistema Hewlett-Packard
Modelo del sistema PC portátil HP Pavilion dv6
Tipo de sistema PC basado en x64
SKU del sistema LE457EA # UUZ
Procesador Intel (R) Core (TM) i5 CPU M 480 a 2.67 GHz, 2667 Mhz, 2 procesadores principales, 4 procesadores lógicos
Versión y fecha de BIOS Hewlett-Packard F.29, 7/11 / 2011
Versión de SMBIOS 2.6
Versión de la controladora integrada 101.56
Modo de BIOS Heredado
Fabricante de la placa base Hewlett-Packard
Modelo de placa base No disponible
Nombre de la placa base Placa base
Rol de plataforma Móvil
Estado de arranque seguro No compatible
Configuración de PCR7 Enlace no posible
Directorio de Windows C : \ Windows
Directorio del sistema C: \ Windows \ system32
Dispositivo de arranque \ Dispositivo \ HarddiskVolume1
Configuración regional España
Capa de abstracción de hardware Versión = "10.0.17134.1"
Nombre de usuario DESKTOP-29V5QAJ \ kelvi
Zona horaria Hora estándar oeste, Sudamérica
Memoria física instalada (RAM) 4,00 GB
Memoria física total 3,80 GB
Memoria física disponible 1,62 GB
Memoria total virtual 5,93 GB
Memoria virtual disponible 3,27 GB
Espacio de archivo de paginación 2,13 GB
Archivo de paginación C: \ pagefile.sys
Protección de DMA de kernel Desactivada
Seguridad basada en la virtualización No habilitado
Compatibilidad con cifrado de dispositivo Razones del error de cifrado automático del dispositivo: No se puede usar TPM, No se admite el enlace PCR7, Error en la interfaz de seguridad de hardware y el dispositivo no se configura como InstantGo., Se detectó un bus o un dispositivo compatible con DMA que no se permite. No se puede usar TPM
Hyper-V - Extensiones de modo de monitor VM Sí
Hyper-V - Extensiones de traducción de segundo nivel Sí
Hyper-V - Virtualización habilitada en Firmware Sí
Hyper-V - Protección de ejecución de datos Sí
yesterday Microsoft released new cumulative update for 1803 with some fixes did that fixed your issue?