Timeline for WindowsUpdateLog update-id based drivers unavailable from Microsoft Update Catalog
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 5, 2023 at 17:56 | comment | added | tmpuser | With the above example, there are only 3 results, and its easy to try them. But, the issue happens with many other drivers too. With some drivers, whose titles are very generic, there are like hundred plus results, and manually downloading the correct compatible driver could be very hard. | |
| Dec 5, 2023 at 17:52 | comment | added | tmpuser | Its only been a couple of days, since i freshly installed windows and did this. If it is pulled it must be many days ago. So, is it possible for pulled update guid to be displayed in windowsupdatelog ? If its assigned/superseded with a new GUID, how would i find the new GUID ? | |
| Dec 5, 2023 at 16:44 | comment | added | DrMoishe Pippik | Likely the exact update with GUID {96941A83-1B8F-430C-96A5-9522B8586A19} has been pulled (e.g., due to issues) or it has been assigned a new GUID. In fact , a web search for just that GUID found only your question! So search on the update ID, 31.0.12027.9001. | |
| Dec 4, 2023 at 23:36 | comment | added | tmpuser | updated question to better mention the issue. the exact updateid of the driver shown from windowsupdate log is not available in microsoft update catalog. | |
| Dec 2, 2023 at 23:24 | history | answered | DrMoishe Pippik | CC BY-SA 4.0 |