Windows server shutdown command access denied

The problem is in this part: I am logged in the administrator account. For this to work you need: Either some account which has administrative rights on the target computer.

Then again, this question came from stackoverflow and probably should have been moved to superuser, not ServerFault. The same username and password on the target computer which would be a very bad habit, using the same password on multiple machines. Improve this answer. Hennes Hennes 4, 1 1 gold badge 17 17 silver badges 29 29 bronze badges.

Dai Dai 2, 7 7 gold badges 26 26 silver badges 41 41 bronze badges. James L. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog.

Podcast Making Agile work for data science. How can I get this working again? Sunday, October 14, AM. As Falcon said you need sufficient Local Privileges. Hello, You can alternatively add your matching credentials to the server or computer you are trying to shut down remotely and make sure that the user has sufficient local privileges to perform a shutdown. The problem is access is denied when attempting a remote shutdown using the interactive mode or the following command: shutdown.

Proposed as answer by rhl Friday, October 17, AM. Thursday, August 22, AM. Friday, October 17, AM. Is there a registry solution for this setting? Thanks for the rest, Texas. Tuesday, February 10, AM. Tuesday, March 10, PM. Thermal issues and servers do not go well. I didn't know by configuring specific users to be able to shutdown would remove the default admin group.

Hope this will help out someone else too. I would recommend creating a bat file the person you are delegating the task to can run from their workstation. I find using a temp admin account to run the script works well. To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Best Answer. Pure Capsaicin. Verify your account to enable IT peers to see that you are a professional.

We're having trouble restarting to finish the install. Try again in a little while. Error code: 0xa". To make this even longer, I did get an "Access is denied" in my event logs and when I looked it up, I found this link regarding the start menu having an issue after an windows upgrade.

Not sure if this is related. I got 7 of these but then they went away. The operation will fail with error 0xfffffbf8. The text was updated successfully, but these errors were encountered:. I just upgraded a second server to and had the same issue as before, where none but my original user account can restart the server using Open-Shell. This time I upgraded the OS from the original user account that had installed windows and ClassicShell but there wasn't any difference.

Note that it did pop-up that it needed to re-configure Open-Shell, which happens after every major upgrade. Sorry, something went wrong. I have the same issue. Originally using Classic Shell v4. Created a new VM template of Win So I upgraded to Open Shell hoping that would fix the situation, but it did not. It just won't work with OpenShell. I don't see any errors in Event Viewer.

Hoping someone can figure this out! From a fresh installation of Windows , restarting the computer from Open-Shell worked fine on the first user Administrator but would not allow me to restart the computer on subsequent users.

I don't have any Windows updates to see if it'll let me restart from that screen but I'm curious about that as well. I can't imagine Open-Shell actually affecting the reboot button of the Windows Update screen but perhaps it does. Either way, on my original post, neither way worked. I can still reboot with a command prompt. I'm seeing the same behavior.

I built a non-VM Win server from scratch to do some more testing. While looking into this issue, I discovered that a policy setting would fix both the SM and OpenShell issues I'm not suggesting that it be left "Disabled" this would make the OS less secure , I'm just providing info as to what might be causing the issue. Good find. I set up a group policy for the domain and working great for Domain Admin users.

The reason this fails is because non-local Administrator account for some reason does not have SeShutdownPrivilege.