Windows 10: Wake Timers "Important" not "Enabled"

[chairmanmao]

Periodically I run into a problem with Sage v9 running under Windows 10 where Sage will not wake up to handle a scheduled recording.

In rooting around through various Windows settings, I noticed that under advanced power options, wake timers was set to "Important Wake Timers Only". Prior to Windows 10, the only choices were Enable or Disable. The "Important Wake Timers Only" is a recent addition.

What's confusing me is I ran into this problem, on the same machine, once before...and at that time set the option back to Enable. Yet something reset the option at some point.

I suspect some Windows patch or upgrade (I have installed the Fall 2018 update) changed the setting...which, if true, would really piss me off at Microsoft .

Has anyone else run into this problem? If you have, have you found a way to make Enable sticky?

[EnterNoEscape]

Originally Posted by chairmanmao

Periodically I run into a problem with Sage v9 running under Windows 10 where Sage will not wake up to handle a scheduled recording.

In rooting around through various Windows settings, I noticed that under advanced power options, wake timers was set to "Important Wake Timers Only". Prior to Windows 10, the only choices were Enable or Disable. The "Important Wake Timers Only" is a recent addition.

What's confusing me is I ran into this problem, on the same machine, once before...and at that time set the option back to Enable. Yet something reset the option at some point.

I suspect some Windows patch or upgrade (I have installed the Fall 2018 update) changed the setting...which, if true, would really piss me off at Microsoft .

Has anyone else run into this problem? If you have, have you found a way to make Enable sticky?

I personally haven't had this problem, but I can empathize with Windows 10 arbitrarily deciding to drop your preference. I am responsible for OS deployment for over 8000 workstations and the nicest thing I can say about the in-place upgrades are they are very poorly thought out for enterprises. Based on my experience as a customer that is supposed to be able to control the OS to a very high degree, I can only imagine what home users deal with.

At home, when Windows 7 runs out of support, I'm moving my remaining computers to a Linux distro for not only this reason, but mainly because of how they still develop Windows. They really need to get their act together.

[SHS]

Originally Posted by chairmanmao

Periodically I run into a problem with Sage v9 running under Windows 10 where Sage will not wake up to handle a scheduled recording.

In rooting around through various Windows settings, I noticed that under advanced power options, wake timers was set to "Important Wake Timers Only". Prior to Windows 10, the only choices were Enable or Disable. The "Important Wake Timers Only" is a recent addition.

What's confusing me is I ran into this problem, on the same machine, once before...and at that time set the option back to Enable. Yet something reset the option at some point.

I suspect some Windows patch or upgrade (I have installed the Fall 2018 update) changed the setting...which, if true, would really piss me off at Microsoft .

Has anyone else run into this problem? If you have, have you found a way to make Enable sticky?

Usually causes by windows update
Usually causes by power management

Now, open Settings >System > Power & sleep > Addtional Power Settings.
Under Choose to customize a power plan, expand the option which says “Unhide Additional plans.”
If you do not see Ultimate Performance Mode, then follow the next steps.
Open a Command Prompt as administrator.
In the command prompt, copy the following command, and hit Enter.
powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61

May sure the system auto login to desktop

[peternm22]

I ran into another problem with Windows 10 wake timers and SageTV earlier this year: https://forums.sagetv.com/forums/showthread.php?t=65426

Sometimes when the computer would come out of sleep, SageTV would think the system was deadlocked when it was sleeping and nothing would get recorded.

I could never figure out how to fix it, and just stopped using sleep mode because of it. Coming home to have my SageTV server missing a bunch of recordings was more than a bit annoying.

Before that, I couldn't use sleep mode because my R5000 tuner wouldn't work after the computer came back from sleeping. When I got rid of the R5000, I figured I could finally use sleep mode. No such luck

[KryptoNyte]

Originally Posted by EnterNoEscape

I personally haven't had this problem, but I can empathize with Windows 10 arbitrarily deciding to drop your preference. I am responsible for OS deployment for over 8000 workstations and the nicest thing I can say about the in-place upgrades are they are very poorly thought out for enterprises. Based on my experience as a customer that is supposed to be able to control the OS to a very high degree, I can only imagine what home users deal with.

At home, when Windows 7 runs out of support, I'm moving my remaining computers to a Linux distro for not only this reason, but mainly because of how they still develop Windows. They really need to get their act together.

Our office machines are static IP for a smaller peer-to-peer network for various reasons, and every time they get a NIC driver update, they are off the network. The best part is when the update comes for 25% of the machines over a period of 4 to 6 nights - even after the static IP is reinstated, the older version machines won't communicate with the newer version machines.

With the amount of additional IT dollars spent in just one day trying to fix whatever a Windows 10 update has done to cripple the computers the previous night, it seems like there would be some kind of class action lawsuit so that the consumers would at least have the option to opt out of updates. This claim of forced updates for security reasons just seems like an excuse to grab full control of machines across the planet.

[trk2]

I have found Win 10's "hybrid sleep" and "fast startup" features to cause issues. Once I disabled those features and made sure the server was sleeping to an S3 state, my wake and stability issues went away.

[peternm22]

Originally Posted by trk2

I have found Win 10's "hybrid sleep" and "fast startup" features to cause issues. Once I disabled those features and made sure the server was sleeping to an S3 state, my wake and stability issues went away.

Thanks for the idea. I just disabled both of those, and I'm going to try sleep mode again on my server.

[Taddeusz]

Originally Posted by KryptoNyte

Our office machines are static IP for a smaller peer-to-peer network for various reasons, and every time they get a NIC driver update, they are off the network. The best part is when the update comes for 25% of the machines over a period of 4 to 6 nights - even after the static IP is reinstated, the older version machines won't communicate with the newer version machines.

With the amount of additional IT dollars spent in just one day trying to fix whatever a Windows 10 update has done to cripple the computers the previous night, it seems like there would be some kind of class action lawsuit so that the consumers would at least have the option to opt out of updates. This claim of forced updates for security reasons just seems like an excuse to grab full control of machines across the planet.

Yuck, I don't care how small the network. Static IP's are a PITA to maintain. I would rather manually assign addresses through DHCP and keep the workstation configuration simpler.

[chairmanmao]

Thanx for all the helpful info!

[KryptoNyte]

Originally Posted by Taddeusz

Yuck, I don't care how small the network. Static IP's are a PITA to maintain. I would rather manually assign addresses through DHCP and keep the workstation configuration simpler.

Apparently there is a reason why we don't do that having something to do with some legacy engineering stuff that we can't ditch. I will check on it, though.

Static IP obviously isn't the only thing that Microsoft screws up these days, there is a long list of computers that come my way that can't boot up any longer after a Win 10 update (friends and family) and so far the Win 10 repair has not been capable of fixing a single one. I finally figured out that one of the updates was to a desktop machine's wireless network card - although Microsoft claimed that I needed to clean install Win 10. After finding the convoluted method of safe booting Win 10 on a machine that won't boot, I disabled the wireless adapter and all of a sudden everything was fine.

Windows 10 is turning into a multi-trillion dollar joke.

[SHS]

Originally Posted by KryptoNyte

Windows 10 is turning into a multi-trillion dollar joke.

LoL you got that right 19 October update is a major joke

[Taddeusz]

Originally Posted by KryptoNyte

Apparently there is a reason why we don't do that having something to do with some legacy engineering stuff that we can't ditch. I will check on it, though.

Static IP obviously isn't the only thing that Microsoft screws up these days, there is a long list of computers that come my way that can't boot up any longer after a Win 10 update (friends and family) and so far the Win 10 repair has not been capable of fixing a single one. I finally figured out that one of the updates was to a desktop machine's wireless network card - although Microsoft claimed that I needed to clean install Win 10. After finding the convoluted method of safe booting Win 10 on a machine that won't boot, I disabled the wireless adapter and all of a sudden everything was fine.

Windows 10 is turning into a multi-trillion dollar joke.

Conversely I’ve not personally had any trouble with Windows 10. Of course I don’t have exposure to as many systems as I once did. I switched from network admin/support to development. Systems is someone else’s problem now and have never been happier.

[tmiranda]

For "everyday" web browsing I use a Chromebook and for anything else I use Ubuntu. I use Windows 10 occasionally but never really miss it. Ubuntu has come a long way and while the UI is still not quite as polished as Windows or Apple, it's very usable and stable.

Other than inertia, I see no reason to use Windows at home. Work is of course another issue. My workstation was recently upgraded to Win 10 due to MS dropping support for Win 7. That upgrade cost the company millions of dollars