win_updates does not list feature updates about ansible.windows HOT 8 CLOSED

Morning guys, I'm curious if you have an idea on what direction you plan to go here. Currently we are seeing 2004 reported on 1909 hosts, win_updates seems to see 1 update available, however - since it cant "install" it, it just reboots the host in a loop until timeout. I can log a new case with Redhat support if thats new behavior.

win_updates: check win_updates results for automatic reboot: {"updates": {"1656cdd2-2e73-4fd8-9ab9-02097d5c7544": {"id": "1656cdd2-2e73-4fd8-9ab9-02097d5c7544", "title": "Feature update to Windows 10 (business editions), version 2004, en-us x64", "categories": ["Upgrades", "Windows 10, version 1903 and later"], "kb": ["3012973"], "installed": true}}, "failed_update_count": 0, "found_update_count": 1, "changed": false, "reboot_required": true, "installed_update_count": 1, "filtered_updates": {}, "_ansible_parsed": true

code:

  - name: Install Other Updates
    win_updates:
      category_names:
        - Application
        - Connectors
        - DefinitionUpdates
        - Tools
        - Updates
        - Upgrades
      reboot: yes
      reboot_timeout: 1200

ansible 2.10.1
  config file = /home/*******/git/ansible-windows/ansible.cfg
  configured module search path = ['/home/******/git/ansible-windows/library']
  ansible python module location = /usr/local/lib/python3.6/site-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 3.6.8 (default, Aug 18 2020, 08:33:21) [GCC 8.3.1 20191121 (Red Hat 8.3.1-5)]

from ansible.windows.

I've spent a few hours trying to figure this out but ultimately I haven't found a solution. I can't even find the feature updates in the Microsoft Update Catalog which makes me suspect there's a completely separate mechanism that the Settings update UI uses to determine if there is one available.

As for the preview cumulative updates I've not sure on that as it does exist the update catalog. I wasn't even able to search for that update by specifying the actual GUID for the update.

I don't know of the actual solution to this problem so if anyone can shed some light I'm definitely interested to hear from you.

from ansible.windows.

What little info I can find implies that those are distributed as full OS images via ESD rather than the normal Windows update stuff... They seem to show up in WSUS, but are consumed by another mechanism. While it's probably possible for us to automate it at some point, getting it to work without production of things like unattend.xml to bypass the OOBE seems like a pretty big blocker to useful automation- it's likely that blindly updated hosts would be dead in the water and require manual console intervention.

from ansible.windows.

Do you happen to have a WSUS server that might be hosting this update?

from ansible.windows.

Yes - the update is being hosted by WSUS

from ansible.windows.

Our plan for now ( per @mwtrigg ) is to blacklist the KB. Which I'm guessing will work from keeping the side effect of looping reboots.

from ansible.windows.

Any updates with regards to this?

from ansible.windows.

There's no updates, after learning more about this setup I'm not sure it's something we can do anything about. This is basically how Windows Updates works and it's API.

from ansible.windows.