# The powershell shell family is incompatible with the sudo become plugin **URL:** \ **Category:** Ansible Project\ **Tags:** awx\ **Created:** [August 4, 2020, 7:57pm UTC](https://forum.ansible.com/t/the-powershell-shell-family-is-incompatible-with-the-sudo-become-plugin/33551 "2020-08-04T19:57:29Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Wafi\_sh](https://avatars.discourse-cdn.com/v4/letter/w/2bfe46/32.png) [@Wafi\_sh](https://forum.ansible.com/u/Wafi_sh)\ **Post date:** [August 4, 2020, 7:57pm UTC](https://forum.ansible.com/t/the-powershell-shell-family-is-incompatible-with-the-sudo-become-plugin/33551/1 "2020-08-04T19:57:29Z")
Using AWX 13.0.0 (Ansible 2.9.10) The playbook: ---
**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\ **Post date:** [August 4, 2020, 8:29pm UTC](https://forum.ansible.com/t/the-powershell-shell-family-is-incompatible-with-the-sudo-become-plugin/33551/2 "2020-08-04T20:29:53Z")
This indicates you are running the playbook with become, or the inventory specifies the hosts use become. However, you have not configured the become\_method for those Windows hosts to use `runas` instead of the default `sudo`. ---
**Author:** ![Wafi\_sh](https://avatars.discourse-cdn.com/v4/letter/w/2bfe46/32.png) [@Wafi\_sh](https://forum.ansible.com/u/Wafi_sh)\ **Post date:** [August 6, 2020, 3:59pm UTC](https://forum.ansible.com/t/the-powershell-shell-family-is-incompatible-with-the-sudo-become-plugin/33551/3 "2020-08-06T15:59:38Z")
Thank Matt, I have tried to add “become\_method: winrm” to the group variable but the template still shows become\_method: sudo when running it. Here is the inventory group variables i’m using for the group “win\_test\_nce” in inventory “win-test”: ansible\_connection: winrm ansible\_winrm\_server\_cert\_validation: ignore become\_method: runas The playbook output is with verbosity: PLAYBOOK: dns-fix-win.yml \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* Positional arguments: dns-fix-win.yml verbosity: 4 ask\_pass: True remote\_user: ccitops.admin connection: smart timeout: 10 become: True become\_method: sudo tags: (‘all’,) inventory: (‘/tmp/awx\_74\_qrt3a82d/tmp3pzi6c98’,) subset: win\_test\_nce extra\_vars: (‘@/tmp/awx\_74\_qrt3a82d/env/extravars’,) ask\_vault\_pass: True forks: 5 1 plays in dns-fix-win.yml ---
**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\ **Post date:** [August 6, 2020, 4:07pm UTC](https://forum.ansible.com/t/the-powershell-shell-family-is-incompatible-with-the-sudo-become-plugin/33551/4 "2020-08-06T16:07:48Z")
That verbose output you see, is telling you how `ansible-playbook` was invoked from the command line. It does not reflect inventory variables. ---
**Author:** ![Wafi\_sh](https://avatars.discourse-cdn.com/v4/letter/w/2bfe46/32.png) [@Wafi\_sh](https://forum.ansible.com/u/Wafi_sh)\ **Post date:** [August 6, 2020, 4:30pm UTC](https://forum.ansible.com/t/the-powershell-shell-family-is-incompatible-with-the-sudo-become-plugin/33551/5 "2020-08-06T16:30:47Z")
Thanks again Matt, i’m hitting a wall here, any suggestions? When running it from the Ansible (command line) it works perfectly, but in AWX it seems to be stuck on using sudo as become method! ---
**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\ **Post date:** [August 6, 2020, 4:46pm UTC](https://forum.ansible.com/t/the-powershell-shell-family-is-incompatible-with-the-sudo-become-plugin/33551/6 "2020-08-06T16:46:44Z")
I’d consult the IRC channel or mailing list for AWX and seek help there. This mailing list is for ansible proper, so you may not find too much in depth AWX knowledge here. [https://github.com/ansible/awx#get-involved](https://github.com/ansible/awx#get-involved)