line console, type:
powercfg-energy
test + report generated can 'be very helpful in understanding problems.
powercfg-a instead gives you a list of supported modes
powercfg -H on you activated Hibernate
powercfg -? as usual there from the list of all commands
In my case, I understood that the computer my wife never went into standby because of the service "spooler print ". Restarting the problem seemed to disappear but in reality ', soon after, riprensentava.
Here and 'took the second problem. After some investigation I discovered that there is' still an old printer registered with the outstanding job for thousands of years. We can not close the interface is the only chance 'and I' and remained 'state
powercfg-a instead gives you a list of supported modes
powercfg -H on you activated Hibernate
powercfg -? as usual there from the list of all commands
In my case, I understood that the computer my wife never went into standby because of the service "spooler print ". Restarting the problem seemed to disappear but in reality ', soon after, riprensentava.
Here and 'took the second problem. After some investigation I discovered that there is' still an old printer registered with the outstanding job for thousands of years. We can not close the interface is the only chance 'and I' and remained 'state
- stop the service "print spooler"
- delete all files in the directory c
: \\ windows \\ system32 \\ spool \\ printers
- restart the service "print spooler
powercfg-lastwake to understand the event that triggered the ignition
powercfg-devicequery wake_armed to get the details and figure out which device and 'was involved (the mouse, keyboard, network card, a timer an application, etc ...)
In most cases it is the network adapter that has caught some "package" that caused the restart to occur. Disable this option (deflaggate "allow this device to wake the computer") on the properties of the card and you will see the miracle.
- )
