this post was submitted on 22 Sep 2025
381 points (95.5% liked)
memes
17482 readers
2152 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I thought the "addressed to it" part was implied. you seem to keep saying that windows handles things. The computer is shut down, not in sleep mode. There is no windows to handle things. Windows is not loaded. It has not gone through the boot process. WoL still works if you rip out all the storage. WoL is handled by the network adapter hardware
You're describing what windows does after a computer is woken/turned on. That's irrelevant, by that point the WoL is long over. After the pc is turned on and booted then windows is free to do whatever, including putting the system back to sleep. Whether it does this fast enough for you to notice is irrelevant, that is not WoL functionality.
And no, systems are not constantly waking up and then re-sleeping. Again, if the pc was shut down it'd have to go through the whole boot process before windows can put the system back to sleep. And you would find a sleeping pc when you left a shutdown one. Not what happens. And if instead of sleeping it shut itself down that'd look like a boot loop. definitely noticable.
tldr: after the pc is turned on and the os has been loaded, the os is free to do anything
We're in a thread that was started by someone complaining that their Windows machine kept waking up seemingly on its own when they put it to sleep, so how wake on LAN behaves for a computer that's completely shut down was never particularly relevant, and certainly not something to be taken as the only situation we're discussing. When a computer is asleep, wake on LAN can wake it, and because the OS is still loaded, it doesn't need to do a full boot before running any wake on LAN handling it has. If wake on LAN is disabled in the motherboard settings, then a computer in a deep sleep like S3 can't respond to network activity at all.
Also, I'm not sure where you've got the idea that wake on LAN is mainly for fully powered off machines. There's a reason it's usually called wake on LAN, not power on by LAN. The ability for a network event to power on a machine from S5 power off is usually a separate setting and isn't even possible on all hardware that supports wake on LAN.
I'm also not sure where you got the idea that only the hardware aspect counts as wake on LAN and the OS-side handling for being woken on LAN doesn't count. Like with many things related to computers, it requires a hardware aspect and a software aspect working together to form a whole system, and in this case, it's the whole system that's called wake on LAN.