Personal computing discussed
Moderators: renee, Flying Fox, Ryu Connor
Krogoth wrote:I suspect that it might be a similar case for you.
Glorious wrote:powercfg -devicequery wake_armed only lists the ethernet adapters (which is intended, and have been eliminated as the cause)
Glorious wrote:The problem exists with the vendor application installed, and not without it.
Glorious wrote:*Inserts verbose way of saying "I have already looked at that" while acting like a smart-a$$*
Krogoth wrote:That approach is a great way to attract helpful feedback.
The Egg wrote:I take it you've gone into Power Options (standard Control Panel) and pored over the "Advanced Settings"? Unfortunately I don't have a W10 machine accessible at the moment to go more in-depth.
Same for me - two machines suddenly waking from sleep and I can see from powercfg -waketimers that it is teamviewer that has created an entry that is causing it.
Unfortunately the disable waketimers option in the control panel for Windows 10 seems to make no difference - they were already disabled and yet the PC still wakes from sleep.
Spotify seems to be setting up wake timers on my system that prevent Windows from reliably staying in sleep/hibernate mode. Even when wake timers are turned off in system settings.
Glorious wrote:*Another verbose response that can be easily be sum-up with "RTFP, DUMBA$$!" colored with a massive condescending tone while pretending to be witty and clever*
Krogoth wrote:In any case, I would recommend focusing your energies towards Microsoft and software vendors in question for a possible solution.
Glorious wrote:The solution in those cases involved the respective companies releasing updates that just didn't use waketimers. But as I said in the OP, it could be months->never until that happens in my case.
just brew it! wrote:Krogoth wrote:In any case, I would recommend focusing your energies towards Microsoft and software vendors in question for a possible solution.Glorious wrote:The solution in those cases involved the respective companies releasing updates that just didn't use waketimers. But as I said in the OP, it could be months->never until that happens in my case.
@Krogoth - Are you even reading his posts before hitting Reply?
morphine:Glorious, I recently troubleshooted an issue like that. It was before the Anniversary Update, though.
What fixed it for me was scouring through every connected USB device and making sure that other than the keyboard and mouse, none could wake the PC. Heck, disable them for testing if need be. I eventually narrowed the problem down to a gamepad.
Get-ScheduledTask | where {$_.settings.waketorun}
Krogoth wrote:In any case, I would recommend focusing your energies towards Microsoft and software vendors in question for a possible solution. I doubt you will find viable answers in the "Computer enthusiast" portals if simple web searching does not yield any solutions.
Glorious wrote:So, maybe I ought to be asking how I might report or file a bug with Windows 10?
Glorious wrote:The vendor shouldn't be this retarded, I agree, but the timeline for them fixing it in this case is months to possibly never.
Glorious wrote:But as I said in the OP, it could be months->never until that happens in my case.
morphine wrote:Glorious, I recently troubleshooted an issue like that. It was before the Anniversary Update, though.
What fixed it for me was scouring through every connected USB device and making sure that other than the keyboard and mouse, none could wake the PC. Heck, disable them for testing if need be. I eventually narrowed the problem down to a gamepad. Amusingly enough, the same gamepad never produced this problem a problem with Win7.
morphine wrote:Glorious, I recently troubleshooted an issue like that. It was before the Anniversary Update, though.
What fixed it for me was scouring through every connected USB device and making sure that other than the keyboard and mouse, none could wake the PC. Heck, disable them for testing if need be. I eventually narrowed the problem down to a gamepad. Amusingly enough, the same gamepad never produced this problem a problem with Win7.
Convert wrote:I've not had to deal with this issue, but is the application creating the wake timers through a scheduled task? I came across this while researching, they said that running:
Glorious wrote:Does anyone have any idea why the setting in power profiles (I set it to disable in all of them) doesn't actually disable the ability of waketimers to wake a windows 10 computer from sleep?
I don't mean the microsoft update one, I can live with that. I mean vendor applications that set an infinity of waketimers for unknown reasons and thus the computer can't sleep for more than a minute at a time.
liquidsquid wrote:Interestingly I had similar issues on my home boxen, and gave up and left the machine to run 24/7. Even more annoying is the monitor wont sleep, and I have to manually power it off. This monitor problem one is due to older than dirt weather software that inexplicably will wiggle the mouse cursor every so often to keep the machine awake. It must have been an old Windows 95 trick to prevent the machine from shutting down, and it has never been removed for recent OSes. Really naughty IMO.
liquidsquid wrote:And Microsoft wonders why its OS is not getting adopted in the embedded space... let alone phones. Critical low-level functions like power modes should be the first thing to work, not search engines, should be tight and functional.
liquidsquid wrote:And Microsoft wonders why its OS is not getting adopted in the embedded space... let alone phones. Critical low-level functions like power modes should be the first thing to work, not search engines, should be tight and functional.
The Egg wrote:I think the most likely culprits are a USB device, an asinine piece of software, or a poorly written driver; in that order. The first one should be fairly easy to eliminate (just unplug everything sans the keyboard and put it to sleep).