# Module Suffix's and custom windows modules

**URL:** <https://forum.ansible.com/t/module-suffixs-and-custom-windows-modules/17225>\
**Category:** Ansible Project\
**Tags:** windows\
**Created:** [January 9, 2015, 4:04am UTC](https://forum.ansible.com/t/module-suffixs-and-custom-windows-modules/17225 "2015-01-09T04:04:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tony\_Kinsley](https://avatars.discourse-cdn.com/v4/letter/t/b19c9b/32.png) [@Tony\_Kinsley](https://forum.ansible.com/u/Tony_Kinsley)\
**Post date:** [January 9, 2015, 4:04am UTC](https://forum.ansible.com/t/module-suffixs-and-custom-windows-modules/17225/1 "2015-01-09T04:04:41Z")

</div>

I have a custom windows module that I have been using in my playbooks and I just went to update to the version 1.8.2 ( installed with pip ). I went to run a playbook that I run all the time and got this error:

`

/usr/local/bin/ansible-playbook -i ./core/inventory.py --module-path ./modules/ ./main.yml  
ERROR: win\_exe is not a legal parameter in an Ansible task or handler

`

My module is in a file called win\_exe.ps1 ( it’s basically just runs a windows command but adds in support for the creates keyword ) located ./modules. I changed the playbook to specify

`

- name: install packages  
win\_exe.ps1:  
exe: ‘C:\Users\admin\_user\Downloads\myapp.exe’  
ArgumentList: ‘/w /S /v"/l\*v "C:\Users\admin\_user\AppData\Local\Temp\myapp.log" /qn"’  
creates: ‘{{myapp\_root}}/sbin/myapp.exe’

`

and now it works. I was just wondering whether this is expected and when to expect to require a suffix and when not to expect to need a suffix. Previously I was running ansible version 1.8.

Thanks,  
Tony

---

<div class="post-metadata">

**Author:** ![Chris\_Church1](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@Chris\_Church1](https://forum.ansible.com/u/Chris_Church1)\
**Post date:** [January 9, 2015, 4:58am UTC](https://forum.ansible.com/t/module-suffixs-and-custom-windows-modules/17225/2 "2015-01-09T04:58:50Z")

</div>

It should work without the suffix. However, I’m seeing the same issue with 1.8, 1.8.1 and 1.8.2.

In my case, it works when using ansible to run an adhoc command, but not ansible-playbook:

---

<div class="post-metadata">

**Author:** ![Chris\_Church1](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@Chris\_Church1](https://forum.ansible.com/u/Chris_Church1)\
**Post date:** [January 9, 2015, 5:16am UTC](https://forum.ansible.com/t/module-suffixs-and-custom-windows-modules/17225/3 "2015-01-09T05:16:53Z")

</div>

>

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [January 10, 2015, 1:14am UTC](https://forum.ansible.com/t/module-suffixs-and-custom-windows-modules/17225/4 "2015-01-10T01:14:24Z")

</div>

Can you test against the latest devel? there was an issue in which if  
you did not have the corresponding win\_\<mod\>.py ansible would not  
correctly detect the module existence at 'play compile time'.