KVM Windows virtual machines and ACPI unattended shutdown: a recap
/ 3
Page 5 of 6
ACPI results with policy/registry changes and disabled login screensaver/screen sleep
What about disabling the login screen saver (WinXP/2003) or login screen sleep (Win7/2008R2+)?
| Windows version | Console OFF long idle (3) | Console OFF | Console ON | Console login | Terminal Server login | Locked session |
| Windows XP | yes | yes | yes | yes | no (1,4) | no (1,4) |
| Windows 2003R2 | yes | yes | yes | yes | yes | no |
| Windows 7 | yes | yes | yes | yes | yes | no |
| Windows 2008R2 | yes | yes | yes | yes | yes | no |
| Windows 2012R2 | yes | yes | yes | yes | yes | no |
Notes:
- it requires manual console-based shutdown confirmation
- it require two ACPI shutdown events: the first one exits from the screensaver, the second one shutdown the machine
- long idle = login screen with screensaver or monitor sleep
- warning timeout not working on winxp: http://www.pcreview.co.uk/threads/how-to-disable-shutdown-warning-message.2688069/
- the screensaver is never exited, but as soon you move the mouse, a sudden shutdown happens
- Win7 / 2008R2 / 2012R2 do not appear to have a login screensaver by default. Rather they put monitor to sleep, by default. To enable login screensave, give a look at https://support.microsoft.com/en-us/kb/185348
The two-ACPI-events-for-shutdown behavior is now gone. On the other hand, locked session remain, well, locked and (almost) totally unresponsive to shutdown events.