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.
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!
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.
Even worse, Microsoft made it so very hard to hunt down all the various settings and registry flags to disable that behavior, AND it reverted to those same settings after every major update. I absolutely despised that desktop for a while.
while i understand the intention behind automatic updates, i feel it's an anti-user design. It is based on the assumption (a bad one) that the user isn't intelligent enough to do the update at a time suitable for them. It assumes that the windows design and dev team knows better. It takes control away from the user.
Rather than forcing automatic updates, it is better to teach the user why updates are important. Education beats subversion.
Then the software companies and developers, in their infinite wisdom, decided that the best approach was to force updates on the users. Because when people are already upset with your awful updating mechanisms then forcing them to do so is surely going to improve things. And now we have people crippling update functionality as a result.
Windows 10 has been a nightmare in terms of patch quality.
No, they were very responsible. They knew the updates are likely going to be UX downgrades, slow the machine down, make it bluescreen more, or possibly even brick it. That was the experience around Vista/7. That's still the experience today, maybe sans the bluescreen.
The cardinal sin of Microsoft and every other company pushing automatic updates is update commingling. Mixing up security patches (which users need and might even want) with generic bug fixes (which users need and like) with feature updates (which users don't need, and rightfully don't like). As long as all of those are mixed, updating is a risky job, and many users will responsibly decide not to do it.
A large number of users were not patching because they believe they didn't need to, and they weren't educated well enough.
Raising the competency of the users is part of the responsibility.
Having neutered Windows update my PC actually feels like a PC again.
However the combination of 15 hrs battery life + closing the lid and it not melting a hole in my bag trumps any negatives.
If I told it to update, I didn't mean "oh pretty please but if it's too hard don't worry about it", I meant "I know this ii. update is going to take an hour for a point release for some reason, but I'm going for a walk now - go ahead so IT gets off my back".
Also I've had many issues with my macbook overheating/discharging in my bag because I hit sleep, it looked like it was sleeping, but it was still on/woke up. Admittedly not a huge amount because of COVID but still.
1. Press Cmd+Option+Escape to bring up the Force Quit menu
2. Press Cmd+A to select all running apps
3. Click the "Force Quit" Button to force quit all apps
Apps that let you risk losing work -- from not just shutdowns but crashes and power outages - are the ones I don't tolerate. It's one of the reason I use Sublime Text for taking notes for example.
I can guarantee you that a Mac will still shut down when its battery is empty. Unfortunately Apple hasn't yet cracked unlimited power.
> I can guarantee you that a Mac will still shut down when its battery is empty.
Macs "safe sleep" --- when they sleep, they save a hibernation/ram state too. So if the battery is depleted, they still do not shut down.
I'm probably going back to MacOS after my current Windows 10 machine, because too many annoyances have shown up (and now ESC keys exist again).
I use mac and windows daily, and they both have similar amounts of annoying niggling features.
I was using an iPad Pro and I thought something in the Apple Notes app was good. Poof. Never found the file after.
Or I'd find it nearly dead and burning hot, fans spun up wildly, in the process of cooking it's own motherboard.
It heat suicided itself through 2 motherboards during the 1 year warranty.
I have my complaints about MacBooks, but at least I had a laptop I could count on being reliable and ready to work when I showed up to class every day.
I couldn't trust the Dell, making it absolutely worthless.
Sometimes it seems Apple is just minimalist for the sake of it. Because this is really a useful feature.
But I do very much like them, and would happily pay a bit to get it back.
And a hole with a plastic insert would be fine for me too. It wouldn't be as minimalist but not doing it at all is much worse IMO.
So kinda yes... but also kinda no, I don't think that really supports a claim that it's cheap enough to do everywhere.
But yeah, I'd totally be fine with an LED glued into a hole. The indicator is the important part, and it's a shame that it's gone.
I do have my MacBooks cooking themselves in my backpack every so often too.
Basically, every MacBook's I had in the past > 10 years ended with that issue.
Why the frak doesn’t the laptop have an over temp shutdown feature? iPhones so, trying leaving one in the sun for a bit.
I guess it's a bug or some monitoring service that crashed.
Of course iOS wasn't as stable as it is now.. I don't think this will still happen.
s2idle is broken and I have an AMD thinkpad with deep sleep and even that doesn't suspend 80% of the time.
Intel (search for 'deep' and 's2idle')
I already know the replies I might get but just wanted to get this out there. My laptop is now on 24x7 because I don't know if it will suspend or completely freeze.
What is this "known good hardware"?
I was thinking of somehow getting my hands on the FrameWork laptop since everyone and their mother keep singing praises about it but going through its forums makes it clear that it also doesn't do suspend and resume reliably.
I've already seen plenty of people reporting that their AMD laptops don't do suspend resume and break with every new kernel release. I assumed Intel would be better but reading about the same issue on FrameWork forums isn't encouraging at all.
Any hardware that ships with Linux, for a start. For another, anything whose quirks are documented on a popular community site (e.g., the Arch Linux Wiki).
It's important to choose a distro release a little bit newer than the hardware.
The Framework is brand new and doesn't ship with Linux, so I wouldn't expect it to be a trouble-free experience.
But, I'm a bit cheap, and I treat optimizing older tech as a challenge, so I think I've just declared myself both an outlier in general and a stereotypical Linux user.
I have no idea if the situation is just as bad on Intel.
The experience out of the box is still crap because the ACPI signals from the hardware are often a complete mess - but disabling most of them generally works.
Please tell me the name of a laptop which has excellent support for Linux. At this point, I'm ready to go out of my way to spend more money than I can afford if that gets me excellent Linux compatibility.
I know, for a fact, that AMD based ThinkPads don't qualify. The Intel based FrameWork laptop has issues with suspend resume as well.
Now I just disable it completely and tell it to shut down when I close the lid, and wait like 15s. If the fans and lights don't stop "soon", I know it's having problems turning off. It's much better than the random freezes, or boiling alive in a backpack before draining all battery power.
Adding `mem_sleep_default=deep` to your kernel cmdline should fix it. Been doing this on my XPS13 for 3 years now and it's fine.
dmesg | grep ACPI | grep supports
[ 0.193967] ACPI: (supports S0 S4 S5)
sudo cat /sys/power/mem_sleep
What is bad, because if there were one platform that would avoid this problem it would be Macs. But anyway, my phone does that once in a while too... Phones also shouldn't do it.
It's not even a hard problem to solve. There is a single piece of code that wakes a device up, you just have to not call it everywhere. If you don't control all the code, just require some kind of permission, and don't go granting it to the team that writes the system updater.
I've now had three generations of XPS 13 with Ubuntu. They're not perfect (the battery drains over 3 or 4 days instead of overnight) but overall my experience has been much better.
It’s more serious than laptops committing suicide in bags. It’s, anything with a high-energy battery can short itself and cause a fire. Worse, it could be malware or hardware. At this point I am surprised the vulnerability hasn’t been used by anyone.
The law is that you can only bring aboard Li-ion batteries of size 100 watt-hrs or smaller on any airplane (https://www.tsa.gov/travel/security-screening/whatcanibring/...).
I think the airline crews are confident they can handle 100 watt-hours worth of burning, but no more than that!
I'm not sure if they are smothering the fire. The strategy seems like it's just a safe place to keep the fire until later.
You won't have buckets and buckets of water on an airplane. You need a solution to safely contain the fire and keep the passengers safe.
Not the most comfortable, as you have to manage sleep manually, but definitely the safest.
Turns out I kept bumping the Bluetooth mouse which kept waking it up, and it would stay awake for a while, even with the screen closed. Disabling the permission for Bluetooth devices to wake it fixed it, but I had a couple of Mondays where I couldn't do anything for a half hour while the machine charged up enough to boot.
That's a bummer when you want to go clean your keyboard and don't want the laptop running at the same time.
I've been using Linux for the last 15 years. Had my fair share of issues with suspend. But at least once a laptop was in a state, it tended to stay there. Whether it would resume was another story :P
Ha! While not related to the bag issue, I had a 15" MBP literally catch fire in my bed while I was asleep.
I fell asleep wat hing Netflix or some such and the macbook caught fire and woke me up.
It was in the recall batch for batteries at that time.
I took it to apple flagship SF store.
They had the FN machine for two months then came back and said that at some point the moisture sensor went off and due to this reason they would not honor the battery recall or address the fact it caught on fire and the "apologized" for the potential "safety hazaard"
They told me my option was to buy a new one, or take it to a 3ed party repair place and have it repaired for more than the machine was worth.
I haven't bought another mac since, and I have switched from iPhones entirely, even though I have had an iPhone since day one.
In my opinion, the only reason why Windows is so prevalent in the "enterprise" world is because Microsoft provides support contracts to make it easier to adopt. Problems with your windows laptop? Send it off to Microsoft or open a business priority ticket to have them work on it for you. No need to hire an internal IT team.
Almost all Steam games work flawlessly out of the box now thanks to extensive investment in Proton.
That is why the Valve is confident shipping the steam deck with Linux.
For programming, by all means use Linux instead of Windows, it's better. For anything else, it's still not there yet.
I do have minor issues when scaling my 4K screen to a lower resolution, and starting a fullscreen game, but that’s about it.
I'm not sure if newer tech has better viewing angles than my old (but not that old) IPS LCD, but having having greater color depth to represent color fades with finer progression, and having more pixels to spread the fade across (hidpi), does sound like a nice step forward to me.
~"1.07 billion colors" though? Ehhh, I can't deny that does feel like overkill, but I'm honestly not even sure if there's a way to fix the above problem with a smaller colorspace.
Given that we're starting with 24 bits / 16.7 million, we're just up 6 bits more.. or 2 more bits per color... so a purely red gradient would have 4x as many steps.
And we're using some of that space to get "whiter than white" -- so that the brightest white in photos/videos can be brighter than the normal value of white.
It's ok. Not as snazzy as MacOS. But security/privacy concerns excluded, feels less headachey than Linux (which I'm also using in parallel, since Slackware 7).
I know business premium support is a selling point (ironic because it actually costs money on its own) which is good for the CYA of top management. Someone to blame when stuff goes wrong. But it doesn't really solve issues on the floor and Microsoft isn't alone in that.
That plus a whole host of annoying software bugs with the detachable design, keyboard backlight not working until I reboot, etc. was just a horrible experience so ended up getting a refund and buying a MacBook Pro when the 2018 models came out. Sure it has the crappy butterfly keyboard but three years later and that MacBook Pro is still a fantastic machine that I haven't had a single issue with. Cost the same as the Surface Book 2 as well.
The new Surface Laptop Studio looks interesting but I am very hesitant to buy Microsoft hardware again. It looks nice but is plagued with issues even today from what friends and colleagues tell me. Real shame. Hopefully things are better with the new models announced this week but I will be sitting back and waiting a few months to see how they are in the real world rather than a 3 day review.
It appears you can instruct it to avoid connecting to the internet to do stuff while in standby. I hope this works since my Surface Book has bad standby drain after sitting on my desk for 2-3 days off charge.
> powercfg /setdcvalueindex scheme_current sub_none F15576E8-98B7-4186-B944-EAFA664402D9 0
> powercfg /setacvalueindex scheme_current sub_none F15576E8-98B7-4186-B944-EAFA664402D9 0
That reminds me of last time I upgraded my mac by doing the transfer from one machine to the other. When the new mac booted for the first time, it had the same unsaved documents I had open on the old one. Things have come a long way.
I'm in awe at how much contempt some guy at Microsoft must have for users and their use-cases to conceive of a feature like that. One imagines Microsoft thinks of all of their users as yokels doing nothing more important than playing Solitaire all day.
It solidified in my mind the impression that Windows is not meant to be run on any machine you consider more important than a toy.
However, as a security professional, I think the general population doesn't understand just how critical it is to stay up to date with software updates. Sometimes we have to force them!
It's my computer, you see. It's not yours. You're welcome to buy your own, of course. But this one is mine. That's why they call it a "Personal Computer."
The rest of us aren't going to let you turn the Internet into the modern equivalent of a closed IBM shop, at least not without opposition. There's a history here, one you might be too young to have experienced personally. It's been well-documented, though. Steven Levy's Hackers is a great place to start, highly recommended.
But forcibly shutting down a machine in the middle of the day during active usage is a cardinal sin, just about the most fundamental user-hostile activity I can imagine. Microsoft may be right, and there may be a portion of the general population whose computer usage is 100% pointless nonsense that can be interrupted as easily as you'd interrupt your child's videogame to make him do homework. But I'm not in that group, and I doubt anybody here would consider everything they do on their computer to fall into that bucket.
Computers touch _everything_. I'm not an NSA agent or a hacker on a heist team, and I can think of a dozen (non-work) times in the last month where a shutdown-interruption of the work I was doing would have been a big problem.
Which brings me to my tldr: I'm not suggesting that Windows' decision is a generally bad one. I'm saying that it's a poor fit for anyone who considers their computer to be anything but a useless toy.
Neither is getting awakened at 4am by plinks from the OS intending to alert you to the installation of updates. If you're going to have so little respect for the user then just install them w/o making any noise.
I then got an iPad via a ridiculously good deal from Comcast (128 GB 6th generation (which was the latest generation at the time) for $120. The iPad took over most browsing, reading, and scratchpad duties, with the SP4 just getting occasional use when I needed something more general than the iPad.
What I noticed when the SP4 went from daily use to weekly or so is that the battery would always be low when I went to use it. Charge it up fully and shut it down...and a week later it needs charging again.
I believe that is because shut down is really some kind of sleep or hibernate. I've tried disabling all of those, and fast start. I've tried shutting down from the start menu, with and without the modifiers that are supposed to make it really shut down. I've tried command line commands that are supposed to really shut it down. I've tried shutting down from the BIOS.
But no matter what I do it consumes significant power while off. If I leave it on the charger so that it will be ready when I need it, it seems to charge to full, then stop charging until the battery drains a bit, and then repeats that cycles.
The result is after a couple years of sporadic use, the battery was degraded enough that now just using it for light browsing I'm lucky if I get 30 minutes of battery time. So now it is pretty much relegated to only being usable when hooked to external power.
I'm never buying another Surface product. And I'm not buying any Windows laptops or tablets unless there is some reasonable way to definitely turn them all the way off and have them stay that way.
I never figured out what caused it, maybe it was something in the firmware. Or something bumping the power button? However it was in a padded laptop compartment on its own.This was actually from full-off. Not even standby.
What didn't help was that I used LUKS full disk encryption so it would be sitting there waiting for a password and there was no sleep timeout.
In the end I found the SP3 was just not great for Linux, I had so many hardware issues. Sometimes I'd detach the keyboard and reattach, and it'd just not work. Or the pen would stop working or the rotation etc. Mind you this is around the time it came out. So a good while ago.
LTSC version does everything regular versions do exactl wrt automatic updates and wakeups.
Only difference is you can disable these with group policy in enterprise versions (which ltsc is)
Some interesting observations:
1. fan spins crazily for no reason randomly, and the laptop seemed to be always heated (in comparison with MBP and other laptops running Linux).
2. it can become overly hot and fan can spin even if it was in sleep! This was scary so after seeing it once I tend to power if off whenever finishing using it. Some times it didn't wake up, giving a QR code (BSOD...)
3. the not-too-bad specs failed to pump out expected performance (so sluggish), in comparison with similar hardware running Linux x86_64 or macOS (not surprised)
I personally turned them on intentionally, as I mostly use my PC as a music/fine server these days; I configured most of my applications (bubbleupnp, nginx, airsonic, everything, etc) to start up either as system services on boot; the rest (WSL, fb2k, calibre) start up on login via schtasks, so if my they aren't working remotely I can just login via TeamViewer to log into my profile. Without this setup, my computer would _never_ get updates, as I don't sit down at it much anymore.
Basically if I know I won't be using my laptop for a bit and am putting it in a bag I always make sure to turn it off now.
Though I don't share the confidence half this thread has that my experiences are universal, so I'm curious what you're referring to that I've managed to avoid.
The Dell with Linux out of the box had cooling issues and a high-pitched fan. Sure the cores would be disabled to deal with the power issues, which supports your point.
This whole post is actually pretty confusing to me. I don't use Windows that frequently myself, but my work laptop, my wife's laptop, my child's laptop, and my Surface Pro 1 all have Windows 10 on them, and this sort of thing has never happened to me. But I do my updates in a timely manner, shut down my PCs regularly, and only use sleep for temporary moments when I'm away from my PC.
I just feel like a lot of the problems people have with Windows 10 aren't really in the software, but are between the keyboard and chair.
In my case, it was mostly executables that I'm in the process of debugging and stepping through. I'm not aware of any debugger which can save and restore open file handles.
> I just feel like a lot of the problems people have with Windows 10 aren't really in the software, but are between the keyboard and chair.
I would have argued just like you before I encountered the cursed tablet. That thing had an integrated battery, so no matter what you tried, it could still turn on by itself if it wanted to. The only reliable way to make it stop making noises in the middle of the night was to thoroughly drain its battery.
That said, the Dell XPS support post that I commented on is by itself pretty detailed about all the issues that Dell machines are having with Windows 10. I think you'll believe me that Dell wouldn't publicly post that unless they had a lot of support requests related to it. So it's apparently a widespread issue.
In my case, virtual-machines. When Windows 10 decided it had to reboot, it would kill them dead. You can't quicksave those, and even if you did they have a higher-than-normal chance of not coming back up cleanly.
In any case, Win10 did not signal VirtualBox to save state -- or else didn't give it enough time -- so I would occasionally come back to my office to find everything I was working on gone due to some mystery-reboot that I didn't recall scheduling.
Because it's extremely convenient and I don't remember ever losing anything on my Mac. I close the lid in the evening, open it the next morning and everything is there exactly like I left it. MariaDB is still running, my IDE is still running, and I can jump right in. Day after day after day, my uptime is usually the number of days since the last macOS update.
My workflow involves closing up the laptop, carrying it elsewhere (while it sleeps - it has to survive being in a bag so not heating up), reopening with all the exact state it had, potentially many times each day. Then at the end of computer-day closing it (to sleep mode), and starting the next morning exactly where I left off - not from a clean after-shutdown state. Even for an unavoidable reboot (e.g. install of OS version update) I'd expect most of that state to be restored e.g. OS X and compatible apps restoring most the open apps and documents as they were - sadly it doesn't work as well as it should, so sleep is strongly preferable to anything involving a reboot.
A full shutdown is an extraordinary event that's done when placing an unused system in long-term storage or when giving it to someone else, because all other daily usage (and short breaks e.g. weekends, not just "temporary moments when I'm away from my PC.") is better suited by a sleep/hibernate mode, at least if that works properly.
TL;DR - a need to shutdown regularly is a fundamental design flaw, not a problem between keyboard and chair.
Close my work laptop, take it to the office, open it up - it's hot to the touch, stuck on the Dell high temperature warning screen, and needs to cool down and reboot.
Of course it would be crazy for me to keep repeating this scenario (I tried changing the hibernation settings, and now just shut it down) - but we can wish for it to be better, especially since it's obviously possible.
Because on other computers it just works. And if the computer stops it will re-open your unsaved documents.