WinRM service could not start

Hello Martin Kovac,

Here are a few things to consider:

• Confirm whether the required ports for WinRM are open and accessible. The default ports are 5985 for HTTP and 5986 for HTTPS. To confirm WinRM is listening on HTTPS, type the following command: winrm enumerate winrm/config/listener
• Try running the command winrm quickconfig in Command Prompt with administrator privileges. This command helps configure the WinRM service with default settings and might provide additional information on any configuration issues
• Check if the WinRM service dependencies are met. Specifically, ensure that any services or components that WinRM relies on are running and configured correctly.

I hope this helps! Please let me know if you need any further assistance.

---If the Answer is helpful, please click "Accept Answer" and upvote it.

I'd suggest checking the event logs for events for this service and using the details for further investigation. Have you seen this thread?  https://social.technet.microsoft.com/Forums/en-US/ad600d2b-a8af-431f-a1c0-42e6ddfa22b8/winrm-wont-start-with-nt-authority-and-when-started-under-another-account-a-connection-error?forum=ITCG

We had the same issue on Windows 2016 and Windows 2022 servers. The root cause was a GPO which contained incorrect settings:

This was applied on the HTTP service on which WinRM is depended on. Changing the REG_SZ to REG_DWORD solved the issue immediately. Adding this to this article as this is exact the same issue. Unfortunately for us, there was not yet a solution known. Hopefully this helps others in the future.