Windows 10: Компьютер сам просыпается рано утром
Сегодня мне приснился сон: я рассказывал жене, что узнаю играющий трек и вот-вот пойдет «расколбас». Трек был от одного из моих любимых продюсеров Евгения Смирнова. Спустя пару секунд, я проснулся и действительно довольно громко в соседней комнате играл трек от Omnia и всё бы ничего, если бы на часах не было время 4:45 утра. Продрав глаза, я подумал, что кошка шарилась по моему столу и нажав кнопку на клавиатуре, вывела комп из режима «Сон». Однако, когда я встал с кровати, увидел кошку мирно спящую «в ногах». Я выключил комп и пошел спать дальше. Что же произошло? Какого хрена комп сам включился?
Оказывается, все довольно просто. На этот раз, это был не Google Chrome, а Windows 10, решивший что именно сейчас ему надо обновить Orchestrator. Что это за такая важная приблуда, я не особо разобрался.. да и не важно.
Самое главное, что я хотел бы рассказать, это как найти и обезвредить подобное поведение, ведь все мы любим ночью спать.
Все примеры (скриншоты) привожу для Windows 10, для более ранних версий этапы должны быть очень похожими или точно такими же..
- Самое первое, что нужно сделать в случае если у Вас такое произошло, это разобраться кто именно и каким образом вернул компьютер из режима «Сон». Для этого, нажимаем правой кнопкой на «Пуск» (в Windows 10) или на «Мой компьютер» (в предыдущих версиях) и выбираем пункт «Управление компьютером»:
Так же существует еще один способ запуска, данной оснастки: нажать Win+R и в открывшееся окно ввести compmgmt.msc
В открывшемся окне, в левой его части, в дереве выбрать такой путь:
— Управление компьютером
— Служебные программы
—— Просмотр событий
———- Журналы Windows
————— Система
Системный журнал событий Windows
4:45. В принципе, если вы выключили компьютер, например в 19:00, а включился он только в
4-5, то вы без проблем найдете этот разрыв:
Виновник выхода ПК из сна
Система вышла из состояния пониженного энергопотребления.
Время перехода в спящий режим: 2015-08-19T16:32:28.789995400Z
Время выхода из спящего режима: 2015-08-20T01:44:32.479224100Z
Источник выхода: Таймер — Будет выполнено назначенное задание «NT TASK\Microsoft\Windows\UpdateOrchestrator\Reboot», запросившее вывод компьютера из спящего режима.
Тут мы видим, во-первых, что произошло, а во вторых, кто вывел систему из сна. В нашем случае это «NT TASK\Microsoft\Windows\UpdateOrchestrator\Reboot«, запоминаем этот путь.
Теперь когда мы знаем виновника, настала пора его наказать. Для этого открываем планировщик заданий. Сделать это можно либо в этом же окне, либо нажав Win+R и написав туда: taskschd.msc . Я буду делать все в том же окне:
Отключение пробуждения ПК
Теперь вы знаете, как найти и обезвредить задания, которые пробуждают ваш ПК среди ночи..
Честно говоря, я не знаю чем думали разработчики, установив подобную задачу, но знаю точно, головой думали мало..
Желаю всем спокойных снов 🙂
— [добавлено 30.08.2015] —
Проснувшись сегодня утром, я опять обнаружил свой ПК включенным. Изучив события, я опять наткнулся на Orchestrator. Как оказалось, это событие, создается другим приложением, и его отключение не повлияет на его повторный запуск (т.к. оно будет пересоздано). Немного погуглив, я наткнулся на топик: Computer wakes up every night from sleep, здесь предложили такое решение:
I came to this thread after updating to Windows 10 and encountering issues with my computer not staying asleep when I came back to it the next day. I had not thought of looking in the group policy details for this kind of a setting. Here I thought I was being pretty savvy just going to the Event Viewer to find the root of my problem 🙂
I found your advice useful, but I think there might be a more broad solution for anyone who «just wants their computer to stay asleep.» I say this because this is not the first thing in the event logger that I’ve found as a cause of my computer waking. (Media Center updates with this scheduled task ‘NT TASK\Microsoft\Windows\Media Center\mcupdate_scheduled’ were also causing the computer to wake).
As I read through the documentation in the group policy editor for the ‘Enabling Windows Update Power Management to automatically wake up the system to install scheduled updates’ setting, it says «Specifies whether the Windows Update will use the Windows Power Management features to automatically wake up the system from hibernation, if there are updates scheduled for installation.»
This made me wonder. what are my settings in power management that relate to allowing it to wake? I then found that in Control Panel > Power Options > Edit Plan Settings > Change advanced power settings you can then expand Sleep > Allow wake timers. Here you can choose
Your solution is certainly correct and concise, but if you want the nuclear option, this power management option seems to be a good solution.
Нас интересует выделенная часть. Вкратце в ней говорится, что в Плане управления питанием, есть опция позволяющая Разрешить/Запретить таймеры пробуждения. И что на самом деле, пробуждение компьютера занимается Windows Update который помимо всего прочего еще и перезагружает компьютер без вашего ведома.. Ну, что же попробуем это решение:
- Открываем настройки Электропитания, для этого нажимаем Win+R и в открывшееся окно вводим powercfg.cpl . Второй способ это:
Пуск>Параметры>Система>Питание и спящий режим>Доп. параметры питания - В открывшемся окне, нажимаем Настройка схемы электропитания
- Теперь нажимаем Изменить доп. параметры питания
- В открывшемся окне, раскрываем пункт Сон>Разрешить таймеры пробуждения и в пункте «Значения«, выбираем «Отключить
Отключение таймеров пробуждения
Надеюсь, теперь комп не будет просыпаться. И приход скайнета отложится до следующей переустановки винды 🙂
UpdateOrchestrator Reboot task bug
I’ve disabled the group policy of «Enabling Windows update power management to automatically wake up the system to install scheduled updates» in the hope of stopping my computer from waking up from hibernate — it’s a fairly loau desktop so it waking up means I wake up.
Disabling this policy changed the Reboot task to run a action of «Schedule Restart» — but that task still has the flag set to enable it to wake up the computer. So in affect, it wakes up my desktop to ask me when to schedule a restart. great.
I’ve tried writing a powershell script which fires on hibernate and disables this specific task, but seemingly it only works some of the time.
Editing the reboot task does not work, it must get routinely deleted / recreated by windows.
It seems like an immensely stupid condition to have, and I can’t imagine I’m the only one with a desktop in my room.
Microsoft — please can I have *some* power back.
Anyone got any sure fire methods of killing this task for good?
Replies (6)
Thank you for contacting Microsoft Community.
This issue might be to corrupted power settings.
To diagnose and fix this issue, try the following methods.
Method 1: Power troubleshooter.
I would suggest you to run the Power troubleshooter and check if it helps.
- Press the ‘ Windows + X’ key on the keyboard.
- Type troubleshooter in the search box and then press Enter.
- Select Troubleshooting . Click on view all and select Power.
- Click next and follow the on-screen instructions.
If the issue still persist follow the below method.
Method 2: Restore Power Option Settings.
I would suggest you to restore default settings of power plan and check if it helps.
- Press Windows + x , and select the option Control Panel.
- Click on the Power Options icon.
- Click on Change advanced power settings .
- Select the option “ Restore default settings for this plan ”.
Hope this information is helpful and do let us know if you need further assistance. We will be glad to assist.
Did this solve your problem?
Sorry this didn’t help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this response?
Thanks for your feedback.
Why do you think this is due to corrupt power settings?
Did this solve your problem?
Sorry this didn’t help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this response?
Thanks for your feedback.
marlon_tucker has a valid point. And it’s not corrupt power settings. Why must Microsoft always assume something’s corrupt? The only thing corrupt is Microsoft thinking they need to take total control of our computers and not letting people who know what they’re doing have any control at all.
Yesterday I applied the latest updates and rebooted to finish them. Yet Microsoft *still* set the Reboot task in UpdateOrchestrator to reboot my machine at 3:30am. WHY. There was nothing left to finish. You know I rebooted my machine. So why schedule it again?
It wouldn’t be so bad if Microsoft wakes up my machine in the middle of the night to do whatever, but it NEVER PUTS IT BACK TO SLEEP!! Why not? So I wake up to a machine that’s been on and doing who knows what (since you never tell us what) all night long. You didn’t even tell me that the reboot task was set so I get to wonder what’s going on and spend MORE of my time researching it. Thanks so much!
As marlon_tucker asks: «Microsoft — please can I have *some* power back. «
7 people were helped by this reply
Did this solve your problem?
Sorry this didn’t help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this response?
Thanks for your feedback.
It’s 6 AM here, in a few minutes. I usually wake up at 8 AM, but today is a very special day.
I had a weird dream, it woke me up. Trying to fall asleep again, I noticed the silent hum of my PC’s fans. I put it to sleep again by a few key strokes, lied on the bed again and tried to fall asleep. A few moments later, not sure how long after, I heard it waking up from sleep mode again.
But what woke up my PC? I have Wake on LAN disabled, I have Power Settings set so that no scheduled tasks wake up PC from sleep. I have even gone as far as setting UpdateOrchestrator’s Reboot task not to wake up my PC. But I was suspecting this one and I was damn right about that. When I found that task, it showed that it successfully ran just few minutes ago.
And it was all enabled again. To wake up my PC and make my life a walk in hell. So I didn’t stick to just disabling it. I went to Windows/Tasks folder, made myself the sole owner and administrator and locked SYSTEM users out of doing anything but reading and executing. Am I sure this is safe? Nope.
But especially when I go to work, I want to have a good night’s sleep. I was deprived of that today. Please find out what incompetent bunch of fools made UpdateOrchestrator to bypass the Power Settings configuration. Don’t tell them. Don’t fire them. Just keep waking them up every single night at 2 AM to 5 AM when it hurts the most. Until they realize it is not a great idea to do that to users. Thanks in advance. (Even though I doubt anyone will do that.)
UpdateOrchestrator Reboot task bug
I’ve disabled the group policy of «Enabling Windows update power management to automatically wake up the system to install scheduled updates» in the hope of stopping my computer from waking up from hibernate — it’s a fairly loau desktop so it waking up means I wake up.
Disabling this policy changed the Reboot task to run a action of «Schedule Restart» — but that task still has the flag set to enable it to wake up the computer. So in affect, it wakes up my desktop to ask me when to schedule a restart. great.
I’ve tried writing a powershell script which fires on hibernate and disables this specific task, but seemingly it only works some of the time.
Editing the reboot task does not work, it must get routinely deleted / recreated by windows.
It seems like an immensely stupid condition to have, and I can’t imagine I’m the only one with a desktop in my room.
Microsoft — please can I have *some* power back.
Anyone got any sure fire methods of killing this task for good?
Replies (6)
Thank you for contacting Microsoft Community.
This issue might be to corrupted power settings.
To diagnose and fix this issue, try the following methods.
Method 1: Power troubleshooter.
I would suggest you to run the Power troubleshooter and check if it helps.
- Press the ‘ Windows + X’ key on the keyboard.
- Type troubleshooter in the search box and then press Enter.
- Select Troubleshooting . Click on view all and select Power.
- Click next and follow the on-screen instructions.
If the issue still persist follow the below method.
Method 2: Restore Power Option Settings.
I would suggest you to restore default settings of power plan and check if it helps.
- Press Windows + x , and select the option Control Panel.
- Click on the Power Options icon.
- Click on Change advanced power settings .
- Select the option “ Restore default settings for this plan ”.
Hope this information is helpful and do let us know if you need further assistance. We will be glad to assist.
Did this solve your problem?
Sorry this didn’t help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this response?
Thanks for your feedback.
Why do you think this is due to corrupt power settings?
Did this solve your problem?
Sorry this didn’t help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this response?
Thanks for your feedback.
marlon_tucker has a valid point. And it’s not corrupt power settings. Why must Microsoft always assume something’s corrupt? The only thing corrupt is Microsoft thinking they need to take total control of our computers and not letting people who know what they’re doing have any control at all.
Yesterday I applied the latest updates and rebooted to finish them. Yet Microsoft *still* set the Reboot task in UpdateOrchestrator to reboot my machine at 3:30am. WHY. There was nothing left to finish. You know I rebooted my machine. So why schedule it again?
It wouldn’t be so bad if Microsoft wakes up my machine in the middle of the night to do whatever, but it NEVER PUTS IT BACK TO SLEEP!! Why not? So I wake up to a machine that’s been on and doing who knows what (since you never tell us what) all night long. You didn’t even tell me that the reboot task was set so I get to wonder what’s going on and spend MORE of my time researching it. Thanks so much!
As marlon_tucker asks: «Microsoft — please can I have *some* power back. «
7 people were helped by this reply
Did this solve your problem?
Sorry this didn’t help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this response?
Thanks for your feedback.
It’s 6 AM here, in a few minutes. I usually wake up at 8 AM, but today is a very special day.
I had a weird dream, it woke me up. Trying to fall asleep again, I noticed the silent hum of my PC’s fans. I put it to sleep again by a few key strokes, lied on the bed again and tried to fall asleep. A few moments later, not sure how long after, I heard it waking up from sleep mode again.
But what woke up my PC? I have Wake on LAN disabled, I have Power Settings set so that no scheduled tasks wake up PC from sleep. I have even gone as far as setting UpdateOrchestrator’s Reboot task not to wake up my PC. But I was suspecting this one and I was damn right about that. When I found that task, it showed that it successfully ran just few minutes ago.
And it was all enabled again. To wake up my PC and make my life a walk in hell. So I didn’t stick to just disabling it. I went to Windows/Tasks folder, made myself the sole owner and administrator and locked SYSTEM users out of doing anything but reading and executing. Am I sure this is safe? Nope.
But especially when I go to work, I want to have a good night’s sleep. I was deprived of that today. Please find out what incompetent bunch of fools made UpdateOrchestrator to bypass the Power Settings configuration. Don’t tell them. Don’t fire them. Just keep waking them up every single night at 2 AM to 5 AM when it hurts the most. Until they realize it is not a great idea to do that to users. Thanks in advance. (Even though I doubt anyone will do that.)