This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
hello , Yesterday I installed the 1809 update , and today i noticed that each time i restart my laptop the brightness level is being reset automatically to 0% or 25-50 i'm not really sure , and after windows will boot up , i will need to manually adjust the screen brightness again to 100% . I searched the web and i found this https://www.windowscentral.com/windows-10-october-2018-update-common-problems-and-fixes#fix\_brightness\_windows10\_1809 , and it might be an update issue i think , by the way , my power plan is set to maximum performance and my laptop is always plugged in , and solutions or ?
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.
What other features or functions will stop working if you disable this service?
I don’t see any problem on my laptop. Brightness control works, color profiles work. Maybe DisplayEnhancementService affects some rare features like automatic brightness adjustment etc. (if your laptop supports such features). BTW, Windows worked good for years without DisplayEnhancementService - it was added in 1803 update as far as I know.
What other features or functions will stop working if you disable this service?
The solution is to disable "Display Enhancement Service" (DisplayEnhancementService).
sc config "DisplayEnhancementService" start= disabled
sc stop "DisplayEnhancementService"
This issue has nothing to do with the actual issue of the thread starter, but worth a shot for people with the educational version of Windows. If you don't have an educational copy the solution won't work because it is a different problem. It has already been pointed out that the actual problem occurring since 1809 is a Windows problem which already has been fixed within the insider builds...
your issue is similar to this one.Do check it out
