WEBVTT 00:00:00.000 --> 00:00:08.220 look at what you've done to a Microsoft this lifelong Windows user has been 00:00:05.580 --> 00:00:11.940 forced to switch to a MacBook why well because he's got real work to 00:00:10.679 --> 00:00:17.220 do and he needs something he can actually rely on and it's your fault 00:00:14.340 --> 00:00:22.199 this is no exaggeration this is real you guys it's happening and all because you 00:00:20.279 --> 00:00:27.779 can't fix a feature that most people probably couldn't even name modern 00:00:24.960 --> 00:00:31.920 standby that's right guys after complaining about it in every single 00:00:29.699 --> 00:00:36.480 laptop video for the last year we're finally doing a deeper dive into what we 00:00:34.140 --> 00:00:40.860 consider to be the biggest problem with Windows laptops in fact it's something 00:00:39.000 --> 00:00:45.000 that I'm sure that you have first-hand experience with you know that thing 00:00:43.020 --> 00:00:48.840 where you fully charge your laptop then you take it out of your bag the next day 00:00:46.440 --> 00:00:53.100 to find it dead and as a bonus probably hot enough to burn you well it took some 00:00:51.660 --> 00:00:56.820 time and there were definitely challenges including discovering that 00:00:55.079 --> 00:01:01.379 Max can actually suffer from the exact same problem but we think we've cracked 00:00:59.160 --> 00:01:06.479 it we figured out what Microsoft hasn't been able to in the last three years and 00:01:04.140 --> 00:01:10.320 we might even have the solution just like we have the solution to 00:01:08.280 --> 00:01:13.500 perfectly segue to our sponsor build Redux takes the challenge and hassle out 00:01:12.240 --> 00:01:17.100 of building your own PC with configuration options support guides to 00:01:15.420 --> 00:01:21.060 Aid you and competitive pricing versus building a PC yourself why not kick up 00:01:19.140 --> 00:01:25.680 your feet and let build Redux handle it for you so head to build redux.com Linus 00:01:23.759 --> 00:01:31.020 and start your new build today for a long time I gaslit myself into thinking 00:01:27.600 --> 00:01:32.580 my it might just me and then I moved on 00:01:31.020 --> 00:01:36.659 to thinking ah my this laptop like ah this piece of junk 00:01:34.920 --> 00:01:40.799 never has battery when I need it but then we started to notice this pattern 00:01:38.159 --> 00:01:45.659 but no matter the brand Dell HP Lenovo Microsoft lga's races you get the point 00:01:42.900 --> 00:01:53.460 it's bound to show up once in a while on pretty much every Mobile Windows machine 00:01:48.900 --> 00:01:55.560 and no it isn't just us we asked on 00:01:53.460 --> 00:02:01.079 Twitter if anyone had experienced the same problem and we received thousands 00:01:58.320 --> 00:02:04.560 of replies full of tales of hot dead laptops that should have been asleep and 00:02:03.360 --> 00:02:08.160 fully charged what makes this problem challenging to 00:02:06.420 --> 00:02:13.200 diagnose though is that there's no obvious pattern to it one day it's fine 00:02:10.739 --> 00:02:16.860 the next day it's not and even when the battery is draining it can take hours 00:02:15.180 --> 00:02:22.319 for the loss to be noticeable which makes testing take forever 00:02:19.379 --> 00:02:26.160 we don't know exactly what causes this rapid battery drain but we did observe 00:02:24.300 --> 00:02:31.260 that the problem is more pronounced on powerful machines which seems to suggest 00:02:28.800 --> 00:02:34.680 that whatever the background task is we think it could be related to Windows 00:02:32.520 --> 00:02:42.420 update it relies fairly heavily on your CPU so bigger CPU bigger drain but wait 00:02:39.300 --> 00:02:43.980 this laptop is asleep why is it running 00:02:42.420 --> 00:02:50.519 Windows updates well here's the thing in the past 00:02:46.800 --> 00:02:53.340 laptops came with S3 sleep AKA suspend 00:02:50.519 --> 00:02:58.140 to RAM when your computer is using S3 sleep the processor is essentially off 00:02:55.739 --> 00:03:01.440 but Power gets maintained to the memory so that when you open the lid there's no 00:03:00.180 --> 00:03:06.180 need to pull data off of your system drive and you can resume working 00:03:03.480 --> 00:03:10.760 basically immediately but on newer machines S3 sleep has been mostly 00:03:08.400 --> 00:03:16.140 replaced by Windows modern standby or S zero sleep s0 sleep could also be 00:03:13.920 --> 00:03:20.940 referred to as connected sleep and it's actually existed since way back in 00:03:17.879 --> 00:03:23.640 Windows 8. but for a long time it was 00:03:20.940 --> 00:03:28.620 not the default and even if you were using it it was very easy to disable so 00:03:26.640 --> 00:03:34.260 why is it suddenly an existential problem for Windows machines 00:03:30.840 --> 00:03:36.480 Intel in 2020 Intel introduced project 00:03:34.260 --> 00:03:40.739 Athena with the general goal of making laptops feel more like a smartphone and 00:03:39.300 --> 00:03:45.060 there were a couple of really good ideas that Intel pushed in Project Athena like 00:03:43.440 --> 00:03:49.379 instant wake better overall responsiveness and all-day battery life 00:03:47.819 --> 00:03:54.239 to help achieve instant wake manufacturers were pushed to use s0 00:03:51.900 --> 00:03:59.159 sleep a sleep state where the CPU remains on and connected to the network 00:03:56.340 --> 00:04:03.599 this allows laptops to perform small housekeeping items while they're asleep 00:04:01.200 --> 00:04:07.980 and it can actually be pretty great for instance apps can continue to receive 00:04:05.459 --> 00:04:12.659 messages Bluetooth audio can continue playing Windows can update while you're 00:04:10.319 --> 00:04:16.079 away from the computer like have any of you noticed that for the most part your 00:04:14.099 --> 00:04:20.040 Windows install just stays up to date without thinking about it well that's 00:04:17.760 --> 00:04:25.259 the beauty of s0 sleep the problem however is that this is in fact a laptop 00:04:22.740 --> 00:04:31.259 not a smartphone and I don't necessarily expect it to work exactly like a 00:04:27.479 --> 00:04:32.820 smartphone also x86 is very different to 00:04:31.259 --> 00:04:38.520 the ARM processors that are used in phones and apple silicon MacBooks 00:04:35.520 --> 00:04:40.440 with my phone I expect to be notified of 00:04:38.520 --> 00:04:45.479 a text message or a phone call even if the screen happens to be off and I also 00:04:43.320 --> 00:04:50.460 expect to plug it in at the end of every day with a laptop I expect to close it 00:04:48.900 --> 00:04:54.360 stuff it in my bag at the end of a Friday and then on Monday morning when I 00:04:52.680 --> 00:04:58.199 come back to work I expect to take it out and have roughly the same amount of 00:04:55.979 --> 00:05:02.040 battery left the final straw that made me go Mac was before the Intel Arc live 00:05:00.300 --> 00:05:06.660 stream it was an incredibly hectic morning running around and there's a 00:05:03.780 --> 00:05:10.500 problem that needed solving now so I take my laptop and my backpack which I 00:05:09.000 --> 00:05:14.520 made sure was charged the night before knowing I'd be very busy in the morning 00:05:12.360 --> 00:05:19.860 Not only was this thing warmer than our retro polar fleece ltstore.com but it 00:05:17.100 --> 00:05:23.460 was completely dead this meant that while I was troubleshooting problems I 00:05:21.660 --> 00:05:28.020 could not get a charger's length away from the wall making me mad enough to 00:05:25.680 --> 00:05:31.080 stop using Windows altogether ah 00:05:29.460 --> 00:05:35.639 and judging by the comments on ShortCircuit and Twitter I am far from the 00:05:33.360 --> 00:05:39.840 only one but after a couple of weeks with the Mac it 00:05:37.440 --> 00:05:44.880 happened again I took this MacBook Pro 14 inch out of my bag and it was dead 00:05:42.479 --> 00:05:49.740 turns out apple has a very similar always on feature to Modern standby but 00:05:47.400 --> 00:05:53.699 would you look at this by going to the battery settings there is a toggle for 00:05:51.479 --> 00:05:58.259 Wake for network access I'll change that to only on power adapter and have not 00:05:56.160 --> 00:06:02.460 had the problem since this Mac has been able to run and update and such while 00:06:00.120 --> 00:06:07.680 it's sleeping so long it is connected to power just as it should be if only there 00:06:05.039 --> 00:06:12.900 was a fix that easy on Windows that's the worst part of this there used to be 00:06:10.220 --> 00:06:17.639 when connected standby was originally introduced it could be toggled in the 00:06:14.820 --> 00:06:22.020 power menu then they got rid of that so you'd have to use the command platform 00:06:19.560 --> 00:06:26.639 AO AC override to revert your laptop back to the old S3 sleep mode then 00:06:24.360 --> 00:06:31.020 Microsoft nuked that work around in an update but it was still possible to go 00:06:28.860 --> 00:06:34.080 back to S3 sleep through a registry edit until they killed that in an update as 00:06:33.180 --> 00:06:39.960 well why is Microsoft actively making it so 00:06:37.740 --> 00:06:47.220 difficult to remove this clearly broken feature well because the BIOS engineers 00:06:42.780 --> 00:06:50.940 at Dell HP Lenovo and so on are lazy and 00:06:47.220 --> 00:06:54.120 didn't bother to support both s0 and S3 00:06:50.940 --> 00:06:56.639 sleep in their firmware so if you apply 00:06:54.120 --> 00:07:01.199 any of the above hacks it could actually cause your laptop to crash outright when 00:06:59.039 --> 00:07:06.360 it tries to sleep this is particularly frustrating because both Intel's 12th 00:07:03.720 --> 00:07:11.160 gen mobile processors and AMD's ryzen 7000 mobile processors still totally 00:07:08.819 --> 00:07:15.120 support S3 sleep it's just that the laptops have crappy firmware that 00:07:12.900 --> 00:07:18.720 doesn't to check if your system supports S3 sleep then if you don't want it 00:07:16.919 --> 00:07:22.979 crashing all the time go to the command line and type power config slash a which 00:07:21.539 --> 00:07:28.500 will show you what sleep states are available to your device look down here 00:07:25.259 --> 00:07:30.000 where it says standby S3 and then you 00:07:28.500 --> 00:07:34.680 just have to hope that it doesn't say the system firmware does not support 00:07:31.979 --> 00:07:39.479 this standby State since if if you see that you're probably screwed we tested 00:07:37.259 --> 00:07:43.800 this on a wide array of laptops in our office and only framework and ASUS 00:07:41.880 --> 00:07:49.020 appear to have bothered to implement S3 sleep on their latest processors but 00:07:46.680 --> 00:07:54.000 don't give up yet head to the BIOS of your laptop by spamming F1 F2 and delete 00:07:51.419 --> 00:07:58.500 while restarting and with any luck you might find a toggle for S3 sleep or 00:07:56.639 --> 00:08:02.940 something called Sleep state with options for Windows or Linux don't be 00:08:01.080 --> 00:08:07.319 put off the naming even Windows users can just swap it over to Linux and 00:08:04.919 --> 00:08:12.180 should be good to go once that's enabled you can still use the old registry edit 00:08:09.479 --> 00:08:16.080 from before to restore good old S3 sleep you can also set it so that closing the 00:08:14.580 --> 00:08:20.340 lid of your machine causes it to hibernate rather than sleep this 00:08:18.120 --> 00:08:24.720 resolves the battery drain issue most of the time but because hibernate writes 00:08:23.099 --> 00:08:31.199 the contents of system memory to non-volatile storage it's a lot slower 00:08:28.259 --> 00:08:34.800 to pull it back into RAM which kind of defeats the purpose of creating modern 00:08:32.640 --> 00:08:38.880 standby in the first place the the strangest thing about all of this is 00:08:36.899 --> 00:08:43.020 that this battery drain problem should never have been a problem in the first 00:08:40.740 --> 00:08:47.700 place when checking the available sleep states with a laptop on battery it 00:08:45.060 --> 00:08:52.380 states standby Network disconnected meaning that when your laptop goes to 00:08:49.920 --> 00:08:57.600 sleep it shouldn't try to pull any updates receive any messages and so on 00:08:54.839 --> 00:09:02.880 and so forth however if you plug the laptop in and check the power States 00:08:59.700 --> 00:09:05.760 again it says standby Network connected 00:09:02.880 --> 00:09:10.320 to allow updates and such that's when our light bulb moment happened what 00:09:08.100 --> 00:09:15.000 we're almost certain is happening is that if you are charging your laptop and 00:09:12.660 --> 00:09:19.740 you close the lid it'll go to sleep in network connected mode then if you 00:09:17.399 --> 00:09:24.120 unplug it and say Chuck it in your bag and go to work the device is not 00:09:21.959 --> 00:09:28.680 recognizing that it has since been unplugged and remains in network 00:09:26.339 --> 00:09:32.760 connected mode if there happens to be a Windows update or something then while 00:09:30.300 --> 00:09:38.880 it's in your bag congratulations your laptop is now drained so the incredibly 00:09:36.600 --> 00:09:44.459 stupid temporary fix if you don't want to do anything else that we said is to 00:09:41.580 --> 00:09:48.000 always unplug your laptop before closing the lid Maybe 00:09:46.080 --> 00:09:53.279 it's difficult to verify this 100 because we're basically trying to force 00:09:50.700 --> 00:09:59.040 a strange error that can take hours to unfold but it's the best guess we have 00:09:55.740 --> 00:10:00.779 for now which Frankly Speaking is as far 00:09:59.040 --> 00:10:06.480 as we should have to go farther than we should have had to go because Microsoft 00:10:03.180 --> 00:10:09.600 you're a multi-billion dollar company 00:10:06.480 --> 00:10:11.640 just fix it Windows modern standby has 00:10:09.600 --> 00:10:15.899 been a crippling issue for the last years and 00:10:14.160 --> 00:10:19.019 I'm gonna just lay down the line here I'm not going to be recommending a 00:10:17.399 --> 00:10:23.459 Windows laptop over a Macbook until you've either fixed it or re-enabled S3 00:10:21.120 --> 00:10:27.779 sleep what I can recommend though is this segue to our sponsor vessi do you 00:10:26.160 --> 00:10:31.920 ever struggle figuring out what to wear in unpredictable weather well vesi says 00:10:29.700 --> 00:10:35.339 their shoes are 100 waterproof keeping your feet dry in the wettest of weather 00:10:33.600 --> 00:10:38.820 they're lightweight and easy to pack sneakers offer you reassurance when the 00:10:37.260 --> 00:10:41.640 snow and rain start coming down putting them on and taking them off is super 00:10:40.260 --> 00:10:45.120 easy and their shoes are made from cruelty free products right down to the 00:10:43.500 --> 00:10:48.540 glue whether it's a rainy city or a Rocky Trail the herringbone tread design 00:10:46.920 --> 00:10:52.260 is there to help stop you from slipping around so treat your feet with vessy 00:10:50.100 --> 00:10:57.540 Footwear and save 25 with our offer code Linus Tech tipsy.com lightest Tech tips 00:10:55.740 --> 00:11:00.899 if you guys enjoyed this video you might enjoy another video about things that 00:10:59.399 --> 00:11:05.480 are broken so why don't you check out part one of the Intel Arc 30 day 00:11:03.180 --> 00:11:05.480 challenge