And in my case, there wasn't any non-Microsoft drivers on the system. The issue appears to be that they do magical stuff when they spot a WiFi connection, or when my WiFi router does its daily reboot.
I think that might've been my issue that kept waking up my desktop. I tried disabling everything I could to stop wake ups - to make it only wake up on pressing the power button, but I never got it to work properly. The desktop would just seemingly randomly decide that it wants to wake up again. I eventually stopped trying to put computers to sleep - it's either shut down or it just stays running.
> or when my WiFi router does its daily reboot.
Damn, I think that might fix 99% of the issues I have with my WiFi router.
I DO NOT understand how all routers I have ever owned are total garbage, but they all have been.
By far, internet connectivity has never been better at my house. I've had various Netgear, D-Link, and Linksys devices. Unifi beats everything hands-down.
so far I am quite glad that I mentioned my problem here.
The community also seemed pretty elitist, I went through many forum posts about people with similar setup questions and/or problems as myself and fairly often they got simply berated when they didn't understand what a certain setting actually did or didn't understand exactly what people were having them input through a 30 item terminal command. The wiki has an example of just about everything once but even that was far from comprehensive when there are 20+ different options and you don't know what they mean and the example on the wiki picks just one of them and doesn't explain why they chose that one.
I don't regret the purchase at all, however I don't think I could feel safe in randomly recommending it to anybody except the most tech savy of my tech savy friends.
The cam is pinged every 5 mins and if it doesn't respond, Node-RED power cycles a mains switch connected to it - and sends me an email! If the camera doesn't come back, the power is cycled up to a total of 5 times before I get a final email that says I need to take a look.
Also, I buy and deploy a lot of Unifi/ER equipment and that doesn't happen. I think you've noticed there's a common factor in your final statement, though.
and what exactly could I be doing to cause random DNS failures, or to cause DHCP to fail only on Ethernet ports? these things can't be configured to do that. they're consumer-grade routers and consumer-grade routers are garbage. all of them.
every enterprise router or access point I administer at work functions just fine for years at a time.
Static devices (as opposed to DHCP reservations) will just (seemingly) randomly stop working with port forwarding, as the router just forgets the device. You can shake it out of that by pinging the device from the router's diag tools, or power cycling the router resolves the issue. Not great for CCTV DVRs/NVRs.
"Smart setup" sometimes breaks stuff, especially IoT stuff.
Your device may or may not just randomly factory reset itself. (I've had one do it twice in three years, to the point where I now save the config.)
It may or may not completely ruin your Sky Q system's reliability if you have more than one box (although I generally advocate wiring them in completely and disabling all wireless functionality anyway).
The automatic channel setting for the WiFi channels is a total dice roll.
The DNS interception rubbish breaks stuff. Most recent example was I was having infuriating issues with Ubiquiti's AP guest portal... Until I switched the BT Business Hub into a dumb modem and put a cheap ER-x in front. Rock solid since.
He was paying €15/mo for 4K television plus 1/0.6Gbit fiber internet on custom hardware they'd provided. I can't help but feel something went terribly wrong in the US for us to be happy with our $80/mo cable options and dated, generic hardware.
Hm, or you could just use a Raspberry Pi.
I use a lot of fans in my house to circulate air, and when someone uses the microwave, half of the fans slow down, and half speed up significantly. no idea how half could speed up, but they do. so, something is up with something, somewhere.
I expect this UPS to beep a lot.
good luck! hope it works, UDM pro isn't without its issues, but it's pretty dang good for what it does!
My router reboots only when the electricity is cut. So many weeks or even months between each reboot.
Wi-Fi works, Ethernet works even better, and I have some Automobilista (videogame) servers open to the world.
It is a big issue if my IP changes, so I am very aware of all these things.
Still, no reboots needed.
In fact I just tried it again on 4 computers and every one of them said "Wake History Count - 0".
also, run the command as an administrator. not just using an account that is an administrator. use an elevated cmd prompt or PowerShell window.
if you're doing all that, idk what's going on.
You can, however, see what devices are capable of waking your machine, and then disable them, by using the commands in my other comment: https://news.ycombinator.com/item?id=28647492
Also what you are referring to as an application's capability (Foobar...) to wake a computer (from sleep or hibernation only) it most probably has to do with setting an RTC (real-time clock) alarm and the computer being allowed to resume from such an event. Again this is also a setting which can be disabled in most BIOS configurations and yours probably is. By the way, Windows' task scheduler exposes this option to everyone so you can set your computer to wake up and run some script and then sleep again (I used to do this all the time ages ago for night downloads, etc.)
So, there are a series of switches (in BIOS and in windows device manager) that all have to be set/unset, for a computer to resume from some event;
# load assembly System.Windows.Forms which will be used
Add-Type -AssemblyName System.Windows.Forms
# set powerstate to suspend (sleep mode)
$PowerState = [System.Windows.Forms.PowerState]::Suspend;
# do not force putting Windows to sleep
$Force = $false;
# don't allow the computer to be woken by devices or tasks (e.g. windows updates)
$DisableWake = $true;
# do it! Set computer to sleep
[System.Windows.Forms.Application]::SetSuspendState($PowerState, $Force, $DisableWake) | Out-Null;I'm one of those people - my computer kept waking up in the middle of the night and that command would always just return "wake source: unknown" for me.
powercfg -devicequery wake_armed
powercfg -devicedisablewake "Device Name"
if you haven't tried this, try it, and I really hope it helps.
It's possible auto wakeup was enabled in the BIOS, with the wake time set to the default of 00:00.
Alternatively, if it was a different time, perhaps *that* was the default, or maybe the value accidentally got changed.
Alternatively-alternatively, maybe the BIOS had a bug in it that somehow enabled auto wake without presenting an option. To tackle this, I would've reset the BIOS settings. (I once had an ADSL2+ modem that randomly started flaking out and not connecting correctly. Changed every accessible setting I could, no dice. Factory reset = instantly back to normal.)
in your case I would scrutinize the task scheduler for tasks that are allowed to wake the PC.
That said, the tablet felt so infuriating to me that I was honestly happy when it was gone again, despite the financial loss.
My desktop used to wake itself up all the time to update and in addition to hunting down all the devices, there was a scheduled task for Office updates that I had to disable. It would wake the computer up and then Windows updates would install because the computer was awake at the scheduled time, giving me the false impression that Windows update was causing the wake.
In 8-9 years of using Surface Pros, on the other hand, I have never had one that woke from sleep to install updates or cooked itself in a bag. They have been trouble-free for me and my favorite travel computer.
Really need to look into a BSD with Windows VM for my next desktop though.
You can get all the BSD’s you want on Windows!
:D
But it's not too late to help others! Thank you for showing us how insane this is.
And easily configurable is subjective. Sure most readers here can work through it but requiring use of the CLI is not "easy" for most people. Not to mention the discoverability of that feature in the first place.
I am the user. I use the machine, not the other way around.
The fact that such a subsystem exists isn't an indication of malice or a subversion of your will. There will be bugs in such a system, but the system still needs to be there.
Because that is the usecase that hibernate is for. It makes laptops convenient by allowing you to just close the lid, put it in a bag, go somewhere, take it out of the bag, and then open it and continue working. If you need to tell people that they need to shut down their computers properly before putting them into bags, you have just produced a vastly inferior product.
This is an area where Microsoft desperately needs a Chief-making-it-not-suck-Officer. Someone who can just take that surface laptop, notice that some idiot actually wrote that you are supposed to shut it down instead of hibernating to put it in a bag, and yell at people until the product is fixed. Because right now it's broken.
Pre-covid I had many co-workers who would sit down, plug their laptop into the dock, and work the whole day without ever opening the lid.
I've also spent 15+ years with a laptop connected to my TV that never has the lid open, and I definitely expect it to wake up when I sit on the couch and wiggle the Bluetooth mouse.
And running a configuration command is in fact you telling it what to do.
So the actual issue is open-systems vs walled-gardens in system design and how it surfaces in consumer products. The only thing Windows can do is force you to review each and every device driver on install for e.g. can wake machine. A non-starter for a consumer OS.
I've never had it return with "unknown" once in over a decade, but some people I know have.
if you can find all the things waking the computer, and fix those things, it will never wake without user intervention.
usually, for me, it's been device drivers which have permission to wake the computer from sleep by default, for some stupid reason. removing that permission on those devices has eliminated "hot bag syndrome" for me entirely.
I agree that these steps should not need to be taken. device driver authors are the source of almost all bad crap like this in windows.