orev / dpst-control Goto Github PK

In my case, there are multiple subkeys under HKLM:\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318} with a value named FeatureTestControl, and only by editing the 3rd key did the trick work. So this should return a list of all suitable subkeys instead of only returning the first subkey found.

This is not working on my Surface Laptop 3 15" (AMD Ryzen 5)

When execute the bat i get:

C:\Users\conta\Desktop\dpst-control-master\dpst-control.ps1 : Cannot locate FeatureTestControl in registry
In C:\Users\conta\Desktop\dpst-control-master\dpst-control.ps1:139 Zeichen:5
+     Write-Error "Cannot locate ${ftcName} in registry"
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,dpst-control.ps1

Hi,

I have a Surface Pro (2017) with Windows 10.0.19042 and since couple of win updates the fix doesn't work anymore for me.

I found this article which suggests some additional registry key and it worked for me.
I just applied them all so I cannot really say which one did the trick.

Source: Disable adaptive contrast/brightness on new UWD/DCH drivers

Windows Registry Editor Version 5.00
;Disable DPST on Intel UWD/DCH drivers - dancharblog
;
; -----Instructions: -----
;- copy this text into notepad
;- save as DPST-off.reg
;- double-click the file and follow the prompts to import changes
;- reboot
;- if the changes don't do anything, in the line below that starts with "[HKEY_" change "\0001" to "\0000" or "\0002" and retry the above steps
; ------------------------
;
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0001]
"ACUserPreferencePolicy"=dword:09020000
"DCUserPreferencePolicy"=dword:09020000
"DisplayFeatureControl"=dword:000003e3
"Dpst6_3ApplyExtraDimming"=dword:00000000
"FeatureTestControl"=dword:00008200
"PowerAcPolicy"=dword:c1bac1ba
"PowerDcPolicy"=dword:c9bac0b8
"PowerDpstAggressivenessLevel"=dword:00000001
"PowerGpsAggressivenessLevel"=dword:00000001
"PowerPlanAwareFeatureSettings"=hex:ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,02,01,02,00,00,00,02,01,02,00,02,01,02,01,02,00,02,01,02,01,02,00,02,01,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,06,00,00,00,04,00,00,00,00,01,00,00,06,00,00,00,04,00,00,00,00,01,00,00,06,00,00,00,01,00,00,00,00,01,00,00,06,00,00,00,04,00,00,00,00,01,00,00,06,00,00,00,04,00,00,00,00,01,00,00,06,00,00,00,04,00,00,00,00,01,00,00,06,00,00,00,04,00,00,00,00,01,00,00,06,00,00,00,04,00,00,00,00,01,00,00,06,00,00,00,04,00,00,00,00,01,00,00,06,00,00,00,04,00,00,00,00,01,00,00,06,00,00,00,04,00,00,00,00,01,00,00,06,00,00,00,04,00,00,00,00,01,00,00

In the past, (Win10 1803) I had the issue that the built in Intel HD Graphics was actively changing the contrast of my laptop monitor while it's running in battery mode. For example, when a dark color is being displayed , the entire screen would become lightened and when a light image is being displayed, the entire screen would become darkened.

I was able to get around the issue (for battery mode) by disabling that feature from the Intel HD Graphics Control Panel. This problem also exists for when the laptop is in plugged-in mode (and there is no option to turn it off under plugged-in mode in the Intel HD Graphics Control Panel), but I was also able to get around this problem in plugged-in mode by following this post:

laptop-monitor-brightness-changes-depending-on-image-displayed

by using the "DCUserPreferencePolicy" registry value technique.

However, since updating to Win10 1903 in the past few days, I found the problem is back (for plugged-in mode). I stumbled across your repo while looking for a solution to this annoying problem and gave your scripts a try. However, I suspect it's not working (from my own testing when my laptop is in plugged-in mode). The built-in Intel HD graphics chip is altering my screen contrast again.

Could you please verify to see if the scripts work for Win10 1903? I saw in your ReadMe that you verified for Win10 builds prior to Jan 2019.

Some info regarding my specs:

• Intel HD Graphics 630
• Driver version: 21.20.16.4550 (quite old, I know. But this is the only driver I've used and managed to get around the problem for both plugged-in mode and battery mode)