Remote Desktop: No option to Shutdown, Restart, or Sleep.

NOTE: I have already resolved this issue with the "big hammer" option Reset this PC. As a result, I can't troubleshoot further to figure out what caused this issue in the first place, just wondering if anyone has any ideas on what may have caused this just in case I encounter the issue again.

This is a brand new Mini PC that came with Win 11 Pro preinstalled. Everything worked flawlessly with one small exception: When I connect to it via Remote Desktop, there is no option in the GUI to perform a shutdown, restart, or sleep. In order to shutdown or restart, I need to do so from a command prompt. If I logon to the machine locally I have no such problem.

I am already aware of the Group Policy called Remove and Prevent Access to the Shut Down command and this is set to Not configured.

I ran

DISM.exe /Online /Cleanup-image /Restorehealth

and

SFC /Scannow

Neither of these made any difference nor did they find any issues.

I also enabled the built-in Administrator account and tested with it. Same problem on the Administrator account.

I should note that a friend of mine had purchased the exact same model PC a week before I did, running the same Windows image and his machine does not have this issue. In other words, I don't think that the problem has anything to do with the factory system image.

After much research and finding nothing, I decided to try the Reset this PC option and that did solve the issue. I'm glad it's solved, but I'm still curious to know if anyone has ideas on what may have caused this.

I don't think that system specs will really help in this instance, but for the sake of completeness, here they are:

Mini PC, Ace Magician model AD03
Intel N95 CPU
16 GB RAM
512 GB SATA M.2 SSD
512 GB SATA 2.5" SSD (added after purchase)
Intel AX210 WiFi 6e / Bluetooth 5.3 (replaced the awful Reltek adapter from the factory)
2 x Realtek Gigabit Ethernet
Firmware TPM 2.0

Idea ideas would be appreciated.

What about setting the GPO to disabled?

johnlgalt said:

What about setting the GPO to disabled?

Click to expand...

Yeah, that's a good thought, but I had tried that. I also enabled it first, then disabled it, then set it back to not configured. At no point did it change the problem.

Very odd issue. I can't think of anything that I did that would have altered that behavior.

Indeed. It's weird.

And yet, for some odd reason, I seem to remember this exact problem occurring when I was running VMs of 10 in Windows 10 Hyper-V, too. My end result was wiping the VM and starting over and then it worked, similar to your reset. Very odd.