I think what you're seeing is typically a detection mismatch rather than a true installation failure. In other words, Windows Update believes the HP USB driver is applicable, installs it successfully, but during the next scan the device still reports hardware information that matches the update, so it gets offered again.
Since this is a company-managed PC, I wouldn't recommend globally disabling driver updates because that could affect other users and devices. Instead, I'd first check Device Manager and compare the currently installed driver version with the version being offered by Windows Update. If the offered driver is not actually needed on this Lenovo device, the cleanest approach is usually to decline or hide that specific driver update through your update management solution (WSUS, Intune, Windows Update for Business policies, or other enterprise patch management tools), targeting only the affected device or device group.
I'd also review the Windows Update and Device Setup logs to confirm whether the driver is being installed and then superseded, or if the detection logic is simply re-offering it every scan cycle. In mixed-vendor environments, I've occasionally seen HP driver metadata offered to non-HP systems due to broad hardware matching rules, which can lead to exactly this kind of loop.
Identify the update's hardware ID applicability first, then block only that specific driver deployment if it has no business value for the affected ThinkPad. That keeps the fix scoped to the problematic device and avoids unintended impact on the rest of your fleet.