Sure if it fails completely it will, but it doesn’t catch everything. Here’s a related story I have:
At work we had a bunch of Lenovo X1 Carbons running windows that would have the usb-c ports die seemingly randomly on users which was a big problem since that’s also the charging port. There never seemed to be any similar root cause connecting the incidents and Lenovo’s support wasn’t any help. Our entire company is remote but luckily we had onsite support so for a while they would just come by and replace the whole motherboard each time.
Finally one day while scheduling a repair the support guy I was talking to just said, “Oh I’ve seen this before. It’s just a bad update and resetting the CMOS battery by putting a paper clip in this hidden hole fixes it.” We had the user try it out and the ports worked fine again. Apparently they had run some windows updates that failed silently and were causing the hardware issues.
From then on any time a user has had a hardware issue we can’t figure out we just have them try the reset and it has worked every time. This only happens probably 3-4 times a year but we only have less than 40 of these machines so not an insignificant amount.
You can watch rss feeds to follow all CVEs like Microsoft’s https://api.msrc.microsoft.com/update-guide/rss
NIST used to have an rss feed for CVEs but deprecated it recently. They still have other ways you can follow it though https://nvd.nist.gov/vuln/data-feeds
Or if you just want to follow CVEs for certain applications you can host/subscribe to something like https://www.opencve.io/welcome which allows you to filter CVEs from NIST’s National Vulnerability Database (NVD)