# Improved Windows Pipelining in 2.3

**URL:** <https://forum.ansible.com/t/improved-windows-pipelining-in-2-3/24222>\
**Category:** Ansible Project\
**Tags:** windows\
**Created:** [April 15, 2017, 8:49am UTC](https://forum.ansible.com/t/improved-windows-pipelining-in-2-3/24222 "2017-04-15T08:49:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![John\_V](https://avatars.discourse-cdn.com/v4/letter/j/3be4f8/32.png) [@John\_V](https://forum.ansible.com/u/John_V)\
**Post date:** [April 15, 2017, 8:49am UTC](https://forum.ansible.com/t/improved-windows-pipelining-in-2-3/24222/1 "2017-04-15T08:49:40Z")

</div>

I was just wondering if you need to enable the improved pipelining for Window in 2.3 or is it enabled by default.

---

<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:** [April 15, 2017, 11:18am UTC](https://forum.ansible.com/t/improved-windows-pipelining-in-2-3/24222/2 "2017-04-15T11:18:07Z")

</div>

It should be enabled by default. If you run with a high enough verbosity you will see whether it is running with the exec wrapper or if it is still copying the modules across.

---

<div class="post-metadata">

**Author:** ![John\_V](https://avatars.discourse-cdn.com/v4/letter/j/3be4f8/32.png) [@John\_V](https://forum.ansible.com/u/John_V)\
**Post date:** [April 15, 2017, 11:54am UTC](https://forum.ansible.com/t/improved-windows-pipelining-in-2-3/24222/3 "2017-04-15T11:54:14Z")

</div>

Thanks will test it out.