Thanks for your posting on Q&A.
I researched many articles and it is not recommended to deploy Drivers by WSUS. But it's theoretically possible. In order to analysis further, I would like to sharing the working principle of the WSUS first.
WSUS has a caching mechanism whereby the first-time update metadata is requested by any client WSUS will store it in memory. Further requests for the same update revision will retrieve the update metadata from memory instead of reading it from the database. Some of the metadata in the database is compressed, so not only must it be retrieved, it must be decompressed into memory, which is an expensive operation.
For large metadata packages and many simultaneous requests, it can take longer than ASP.NET’s default timeout of 110 seconds to retrieve all of the metadata the client needs. When the timeout is hit, ASP.NET disconnects the client and aborts the thread doing the metadata retrieval.
While the driver category in WSUS contains drivers from some of these vendors, we don't recommend that you use the category as an update mechanism for drivers because the category includes over 100,000 drivers and this can be problematic. The huge list of drivers is not manageable and the metadata alone could be enough to cause scan traffic to spike in your environment.
Hope the above will be helpful. Have a nice day.
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.