Microsoft Update Catalog - searching for firmware updates stopped working

Stefan Müller 5 Reputation points
2025-12-11T11:52:34.11+00:00

We are used to search for firmware updates in Microsoft Update Catalog by UEFI res ID (e.g. uefi\res_{da6b5517-b8a0-4028-9b59-23c3ede398d1}) to obtain the UEFI/capsule firmware update.

This has stopped working since last week!

Although the ID is listed among the supported hardware IDs, searching for it returns no results. For example: Update ID 1cc29a9a-ba3c-4d80-9a5e-d8348915d9e3.

Searching for driver updates using the PnP ID still works.

Windows for business | Windows 365 Enterprise
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. VPHAN 10,565 Reputation points Independent Advisor
    2025-12-11T12:35:58.13+00:00

    Hi Stefan Müller,

    Actually this is a known quirk of the Microsoft Update Catalog search engine that surfaces periodically. The search backend frequently changes how it indexes "Hardware IDs" versus "Strict Keywords."

    It appears that Microsoft has recently tweaked the indexing logic for the public-facing Catalog search bar. It often stops indexing specific namespace strings like UEFI\RES_ or ACPI\VEN_ to improve query performance, restricting "ID-based" searches to standard PnP enumerators like PCI\ or USB.

    Since you rely on this for automation or specific targeting, here are the three effective workarounds to find your firmware updates when the direct ID search fails.

    1: The "Google Dork" Method (Most Effective)

    The internal search engine of the Update Catalog is often worse than external search engines indexing it. Google or Bing usually capture the text on the page (which lists the supported Hardware IDs) even when the site's own search bar ignores them.

    Try searching this string in Google/Bing: site:catalog.update.microsoft.com "uefi\res_{da6b5517-b8a0-4028-9b59-23c3ede398d1}"

    This bypasses the Catalog's broken indexer and points you directly to the page where that text exists.

    Workaround 2: Search by Update ID (If known)

    You mentioned you found the Update ID (1cc29a9a...) as proof. If you are tracking these updates via a script or WSUS feed, searching by the Update ID is the only method guaranteed to never break.

    Query: 1cc29a9a-ba3c-4d80-9a5e-d8348915d9e3

    Note: I realize you usually search the UEFI ID to find the Update ID, so this helps only for verification, not discovery.

    Workaround 3: Broaden the Search to "Model + Firmware"

    Since UEFI\RES IDs are unique to a specific Firmware Capsule, usually tied to a specific System SKU (SystemProductModel), you must revert to searching for the text description.

    Instead of searching for the ID, search for the System Model Name + "Firmware".

    Example: Surface Pro 7 Firmware or Dell Latitude 5420 System Firmware.

    Once the results appear, click the "Date" column header twice to sort by Newest. The latest firmware usually supersedes the specific GUID you were looking for anyway.

    I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to ACCEPT ANSWER. Should you have more questions, feel free to leave a message. Have a nice day!

    VPHAN

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.