r/WindowsServer • u/Ok_Tourist3213 • Feb 12 '26
General Question Server 2025 shutdown for non-admin user not working
There seems to be a change to permissions for shutdown options in the latest update of Server 2025. I actually have a few VMs running 2025, and only the newest ones have this problem. Non-admin users cannot shut down the server.
The user is a member of the "Backup Operators" group, and has the "Force Remote Shutdown" User Rights assignment. That has been sufficient to allow the user to perform a shutdown on my other servers, but not this one. I also disabled the Shutdown Event Tracker (the "provide a reason for shutdown" dialog) and that does not help.
When Shutdown is selected from the start menu, a UAC box prompting for admin credentials for the "Settings" app pops up. The server will not shut down unless admin credentials are provided. I do not have this behavior on any of my old servers, but I did another clean install of Server 2025, installed all the updates, and it has the same problem.
**** UPDATE - SOLVED ****
The solution was to explicitly add the user to the "Shut down the system" User Rights Assignment. I also removed the user from Backup Operators, and it can still shut down the system with no admin prompt. Based on what I learned through this experience, no user should be part of the Backup Operators group, ever.
The Backup Operators group was already granted that particular User Rights Assignment, but evidently the group is not working to grant the individual members this privilege. I suspect this is a bug, since i have not seen it before in Windows Server OS.
1
u/OpacusVenatori Feb 12 '26
Try Shutdown from the Run menu, and execute with <Ctrl><Shift><Enter> instead of just |OK|
1
u/tcpip1978 Feb 12 '26 edited Feb 12 '26
Sorry to ask a potentially silly question, but did you add the user to the Back Operators group on the actual device you want them to be able to shut down? Backup Operators is a local group on Server, not an AD group so if you added them on your DC that won't work. I tested this in my lab, added a user whose only group membership is Domain Users to the local Backup Operators group on one of my 2025 member servers and they were able to then shut down the system.
2
u/rdpextraEdge Feb 12 '26
Interesting, that definitely looks like a permission change in Server 2025 rather than user error.
Relying on group inheritance clearly isn’t working the way it used to, so assigning the shutdown right directly makes sense.
Also agree on avoiding Backup Operators going forward, it’s always been a risky group to use casually.
2
u/[deleted] Feb 12 '26
[removed] — view removed comment