# Is win\_msi deprecated or not ?

**URL:** <https://forum.ansible.com/t/is-win-msi-deprecated-or-not/24246>\
**Category:** Ansible Project\
**Created:** [April 19, 2017, 10:24am UTC](https://forum.ansible.com/t/is-win-msi-deprecated-or-not/24246 "2017-04-19T10:24:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tai\_Kedzierski](https://avatars.discourse-cdn.com/v4/letter/t/b77776/32.png) [@Tai\_Kedzierski](https://forum.ansible.com/u/Tai_Kedzierski)\
**Post date:** [April 19, 2017, 10:24am UTC](https://forum.ansible.com/t/is-win-msi-deprecated-or-not/24246/1 "2017-04-19T10:24:43Z")

</div>

Hello

_(Apologies if this is a double-post - I am sure I posted yesterday, but I do not see the item in the list or in my activities…)_

The docs page for the win\_msi module states that the module is deprecated, and its information seems clipped (incomplete sentence in the explanation)

[http://docs.ansible.com/ansible/win\_msi\_module.html](http://docs.ansible.com/ansible/win_msi_module.html)

But the general modules list does not (no “D:” on the module name)

[http://docs.ansible.com/ansible/list\_of\_windows\_modules.html](http://docs.ansible.com/ansible/list_of_windows_modules.html)

My questions are:

- Is win\_msi really deprecated ?
- If so, what’s the new preferred method ?

---

<div class="post-metadata">

**Author:** ![Matt\_Davis](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@Matt\_Davis](https://forum.ansible.com/u/Matt_Davis)\
**Post date:** [April 20, 2017, 5:48pm UTC](https://forum.ansible.com/t/is-win-msi-deprecated-or-not/24246/2 "2017-04-20T17:48:03Z")

</div>

It’s on the way to being deprecated (most likely we’ll do it for real in 2.4)- win\_package is the recommended replacement, but we’ve been holding off on “really” deprecating win\_msi until we make some usability changes to win\_package. The big one is that you have to look up the product ID to supply it to win\_package, but that’s not necessary with an MSI unless it’s being hosted remotely (so the module can query for the product\_id without downloading the msi). So we’ll be relaxing that requirement, as well as tweaking around a few other things.

---

<div class="post-metadata">

**Author:** ![Tai\_Kedzierski](https://avatars.discourse-cdn.com/v4/letter/t/b77776/32.png) [@Tai\_Kedzierski](https://forum.ansible.com/u/Tai_Kedzierski)\
**Post date:** [April 21, 2017, 2:49pm UTC](https://forum.ansible.com/t/is-win-msi-deprecated-or-not/24246/3 "2017-04-21T14:49:45Z")

</div>

OK thanks - I’ll hold off using win\_msi at all then… definitely would not want to have to re-do this configuration needlessly !

---

<div class="post-metadata">

**Author:** ![Trond\_Hindenes](https://avatars.discourse-cdn.com/v4/letter/t/96bed5/32.png) [@Trond\_Hindenes](https://forum.ansible.com/u/Trond_Hindenes)\
**Post date:** [April 22, 2017, 5:09pm UTC](https://forum.ansible.com/t/is-win-msi-deprecated-or-not/24246/4 "2017-04-22T17:09:09Z")

</div>

As far as I can remember I did a PR trying to accomodate some of this, but it may have been lost when we stopped using separate module repos. I’ll look up on this.