i done nothing ... it 100% by it self .... so weird
Windows Brightness issue after the 1809 update
![](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)
Anonymous
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 ?
Windows for home | Windows 10 | Windows update
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.
184 answers
Sort by: Most helpful
-
Anonymous
2018-10-24T07:44:10+00:00 -
Anonymous
2018-10-23T20:47:33+00:00 accept it, wait or rollback simple as that, kk
-
Anonymous
2018-10-23T20:12:32+00:00 now what MS???? ... been 2 days now my brightness 100% by it self ... i am in high performance set ... i done no updates or anything .... how da ***** this could happen?
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Anonymous
2018-10-20T06:57:33+00:00 I know it is also to me AAF. However if you hate that current behaviour so much, use the described scheduler task this will immediately fix it, but as said this is just a temp fix :)