Windows 10: Win 10 / Microsoft Sculpt Desktop Set / wake from sleep issue

This is how my Win10 x64 Pro system wake from sleep behaves with Microsoft Sculpt

Allow keyboard to wake up PC Allow Mouse to wake up pc PC wakes with keyboard usage PC wakes with mouse usage
yes yes yes yes
yes no yes yes - should be no!
no yes yes - should be no! yes
no no no no

One driver for desktop set handles both device manager flags for keyboad and mouse. They should be handled separately.


Is there something I'm missing? If not, how can I report this for fixing?

:)

 

wake from sleep issue in windows 10

Hi,

Thank you for posting your reply. Apologize for the delay in response.

I suggest you to check which devices are configured to wake up the computer from sleep by following the steps below:

• Right click on Start icon and select Command Prompt (Admin).
• Type the command line below:

Powercfg /devicequery wake_armed

3. Check if the devices (Keyboard, Mouse, Ethernet cable) are listed.

If the system is not going to sleep and going to Hybernate, the only option to wake up is to press the Power button.

Hope the information is helpful.

 

Sculpt ergonomic desktop - Replacement

Hi,



Thank you for writing to Microsoft Community forum.

• What is the version of Windows installed?
  

I suggest you to get in touch with the Microsoft Hardware
Support to know about the replacement criteria. Meanwhile, you may also go through the
Warranty Limit Manual given under Sculpt Ergonomic Desktop.



Regards,

 

Will not wake from sleep

I have two computers. One a laptop and the other a four year old desktop. Both were upgraded from Win 7 to Win 10. The desktop is Win 10 pro. Both have the same problem, they will not wake from sleep. I have tried many of the suggestions in the Forums
and nothing has worked. The desktop was fine until two weeks ago. The desktop has no hibernation setting that I can find. My only choice at the present is to set the desktop to never sleep and do a shut down when I am not using it. If it goes to sleep
I have to reset or boot to get it back. Is MS planning on an update to correct this problem that it appears many are having?