Intel video drivers are an example of how badly Msoft manages this. Each time Windoze updates to a new ver #, they will revert intel video drivers to a generation 5 versions past. Msoft wants to install/revert to version 27.x when 28-32.x versions have since been published by Intel. Msoft even recognizes the vers 31.x Intel driver in their optional driver update suggestion.
Intel's published fix is to update to their drivers, then leave Msoft driver store intact with the reverted version still in the driver store, and have the user suspend ALL Windows updates for 90 days (an unacceptable fix-not even a decent workaround). https://www.intel.com/content/www/us/en/support/articles/000087834/graphics.html#
Msoft community version fix is to install the latest intel drivers, without a clean install, and then use Group Policy to block updates for any device hardware ID that matches the older drivers (this works temporarily, until the next Windows version/patch update, then that particular Group Policy fails even though it remains enabled and the hardware IDs remain unmodified -- again, an unworkable kludge.) https://woshub.com/how-to-turn-off-automatic-driver-updates-in-windows-10/
If Msoft can allow GP to block hardware ID updates until the next win ver update, why can't that remain permanent until revoked or disabled by a new user-initiated GP change? Or if we delete old drivers from the driver store, why does Msoft Update continue to try and revert/re-install them to ancient drivers and THEN suggest in optional updates to update to an Intel version driver that is only 2+ versions out of date?
Even though I have only personally experienced this with my Intel drivers on my Intel branded PC's, I can see in the community that various manufacturer drivers are equally poorly handled by Windows update processes.