none
Windows 10 cant use shutdown command on a network PC! (Access is denied (5)) RRS feed

  • Question

  •      Hi I have searched for this issue for few days but could not found any good answer.

      In my network I have some PC's witch I shutdown remotely. This works for a long time on win 7 but recently I bought a new PC and it has windows 10. Same commands same Network sharing options, but different results.

     This is the command I use: shutdown.exe /s /m \\PC2 /t 00 and it works from win 7.

     The only difference I found in configs was the homegroup, and recently I saw that Microsoft removed homegroup from win 10. In win 7 I had an option saying "allow windows to manage homegroup connections (recommended)". In 10 this is gone...

     Could this be the problem? Anyone can help me with a fix?

    Tuesday, November 26, 2019 11:37 PM

All replies

  • Hi,

    You may try command line "shutdown /r /t settime" (it`s unit is "s"). "/r" means "restart". "/s" means "shutdown" in CMD.

    About more details, you can refer the following link:

    https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/shutdown

    Remember that the server must be members of the Administrators group to annotate an unexpected shutdown of a local or remotely administered computer. 

    Hope this can help you, if you have anything unclear, please let me know.

    Have a nice day!

    Ellen



    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.




    Wednesday, November 27, 2019 6:56 AM
  •      Hi and thanks for reply.

      I'm not new to this, I use NET Use and commands for some time now. I know what R, S and T mean, I also use this command:

    shutdown.exe /s /m \\PC1 /t 00

    everyday, and it works but on windows 7. Same command also "work" on windows 10, I dont get error 53 or anything connection related, I get "PC1: Access is denied.(5)" witch means the command goes to the PC, and there it gets rejected.

     I use the same user as on windows 7 and the user has admin rights on PC1 (the one I try to shutdown), both PC's are on the same workgroup, I also made all the settings in secpol.msc for a long time.

    I tried activating these services as well:

       - Function Discovery Provider Host

       - Function Discovery Resource Publication

       - SSDP Discovery

       - UPnP Device Host

    Nothing worked.

    Wednesday, November 27, 2019 6:06 PM
  •      No one knows? There are a lot of people in my situation, there should definitely be a solution for shutting down a PC remotely with shutdown command from a Win 10 PC.

    Saturday, November 30, 2019 11:33 PM
  • Hello,

    Does the shutdown command work locally on the machine that it fails remotely on or does it only fail when run remotely?

    Are there any group polices in place?

    For Example in the Group Policy Editor look at this setting:

    Computer configuration\administrative Templates\Windows Components\Shutdown option: Turn Off Remote Shutdown Interface


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, December 3, 2019 5:14 PM
  •  Hello,

     This is my setup:

     1. PC Win 10 (this is new, works shutdown command on self, but dose not work on any other PC from network)

     2. PC Win 7 (this is old, works shutdown command on anything. I can stop any PC from network)

     3. PC 3 (this is a file server, all settings were made in order for shutdown command to work, including secpol.msc configs)

    "Are there any group polices in place?

    For Example in the Group Policy Editor look at this setting:

    Computer configuration\administrative Templates\Windows Components\Shutdown option: Turn Off Remote Shutdown Interface"

     I checked this, and there are 2 polices there:

     - Turn off legacy remote shutdown interface (and it is Not Configured)

     - Timeout for hung logon sessions during shutdown (and it is Not Configured)

     both these settings are on PC Win 10.

     Should I change any of these?

    Friday, December 6, 2019 6:53 PM
  • Hello,

    No you should not need to change either of those policies.

    Can you access shares on the Windows 10 computer? Share a folder and see it can be accessed

    Can you do Remote Registry?  Open Regedit on a Windows 7 machines and try to connect to the registry of the Windows 10 machine(In Regedit, under the file menu is a connect network registry option).  If that doesn't work admin sharing may be disabled


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, December 9, 2019 8:36 PM
  •    Hello,

     

      I have tried as you said and the result was like this:

     1. I shared some folders on both PC's, with the same settings and all, and the shares from win 10 could not be accessed, but the ones from win 7 I was able to access from win 10.

     2. I tried to access Remote Registry, but here it was a bi tricky because i have no users with passwords on win 7 or win 10. Both asked me for user and pass and I did not had users and passwords to test.

     Should I try to enable admin sharing on win 10?


    • Edited by Paltinis Saturday, December 14, 2019 10:18 PM
    Saturday, December 14, 2019 10:18 PM