The Adaptive Brightness setting in Windows 10 is a useful setting you can use in adjusting your computer’s brightness. It helps you get the brightness automatically based on the light around your computer. However, there are times when it does not work or it doesn’t turn off when you want it to. If this issue happened right after you update or install Windows 10, then read on as this post will give you a couple of options you can try to resolve the problem.
The first thing you can do to resolve the issue with Adaptive Brightness is to run the Power Troubleshooter as the problem could occur due to some conflicted power settings. To use it, refer to the following steps:
The problem might be due to the Graphics card settings. If you are using either an AMD graphics card or the HD graphics of Intel, you may have to disable the power-related options in the GPU settings. To be specific, you have to disable the Vari-Bright in AMD graphics card settings or the Display Power Saving Technology under Intel’s Graphics panel.
You might also want to use a command-line tool to resolve the problem. This command-line tool is known as PowerCfg. It is a command utility tool that will scan your computer for 60 seconds to know its power. This tool gives detailed results in the form of an HTML report that will help you in evaluating the real cause of the battery drain issues. You can also use this tool to reset the Power Plan defaults of your computer. To use it, follow the steps below.
powercfg –restoredefaultschemes
Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.
Since you will be dealing with Registry files in this post, you need to create a System Restore point first. Once you have that covered, proceed to the following steps:
“We’re having trouble restarting to finish the install, Error 0x8024a11a, 0x8024a112, 0x80070005 or 0x80070032”And so to fix this problem, this post will give you a couple of possible solutions. Refer to the options given below to get started.
SC config trustedinstaller start=auto
powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRootWinStoreAppxManifest.xml