Windows Brightness issue after the 1809 update

Anonymous
2018-10-04T18:39:30+00:00

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.

0 comments

184 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-10-18T16:10:50+00:00

    That sounds great thanks for sharing! :)

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-10-19T07:24:38+00:00

    It is good to hear that this issue has been addressed. But the question is, will MS provide us fix on top of 1809 which is not some preview evaluation nor windows insider version? We need a fix also for the regular versions.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-10-19T09:46:13+00:00

    They will probably will fix it in some KB in the near future after it has been proven to be stable, so we can just wait ;)

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2018-10-19T23:42:00+00:00

    I hope you're right because this issue is annoying af

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. 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 :)

    Was this answer helpful?

    0 comments