Disable Intel Display Power Saving Technology on Surface Pro 4

Stop your display from darkening unexpectedly even when adaptive brightness is disabled.

Advertisements

I recently bought a new Surface Pro 4. I run on battery often and configure the display’s brightness to 25% (with adaptive brightness disabled) to conserve battery.

With adaptive brightness disabled, my display would still occasionally darken or lighten unexpectedly, often to an uncomfortable level. After some experimentation, the trigger turned out to be what was visible on the screen. Darker content resulted in the display darkening, and lighter content resulted in the display brightening.

After some research, the culprit turned out to be Intel Display Power Saving Technology or DPST. The design of this Intel feature is precisely what I experienced: to save power by adjusting the display brightness depending on how dark or light the content on screen is.

While well intentioned, I found the experience incredibly disruptive given its slow and choppy transition and the uncomfortably dark end result. With my display brightness configured to 25% already, you can imagine how any darker might be uncomfortable, especially in adverse lighting conditions.

While on older desktops you could disable DPST via Intel’s driver configuration software, this software isn’t available on the Surface line with the recommended graphics drivers. While some might have success installing the latest available drivers and software from Intel directly, the steps can be complicated to replace the recommended drivers, and you risk introducing more problems with an untested configuration. My options seemed limited to living with it.

Fortunately, via work channels, I discovered an obscure registry key that can enable or disable Intel graphics features with the recommended graphics drivers.

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000]
"FeatureTestControl"=dword:00009240

The FeatureTestControl registry key is a bit field where each bit represents a feature. A value of 0 indicates the feature is enabled, and a value of 1 indicates the feature is disabled. The Intel graphics driver reads this registry key on initialization to determine which features to enable. The bit corresponding to DPST is the fifth bit from the right.

To disable DPST, you’ll need to set the DPST bit to 1. If the value of the registry key is 9240 as shown above, simply replace it with 9250. If the value on your system differs and you are unsure if DPST is already disabled, enter the existing hex value into Calculator’s Programmer mode (select HEX before entering the number) and switch to its bit toggling keypad to check the value of the DPST bit (position 4). If it is already set to 1, then DPST is already disabled. If not, click the bit to toggle it to 1, then copy the updated hex value into the registry. If updated correctly, the only number that should be different is the 4 (or whatever number was in that position), and it should be odd (or b, d, or f for the hex representation of 11, 13, or 15).

Reboot to ensure the graphics driver reconfigures itself, and DPST will be disabled.

Note: OS updates appear to reset the FeatureTestControl registry key back to its default value. If you notice that DPST has been reenabled, you’ve likely taken an OS update and will need to reconfigure the value in the registry again. Also, the registry key may be under […\0001] rather than […\0000] depending on the system and OS version installed.

28 thoughts on “Disable Intel Display Power Saving Technology on Surface Pro 4”

  1. Do you have any info on what each bit represents? The 5th from the right is the power saving, but is there one for adaptive contrast enhancement? Thanks for the informative post.

    Like

  2. Hi Mike, All,

    thanks for posting this solution. I have previously applied it on my surface and it has worked perfectly.

    now i also want to disable this feature on my PC (Dell), and i’m getting hex value 8200. I have tried calculator, but it looks like Chinese to me.

    Could you help me to obtain the right hex value ?

    thank you so much!

    greets
    Peter

    Liked by 1 person

      1. Hi Ray, Could you please help me out here? I’m getting since recently (drive update) value of c200 in the FeatureTestControl.. which value shall i replace it with? Thank you,

        Like

  3. i can’t tell you how helpful this article is. i’ve searched through countless forums and all they ever talk about is the adaptive brightness feature or power settings. both of which have nothing to do with this particular issue. this is now the third time i have used this article because windows updates tend to reset this registry key.

    i’ve actually clipped this post in my evernote for faster reference in the future. i wanted to make sure i said thank you, though, because MAN have you made my video streaming life much better. haha.

    i can’t thank you enough, mike. cheers.

    Like

  4. Thanks! I wanted to note that on my Surface Pro (5th gen) it was under 0001 not 0000:

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

    Liked by 1 person

    1. Hi Nick, I also have a 5th gen so would like to use your solution.
      I’m a newbie to this coding portion, where do I go to put your above info into?
      Thank you for your help.

      Like

  5. Man, I was expiriencing the same issue on my new 2017 Surface Pro. Thanks so much for sharing this valuable tip, much appreciated! Works perfectly there, too. Take care!

    Like

    1. Give that man a cookie….! You should be hired by Intel.
      For those that have C200 ( as I had) value just replace with C208
      I fixed that to my Surface Pro 2 windows 10.

      Like

  6. I found this solution last week and was delighted. A Windows update I installed today rendered it ineffective. I cannot even find the same “FeatureTestControl” key under the same branch of the Registry. If you happen to know where it moved I and many others who benefited from this solution will be grateful.

    Thank you,

    Cemal

    Like

    1. In answer to my own question, the key has moved from the 0000 branch to the 0001 branch under the same registry entry with the same hex value.

      Cemal

      PS you may just ignore my message and after validating my finding just update your instructions for others to benefit.

      Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s