# win\_chocolatey does not update programs/features list on the windows target os **URL:** \ **Category:** Ansible Project\ **Tags:** windows\ **Created:** [December 14, 2018, 1:02pm UTC](https://forum.ansible.com/t/win-chocolatey-does-not-update-programs-features-list-on-the-windows-target-os/29265 "2018-12-14T13:02:58Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Serge\_Zajac](https://avatars.discourse-cdn.com/v4/letter/s/d2c977/32.png) [@Serge\_Zajac](https://forum.ansible.com/u/Serge_Zajac)\ **Post date:** [December 14, 2018, 1:02pm UTC](https://forum.ansible.com/t/win-chocolatey-does-not-update-programs-features-list-on-the-windows-target-os/29265/1 "2018-12-14T13:02:58Z")
Hi cheers, When using win\_chocolatey module to deploy a package, it install the package but do not update programs/features list on the OS.Installing directly with choco do not have this behaviour Is anyone can confirm this behaviour. Can it be a bug to report ? regards ---
**Author:** ![goforawalktwice](https://avatars.discourse-cdn.com/v4/letter/g/c5a1d2/32.png) [@goforawalktwice](https://forum.ansible.com/u/goforawalktwice)\ **Post date:** [December 14, 2018, 8:08pm UTC](https://forum.ansible.com/t/win-chocolatey-does-not-update-programs-features-list-on-the-windows-target-os/29265/2 "2018-12-14T20:08:29Z")
Hi, am not a user of Chocloatey yet but have been doing a lot of .msi installs … the Progs/Features screen seems to automatically refresh sometimes but not always. Could it be that ? Regards, Straff ---
**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:** [December 14, 2018, 9:34pm UTC](https://forum.ansible.com/t/win-chocolatey-does-not-update-programs-features-list-on-the-windows-target-os/29265/3 "2018-12-14T21:34:33Z")
The win\_chocolatey module just calls choco install just like you would do locally. There’s no reason that I can think off that would not have it appear in the list. I use win\_chocolatey and can verify that most of the packages I install appear in that list. The ones that don’t aren’t actually programs so I don’t expect them to appear there. If you are seeing this behaviour, please share the package name so we can try and verify whether it’s a bug with the module or something else. Thanks Jordan ---
**Author:** ![goforawalktwice](https://avatars.discourse-cdn.com/v4/letter/g/c5a1d2/32.png) [@goforawalktwice](https://forum.ansible.com/u/goforawalktwice)\ **Post date:** [January 1, 2019, 4:32am UTC](https://forum.ansible.com/t/win-chocolatey-does-not-update-programs-features-list-on-the-windows-target-os/29265/4 "2019-01-01T04:32:49Z")
Hi, Did your problem get solved? Another possibility is that if the account being used to install software is different to the one looking at “Programs and Features” / “Uninstall Programs” and that “ALLUSERS=1” (or some sort of equivalent) was not specified (either as an arg to win\_package or baked into the .msi package itself as a default) then it won’t show up. I’ve been caught out by this before. Just a thought. ---
**Author:** ![Serge\_Zajac](https://avatars.discourse-cdn.com/v4/letter/s/d2c977/32.png) [@Serge\_Zajac](https://forum.ansible.com/u/Serge_Zajac)\ **Post date:** [January 3, 2019, 1:18pm UTC](https://forum.ansible.com/t/win-chocolatey-does-not-update-programs-features-list-on-the-windows-target-os/29265/5 "2019-01-03T13:18:04Z")
Hello, no problem is not really solved. But as you mentionned, sometimes, list is updated, i have to check this with my system admins team. The package is a custom package and params in the chocolateyinstall.ps1 are silentArgs = “/qn /norestart /l\*v `"$env:TEMP\chocolatey\$($packageName)\$($packageName).MsiInstall.log`”" ---
**Author:** ![goforawalktwice](https://avatars.discourse-cdn.com/v4/letter/g/c5a1d2/32.png) [@goforawalktwice](https://forum.ansible.com/u/goforawalktwice)\ **Post date:** [January 8, 2019, 1:26am UTC](https://forum.ansible.com/t/win-chocolatey-does-not-update-programs-features-list-on-the-windows-target-os/29265/6 "2019-01-08T01:26:36Z")
ok, you could check that MsiInstall.log for value of ALLUSERS - if it’s not ‘1’ and you are installing via a different account to that for viewing Progs/Features then it makes sense. You could try adding ALLUSERS=1 as a property/arg and see what you get Regards, Straff