Again the registry key will be targeted for specific laptop models only so unless we know which laptop model is impacted it will not be added to our future drivers. That should be fine but it may be best if the other users impacted by this problem submit a bug to NVIDIA. If this did not work for you, here's an extract from my Personal Assistance question. Click OK to save.ĥ) This solution is for selected laptop models. Once key has been created, double click the new key and then add the "0x800" to Value data area. Label the name of the new key as "RMBrightnessControlFlags".Ħ.
Create a new key by right-clicking on the right-hand pan of the registry editor window and then select "New" > "DWORD (32-bit) Value".ĥ. It should bring up the registry editor and take you directly to the location where all the NVIDIA driver settings are store.Ĥ. This tool will take you directly to the registry location where all the graphics drivers registry entries are stored.ģ. Download the "DispRegEdit.exe" tool from to your local system. Make sure you are running the 314.21 driver.Ģ. ģ) Check if you are able to change your brightness.ģ) I f the "Enable adaptive brightness" option does not impact issue then try following the steps below to add a registry and see if that helps.ġ. You can access it via the Windows control panel > Power Options > Change plan settings (which ever plan is active) > Change advanced power settings > Display > Enable Adaptive Brightness. This option is located under the Windows 8 power options. Here are the steps to follow to enable your brightness setting:ġ) Download the latest 314.21 beta driver (haven't tested this on the current driver) here: and perform a clean install.Ģ) check if "Enable adaptive brightness" option is enabled and if yes try turning it off to see if that will help. I contacted Nvidia and they have given me the solution.
Have an Nvidia Graphics driver and cannot change your brightness? I also had the same problem after upgrading my Lenovo G460 to Windows 8 Pro. Please see this post for more Informaiton UPDATE : The new drivers have fixed the issue.
0 kommentar(er)
