Skip to main content
added 2 characters in body
Source Link
KJ7LNW
  • 383
  • 3
  • 14

We have Windows 10 running under KVM but it won't shut down when it gets an ACPI power button request triggered by virsh shutdown win10 after a user locks the console---however, it will under the following conditions:

  • No user is logged in
  • User is logged in, screen is not locked
  • User is logged in via Remote Desktop and console is locked because of the remote session.

Here is the question: How do we make it shut down under all circumstances (in this case when the local console is locked by a local user, not by RDP)?

We tried setting Local Group Policy Editor->Computer Config->Windows Settings->Security Settings->Local Policy->User Right Assignment->Shut down the system for allowing "ANONYMOUS".\ANONYMOUS LOGON" but that doesn't seem to help.

We have Windows 10 running under KVM but it won't shut down when it gets an ACPI power button request triggered by virsh shutdown win10 after a user locks the console---however, it will under the following conditions:

  • No user is logged in
  • User is logged in, screen is not locked
  • User is logged in via Remote Desktop and console is locked because of the remote session.

Here is the question: How do we make it shut down under all circumstances (in this case when the local console is locked by a local user, not by RDP)?

We tried setting Local Group Policy Editor->Computer Config->Windows Settings->Security Settings->Local Policy->User Right Assignment->Shut down the system for allowing "ANONYMOUS LOGON" but that doesn't seem to help.

We have Windows 10 running under KVM but it won't shut down when it gets an ACPI power button request triggered by virsh shutdown win10 after a user locks the console---however, it will under the following conditions:

  • No user is logged in
  • User is logged in, screen is not locked
  • User is logged in via Remote Desktop and console is locked because of the remote session.

Here is the question: How do we make it shut down under all circumstances (in this case when the local console is locked by a local user, not by RDP)?

We tried setting Local Group Policy Editor->Computer Config->Windows Settings->Security Settings->Local Policy->User Right Assignment->Shut down the system for allowing ".\ANONYMOUS LOGON" but that doesn't seem to help.

more specific explanation
Source Link
KJ7LNW
  • 383
  • 3
  • 14

We have Windows 10 running under KVM but it won't shut down when it gets an ACPI power button request triggered by virsh shutdown win10 after a user locks the console---however, it will under the following conditions:

  • No user is logged in
  • User is logged in, screen is not locked
  • User is logged in via Remote Desktop and console is locked because of the remote session.

Here is the question: How do we make it shut down under all circumstances (in this case when the local console is locked by a local user, not by RDP)?

We tried setting Local Group Policy Editor->Computer Config->Windows Settings->Security Settings->Local Policy->User Right Assignment->Shut down the system for allowing "ANONYMOUS USER"LOGON" but that doesn't seem to help.

We have Windows 10 running under KVM but it won't shut down when it gets an ACPI power button request triggered by virsh shutdown win10 after a user locks the console---however, it will under the following conditions:

  • No user is logged in
  • User is logged in, screen is not locked
  • User is logged in via Remote Desktop and console is locked because of the remote session.

Here is the question: How do we make it shut down under all circumstances (in this case when the local console is locked by a local user, not by RDP)?

We tried setting Local Policy->User Right Assignment->Shut down the system for allowing "ANONYMOUS USER" but that doesn't seem to help.

We have Windows 10 running under KVM but it won't shut down when it gets an ACPI power button request triggered by virsh shutdown win10 after a user locks the console---however, it will under the following conditions:

  • No user is logged in
  • User is logged in, screen is not locked
  • User is logged in via Remote Desktop and console is locked because of the remote session.

Here is the question: How do we make it shut down under all circumstances (in this case when the local console is locked by a local user, not by RDP)?

We tried setting Local Group Policy Editor->Computer Config->Windows Settings->Security Settings->Local Policy->User Right Assignment->Shut down the system for allowing "ANONYMOUS LOGON" but that doesn't seem to help.

Source Link
KJ7LNW
  • 383
  • 3
  • 14

Why wont Windows 10 Pro shut down with the ACPI power button when screen is locked locally?

We have Windows 10 running under KVM but it won't shut down when it gets an ACPI power button request triggered by virsh shutdown win10 after a user locks the console---however, it will under the following conditions:

  • No user is logged in
  • User is logged in, screen is not locked
  • User is logged in via Remote Desktop and console is locked because of the remote session.

Here is the question: How do we make it shut down under all circumstances (in this case when the local console is locked by a local user, not by RDP)?

We tried setting Local Policy->User Right Assignment->Shut down the system for allowing "ANONYMOUS USER" but that doesn't seem to help.