I think what's happening is due to the fact that you've got OLD UNSUPPORTED OS'S and are attempting to download drivers for those.
For the sake of completeness, I am not downloading these drivers. I only used WSUS to release and control the updates. The clients download the drivers and updates directly from Microsoft.
Understanding that the updates that are synced to WSUS are following a boolean AND with [CATEGORY] AND [PRODUCT]
When you select the Drivers category, with no products, nothing will be downloaded because it would be [DRIVERS] AND [NULL]
When you select a 'Windows 10, 1903 and later' product, it would cause all updates from Microsoft that are [DRIVERS] AND [Windows 10, 1903 and later] to be synced to the metadata.
It could be that it is because I have activated Windows XP and Windows 7. It would be interesting whether one would get it that WSUS for Windows 7 and Windows XP does NOT synchronize drivers. But I don't think that's possible.
Currently I have solved the problem (again) by running the SQL script "RemoveDriversSQLScript.sql" from you (while WSUS was stopped). As a result, WSUS has "calmed down" (the large number of log entries were no longer generated) and the system is now stable. Let's hope that the resynchronization bug doesn't come back.
Also ensure your WsusContent folder is LOCAL to your server (not on a NAS) as that can drastically reduce performance.
See above. I don't have a local WsusContent folder (at least there's nothing in it).
I have expressed myself somewhat incorrectly. I don't want to distribute the driver updates with WSUS but with Windows Updates, the online service from Microsoft. All in all, security updates, feature updates, etc. should be controlled by my WSUS and drivers should be loaded directly from Microsoft.
I think you misunderstood me again: I have WSUS running at each site, of course. The clients also retrieve the necessary updates from this configured via group policy and install them. Only the drivers should be obtained directly from Microsoft and installed automatically. Is it possible to configure this somehow via group policy?
I'm afraid I have to reply to this thread again.
I just got back from Christmas vacation and the server was again running at full memory (32 GB RAM fully utilized) and CPU utilization (16 CPU cores under full load). The server was again writing thousands of these lines to the log every second:
2022-01-10 09:47:11.943 UTC Info w3wp.21 DriverUpdatesData.LoadDeployments Adding DriverInfo DistributionComputerHardwareIdSet and TargetComputerHardwareIdSet for hardwareId_revisionId=hdaudio\func_01&ven_10ec&dev_0269&subsys_15587aa12759212
Before the vacation I had the same effect. Since you said that this whole effect probably comes from Windows XP and Windows 7 in combination with drivers I really removed Windows 7 and Windows XP as a product three weeks ago.
To finish the problem three weeks ago I ran the script "RemoveDriversSQLScript.sql" again. After that I shrunk the database (it was about 40GB big). After that more drivers were synchronized and added without any problems.
Now, unfortunately, this effect occurs again.
What should I do now?
The whole theory that Windows XP and Windows 7 are to blame for this can no longer be the case.