Dude...You don't understand...We all know how to do this...And it's bug...
Windows Brightness issue after the 1809 update
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: Newest
-
Anonymous
2018-10-11T04:40:57+00:00 -
Anonymous
2018-10-11T01:47:07+00:00 seriously MS should hire you .... another human with cow head ... thinks we crying for this ..... brightness is a very tiny issue if u compare to the rest of the **** update issues ..... go to somewhere else that really could fit u... dumb
-
Anonymous
2018-10-10T22:10:49+00:00 Yes, I had the same experience -- today booting up, back to dim screen.
At least the control works to recover, but....
They're in a lot of deserved trouble over the file deletions - had reports, didn't look at them.
Just possibly, the fallout will result in changes making this less Mickey-Mouse
Which would be good...
-
Anonymous
2018-10-10T22:09:32+00:00 OMG! Ebubekir SafakBAYAR has the solution!! Are you retarded? Nobody is crying, we are talking about the bug after the 1809 update, your stupid solution of course it doesn't work, but maybe you should find a job in Windows, I think you would fit well.
Windows please fix the bug if you are able to do it!!
-
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