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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-10-24T07:04:35+00:00

    If you create Scheduler Task to reset your brightness to 100% at logon using the command below, this does work, but I have found that the brightness dims again somewhere between 10-15 minutes, so I have set the task to run every 10 minutes. Seems to be working.

    C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe "(Get-WmiObject -Namespace root/WMI -Class WmiMonitorBrightnessMethods).WmiSetBrightness(1,100)"

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-10-23T20:47:33+00:00

    accept it, wait or rollback simple as that, kk

    Was this answer helpful?

    0 comments
  3. 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?

    Was this answer helpful?

    0 comments
  4. 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

  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