# Cannot enable WinRM remoting on Windows 10 Home Edition

**URL:** <https://forum.ansible.com/t/cannot-enable-winrm-remoting-on-windows-10-home-edition/27130>\
**Category:** Ansible Project\
**Tags:** windows\
**Created:** [March 27, 2018, 3:09pm UTC](https://forum.ansible.com/t/cannot-enable-winrm-remoting-on-windows-10-home-edition/27130 "2018-03-27T15:09:21Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dinesh\_Vashisht](https://avatars.discourse-cdn.com/v4/letter/d/2acd7d/32.png) [@Dinesh\_Vashisht](https://forum.ansible.com/u/Dinesh_Vashisht)\
**Post date:** [March 27, 2018, 3:09pm UTC](https://forum.ansible.com/t/cannot-enable-winrm-remoting-on-windows-10-home-edition/27130/1 "2018-03-27T15:09:21Z")

</div>

While trying to enable PowerShell removing on Windows 10 Home Edition following error displayed:

192.168.169.76 | UNREACHABLE! =\> {  
“changed”: false,  
“msg”: “ssl: the specified credentials were rejected by the server”,  
“unreachable”: true  
}

The ‘/etc/ansible/hosts’ and ‘group\_vars’ have correct entries.

Any suggestions?

Dinesh Vashisht

---

<div class="post-metadata">

**Author:** ![j.r.hawkesworth](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@j.r.hawkesworth](https://forum.ansible.com/u/j.r.hawkesworth)\
**Post date:** [March 27, 2018, 3:12pm UTC](https://forum.ansible.com/t/cannot-enable-winrm-remoting-on-windows-10-home-edition/27130/2 "2018-03-27T15:12:50Z")

</div>

double check the password is correct - that error implies the username/password combination doesn’t exist or is incorrect on the windows hosts.

---

<div class="post-metadata">

**Author:** ![Anil](https://avatars.discourse-cdn.com/v4/letter/a/da6949/32.png) [@Anil](https://forum.ansible.com/u/Anil)\
**Post date:** [March 27, 2018, 10:33pm UTC](https://forum.ansible.com/t/cannot-enable-winrm-remoting-on-windows-10-home-edition/27130/3 "2018-03-27T22:33:24Z")

</div>

Check here -  
[https://github.com/ansible/ansible/issues/16478](https://github.com/ansible/ansible/issues/16478)

---

<div class="post-metadata">

**Author:** ![jborean](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jborean/32/1525_2.png) [@jborean](https://forum.ansible.com/u/jborean)\
**Post date:** [March 28, 2018, 1:30am UTC](https://forum.ansible.com/t/cannot-enable-winrm-remoting-on-windows-10-home-edition/27130/4 "2018-03-28T01:30:28Z")

</div>

As others have pointed out, WinRM is enabled but it is rejecting the user you are trying to connect with. This can be due to numerous reasons but here are the most common ones

- The username or password is incorrect
- Basic auth is not enabled on the WinRM side, need to run **Set-Item -Path WSMan:\localhost\Service\Auth\Basic -Value $true**
- The account is not an administrator or does not have permission on the WinRM endpoint, see the post above for how to configure this
- The account has not been granted the SeNetworkLogonRight [https://technet.microsoft.com/en-us/library/dd277311.aspx?f=255&MSPPError=-2147217396](https://technet.microsoft.com/en-us/library/dd277311.aspx?f=255&MSPPError=-2147217396), if the user is an admin then by default it should
- You are connecting over http but don’t have message encryption, this won’t be the case as you are running over HTTPS
- Using a domain account over basic auth, I see you are using SSL (basic over TLS) and are on the home edition so this won’t be it

Without more detail from yourself, such as the account you are trying to connect with, the output of **winrm get winrm/config/service** and your group\_vars set (sans the password) there is not too much we can do.

Thanks

Jordan

---

<div class="post-metadata">

**Author:** ![Dinesh\_Vashisht](https://avatars.discourse-cdn.com/v4/letter/d/2acd7d/32.png) [@Dinesh\_Vashisht](https://forum.ansible.com/u/Dinesh_Vashisht)\
**Post date:** [March 28, 2018, 1:53pm UTC](https://forum.ansible.com/t/cannot-enable-winrm-remoting-on-windows-10-home-edition/27130/5 "2018-03-28T13:53:17Z")

</div>

Thanks J Hawkesworth,

After correcting the username it worked.

192.168.169.76 | SUCCESS =\> {  
“changed”: false,  
“ping”: “pong”  
}

Regards,  
Dinesh Vashisht