Has anyone noticed that computer will not sleep since installation of .662?
I just updated to .662 last night and my PC slept as usual without issue.
That said, have you checked for any new drivers - particularly GPU or soundcard drivers? Most of the time it's drivers that prevent a PC from sleeping.
Has anyone noticed that computer will not sleep since installation of .662? never had that problem before on this my main computer but now, it will not go to sleep. When I put it to sleep, it sleeps for a while but then wakes back up!!!! Shades of Windows 8.1.
Check to see if any of your devices got changed to allow to wake up the computer, under the properties Power Management tab.
Check to see if any of your devices got changed to allow to wake up the computer, under the properties Power Management tab.
What "devices" should the OP be looking for? And where?
Anyway, that shouldn't need to be done and I've never had it happen to me in any builds I've done. In fact, I don't even mess with the power management settings for any of my devices.
What "devices" should the OP be looking for? And where?
Anyway, that shouldn't need to be done and I've never had it happen to me in any builds I've done. In fact, I don't even mess with the power management settings for any of my devices.
It's happened to me several times after an update. In the Device Manager check Human Interface, Keyboards, Mice and Network Adapters. Doesn't hurt to look, and could solve the problem.
What "devices" should the OP be looking for? And where?
Anyway, that shouldn't need to be done and I've never had it happen to me in any builds I've done. In fact, I don't even mess with the power management settings for any of my devices.
DJG said:
It's happened to me several times after an update. In the Device Manager check Human Interface, Keyboards, Mice and Network Adapters. Doesn't hurt to look, and could solve the problem.
Shouldn't be done? To check the settings?
Happened to me only once. It was network adapter. but it was like a year ago, when MS messed with local networking things.. Had to disable " allow this device to wake computer"
Computer Type: PC/Desktop System Manufacturer/Model Number: home built OS: Windows 10 (Pro and Insider Pro) CPU: Intel i3-10100 Motherboard: ASUS Prime B460M Memory: 16 GB, Crucial Graphics Card: Intel on chip Sound Card: Realtek onboard Monitor(s) Displays: Dual ASUS+LG Screen Resolution: 1920 x 1080 x 2 Keyboard: Cherry, same for the last 20 years Mouse: Logitech M500 PSU: No name, 80 plus, 500 W Case: Mini Tower Cooling: Silent Hard Drives: Kingston A2000 NVMe, 500 GB Internet Speed: 100/20 Browser: FF, Edge, Vivaldi Antivirus: WD + MBAE, SpywareBlaster, hosts file Other Info: Eaton UPS
ASUS Vivobook Flip 14, Ryzen 7 4700U, 512 SSD NVMe, 8 GB DDr4
Computer Type: PC/Desktop System Manufacturer/Model Number: home built / frankenstein Junior OS: Windows Insider, Fast ring CPU: AMD FX6300 Motherboard: gigabyte 970A UD3 Memory: 8 GB Corsair DDR3 Graphics Card: nvidia GT710 Sound Card: Realtek on board Monitor(s) Displays: same as 1st Screen Resolution: 1680 x 1050 Keyboard: Cherry Mouse: Logitech PSU: Tecnoware 520W Case: Ugly one Cooling: 2 x 120 mm Hard Drives: Crucial BX100 240 GB, I TB spinner Seagate Internet Speed: 100/20 Browser: FF, Edge, Vivaldi Antivirus: Windows Defender, Protected folders on, PUA on
It's happened to me several times after an update. In the Device Manager check Human Interface, Keyboards, Mice and Network Adapters. Doesn't hurt to look, and could solve the problem.
Shouldn't be done? To check the settings?
I stand by my statement, but you are correct... it doesn't hurt to check.
And if you're going to tell someone to check something it helps to tell them where to look. Thanks for confirming.
I stand by my statement, but you are correct... it doesn't hurt to check.
And if you're going to tell someone to check something it helps to tell them where to look. Thanks for confirming.
Computer Type: PC/Desktop System Manufacturer/Model Number: Self Built OS: Windows 10 PRO 64Bit CPU: Intel 4770k Motherboard: Asus Maximus Hero VI Memory: 16Gb Graphics Card: Asus GTX 660 Ti Monitor(s) Displays: Asus Screen Resolution: 1920x1200 Keyboard: Logitech G19 Mouse: Logitech G700s PSU: Corsair 860i Case: Cooler Master Haf-x Cooling: Corsair H100i Hard Drives: Samsung 850 PRO 512Gb
Western Digital 1TB * 2
Mushkin Chronos SSD 200GB Internet Speed: 1Gbps Browser: IE Antivirus: Defender
Computer Type: PC/Desktop System Manufacturer/Model Number: home built OS: Windows 10 (Pro and Insider Pro) CPU: Intel i3-10100 Motherboard: ASUS Prime B460M Memory: 16 GB, Crucial Graphics Card: Intel on chip Sound Card: Realtek onboard Monitor(s) Displays: Dual ASUS+LG Screen Resolution: 1920 x 1080 x 2 Keyboard: Cherry, same for the last 20 years Mouse: Logitech M500 PSU: No name, 80 plus, 500 W Case: Mini Tower Cooling: Silent Hard Drives: Kingston A2000 NVMe, 500 GB Internet Speed: 100/20 Browser: FF, Edge, Vivaldi Antivirus: WD + MBAE, SpywareBlaster, hosts file Other Info: Eaton UPS
ASUS Vivobook Flip 14, Ryzen 7 4700U, 512 SSD NVMe, 8 GB DDr4
Computer Type: PC/Desktop System Manufacturer/Model Number: home built / frankenstein Junior OS: Windows Insider, Fast ring CPU: AMD FX6300 Motherboard: gigabyte 970A UD3 Memory: 8 GB Corsair DDR3 Graphics Card: nvidia GT710 Sound Card: Realtek on board Monitor(s) Displays: same as 1st Screen Resolution: 1680 x 1050 Keyboard: Cherry Mouse: Logitech PSU: Tecnoware 520W Case: Ugly one Cooling: 2 x 120 mm Hard Drives: Crucial BX100 240 GB, I TB spinner Seagate Internet Speed: 100/20 Browser: FF, Edge, Vivaldi Antivirus: Windows Defender, Protected folders on, PUA on
UPDATE 2/24: KB4601382 CU Windows 10 v2004 build 19041.844 and v20H2 19042.844
The KB4562830 Enablement Package allows you to go from build 19041 (v2004) to 19042 (v20H2).
Source:...
UPDATE 3/9: KB5000802 CU Windows 10 v2004 build 19041.867 and v20H2 19042.867
The KB4562830 Enablement Package allows you to go from build 19041 (v2004) to 19042 (v20H2).
Source:...
If you already updated to 661 or 662, then you will not need to manually download and install 631 since 661 and 662 is a higher build. No need to do anything.
Source: https://support.microsoft.com/en-us/help/4594440
See also:...
UPDATE 2/9: KB4601319 CU Windows 10 v2004 build 19041.804 and v20H2 19042.804
Source: https://support.microsoft.com/en-us/topic/february-2-2021-kb4598291-os-builds-19041-789-and-19042-789-preview-6a766199-a4f1-616e-1f5c-58bdc3ca5e3b
...
UPDATE 1/12: KB4598242 CU Windows 10 v2004 build 19041.746 and v20H2 19042.746
The KB4562830 Enablement Package allows you to go from build 19041 (v2004) to 19042 (v20H2).
Source:...