- May 16, 2008
- 11,418
- 2,335
- Home Country
- Germany
Guys,
I discovered a PowerScheduler problem this morning on a Win 10 Home x86 client:
I discovered a PowerScheduler problem this morning on a Win 10 Home x86 client:
- Under Windows the client is entering standby according to the energy settings.
- Under MP the client is not entering standby (if set up to be controled) by Windows
- Under MP the client is entering a deeper sleep state than S3 (if set to 'Force standby'). As a result the USB has no power anymore and therefore the client cannot be woken with the remote
- The client is entering the same deeper sleep state if sent into standby manually from the home screen.