Hi:

   I don't know where to report the problem. but since RedHat is releasing virtio windows drivers via windows update, maybe someone will be interested about the inconsistency.

  we want to test the released driver and monthly windows updates before deploy. so we use wsus to import the driver via Microsoft update catalog. it works fine for windows server 2019. but with windows server 2022 and win10 21H2 LTSC,  some drivers use different updateID at microsoft update catalog and windows won't use the driver imported via microsoft update catalog.

for example, I use win10 21H2 LTSC to update via windows update toady. when update finished, I powershell command "Get-WindowsUpdateLog" to create log file "WindowsUpdate.log" at Desktop folder. then I search updated driver  like below:

2024/11/17 01:39:00.2270106 3908  3000  Agent             Title = Red Hat, Inc. - SCSIAdapter - 100.95.104.25300
2024/11/17 01:39:00.2270194 3908  3000  Agent             UpdateId = F81631B8-4765-4004-96C7-9D95B85B5644.1
2024/11/17 01:39:00.2270706 3908  3000  DownloadManager No locked revisions found for update F81631B8-4765-4004-96C7-9D95B85B5644.1 (SessionData = (null)); locking the user-specified revision.

the UpdateId "F81631B8-4765-4004-96C7-9D95B85B5644" can not be found at microsoft update catalog.

if you search the hardware id "PCI\VEN_1AF4&DEV_1042" via "https://www.catalog.update.microsoft.com/Search.aspx?q=PCI%5CVEN_1AF4%26DEV_1042" you can find there are drivers with the same version "100.95.104.25300" but different UpdateID. Win10 21H2 LTSC won't accept any of them.

for virtio storage and nic drivers via microsoft update catalog, windows server 2019 will install both. win10 21H2 LTSC will install only nic driver . windows 2022 will install only storage driver.

it looks like the fault of Microsoft. I don't know if RedHat can do some update and fix it.