To ensure that my REQUESTSOVERRIDE command took effect I ran: powercfg -REQUESTSOVERRIDE Unfortunately this did not fix the problem. Powercfg -REQUESTSOVERRIDE DRIVER "Legacy Kernel Caller" SYSTEM So naturally I executed REQUESTSOVERRIDE again for the related headset drivers: powercfg -REQUESTSOVERRIDE DRIVER "USB Audio Device" SYSTEM Upon plugging in my headset again, the problem came back. This did in fact allow my computer to enter sleep. powercfg -REQUESTSOVERRIDE DRIVER "Realtek High Definition Audio" SYSTEM So I then ran the following command to prevent the Realtek High Definition Audio driver from preventing sleep. The problem still persisted after unplugging the headset. If I unplugged my headset, both the USB Audio Device and the Legacy Kernel Caller entries were gone upon running powercfg -requests again. What I had noticed with my headset was confirmed by the USB Audio Device entry under system. To identify the cause of what's keeping the computer from waking I used powercfg in an elevated command prompt: powercfg -requests Set the computer sleep time to 1 minute of inactivity to see if any changes had an effect.I recently got extremely fed up with my computer waking from sleep very consistently and decided once again to try and solve the problem. I had noticed that the problem would occur whenever my headset (Hyper X Cloud II) was plugged in, but it was not exclusively occurring when plugged in. I had hoped that Windows 10 would resolve these issues, but unfortunately this is not the case. I have been having issues with my computer not entering sleep and also waking from sleep since Window 8.1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |