How do you identify Microsoft Office updates to determine whether or not to download or apply them, since the KB number does not appear in the file name? For example, the 06/22/2017 "Security Update for Microsoft Office Outlook 2007 (KB3191898)" has the file name "outlook-x-none_9074b332e588526264deb590fd6f9f90f6f5b5ed" (whether downloaded from the Windoze Update Catalog or via WSUS Offline).

During installation, these Update Ids are used to determine missing updates.

I wonder, if the same approach could be used to query missing updates for the .NET Frameworks. There we have the situation, that the new update rollups for .NET Frameworks have kb numbers, but no files directly associated with it. The individual updates have different kb numbers. Somehow, the connection between the update rollups and the included downloads gets lost in WSUS Offline Update: The individual files are downloaded, but they won't get installed.

Using the Update Ids to query missing updates might work around this situation.

The catalog wsusscn2.cab does contain all updates based on their UpdateId. Based on those it defines dependencies, supersedences, download links and so on. When downloading, wsusou extracts all UpdateIds for Office updates. While determining the download links from the catalog, wsusou matches the UpdateIds with the file names (= last part of the download links) and writes them into a CSV-file.While installing, the Windows Update Agent reports two values: the UpdateId and the KB-number. Normally one UpdateId matches one KB-number. So we can use the Windows version and the KB-number to determine the file name and path.But for each Office version, there is one update, but all with the same KB-number. Thats why we use the CSV-file.