# ansible windows

**URL:** <https://forum.ansible.com/t/ansible-windows/32456>\
**Category:** Ansible Project\
**Tags:** windows, galaxy-ng\
**Created:** [March 13, 2020, 5:16pm UTC](https://forum.ansible.com/t/ansible-windows/32456 "2020-03-13T17:16:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew\_Meyer1](https://avatars.discourse-cdn.com/v4/letter/a/df705f/32.png) [@Andrew\_Meyer1](https://forum.ansible.com/u/Andrew_Meyer1)\
**Post date:** [March 13, 2020, 5:16pm UTC](https://forum.ansible.com/t/ansible-windows/32456/1 "2020-03-13T17:16:51Z")

</div>

Getting the following error when trying to install the ansible windows collection.

I am running Ansible 2.9.6 from pip3 on CentOS 8.

`$ ansible-galaxy collection install ansible.windows Process install dependency map ERROR! Cannot meet requirement * for dependency ansible.windows from source 'https://galaxy.ansible.com/api/'. Available versions before last requirement added: Requirements from: base - 'ansible.windows:*'`

I also tried from the rpm version of ansible. Same issue.

---

<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 13, 2020, 9:03pm UTC](https://forum.ansible.com/t/ansible-windows/32456/2 "2020-03-13T21:03:17Z")

</div>

That is because the ansible.windows collection because the current released versions at [https://galaxy.ansible.com/ansible/windows](https://galaxy.ansible.com/ansible/windows) are all beta versions. The ansible-galaxy cli tool does not use any pre-release versions in it’s check and the only way to install it is to explicitly set the version like

`  
ansible-galaxy collection install ansible.windows:0.0.1-beta.2

`

Once a proper release is out then the install command will select the latest non-prerelease version as expected but for you now you need to explicitly opt in.

---

<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 13, 2020, 9:03pm UTC](https://forum.ansible.com/t/ansible-windows/32456/3 "2020-03-13T21:03:56Z")

</div>

I also forgot to mention that while some components may work in 2.9 this collection will not be tested against this version and will officially be designed to work with 2.10 onwards.

---

<div class="post-metadata">

**Author:** ![Andrew\_Meyer1](https://avatars.discourse-cdn.com/v4/letter/a/df705f/32.png) [@Andrew\_Meyer1](https://forum.ansible.com/u/Andrew_Meyer1)\
**Post date:** [March 13, 2020, 9:09pm UTC](https://forum.ansible.com/t/ansible-windows/32456/4 "2020-03-13T21:09:16Z")

</div>

Would it be wise to wait for 2.10?

---

<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 13, 2020, 9:21pm UTC](https://forum.ansible.com/t/ansible-windows/32456/5 "2020-03-13T21:21:12Z")

</div>

If you are wanting to play around with things there’s no harm in it. If you are wanting to use it in production I would wait until some of the kinks are ironed out and 2.10 is officially released.

That’s not to say you can use it side by side and selectively try out various modules in the collection if you want to use a newer version.