# Windows scripts executed without "-ExecutionPolicy Unrestricted" in Ansible 1.9

**URL:** <https://forum.ansible.com/t/windows-scripts-executed-without-executionpolicy-unrestricted-in-ansible-1-9/17940>\
**Category:** Ansible Developer\
**Tags:** windows\
**Created:** [April 9, 2015, 11:16am UTC](https://forum.ansible.com/t/windows-scripts-executed-without-executionpolicy-unrestricted-in-ansible-1-9/17940 "2015-04-09T11:16:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ivaylo\_Bratoev](https://avatars.discourse-cdn.com/v4/letter/i/f9ae1b/32.png) [@Ivaylo\_Bratoev](https://forum.ansible.com/u/Ivaylo_Bratoev)\
**Post date:** [April 9, 2015, 11:16am UTC](https://forum.ansible.com/t/windows-scripts-executed-without-executionpolicy-unrestricted-in-ansible-1-9/17940/1 "2015-04-09T11:16:15Z")

</div>

Since 1.9 I noticed that Ansible runs the Windows modules/scripts without specifying Unrestricted execution policy. The change was made in a this commit: [https://github.com/ansible/ansible/commit/07dfbaedc30944857afc32cf2d3303d46b9cf3c9](https://github.com/ansible/ansible/commit/07dfbaedc30944857afc32cf2d3303d46b9cf3c9)  
I noticed that in the v2 folder Execution Policy is still set to Unrestricted. So my question is - is the removing of “-ExecutionPolicy Unrestricted” intentional or can be considered bug?

---

<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:** [April 9, 2015, 7:39pm UTC](https://forum.ansible.com/t/windows-scripts-executed-without-executionpolicy-unrestricted-in-ansible-1-9/17940/2 "2015-04-09T19:39:34Z")

</div>

Yep, it's a bug. Fixed in [https://github.com/ansible/ansible/pull/10664](https://github.com/ansible/ansible/pull/10664)