Ok, it looks as though the AMD chipset drivers are installed.
If the HP softpaqs are requiring .NET 3.5 - they're pretty old - your machine isn't that old
I'll look around HP and see if there isn't a newer SP - they're terrible at keeping the support site up to date, but so are many other mfrs.
I'm not familiar with USB replicator software drivers, so there's another reason to take it slow.
Do you know for a fact that you need those? Windows is very good now-a-days at supplying HW drivers - of course this is Win10 and there are exceptions. But as a general rule, since Windows 7, I only look for drivers that are either erred out in dev mgr or causing an issue.
You might try this - in Pgms & Feats press Turn Windows Features on or off - then select .NET 3.5 (SB the 1st one in the list). That might stop the errors from being thrown - not sure ... it might already be turned on.
If it were my machine, I think I'd hold off hoping that a newer USB replicator set is available or uninstall those SPs - Dev mgr didn't flag them as errors did it?
Nope, don't need the evt logs for 420 & 430 - the device is no longer unknown - right? Finding that driver wasn't that hard, I searched for the hardware Id you provided, and then looked on the device support page - nothing! - but searching HP gave me the answer so I could give you the answer
I got a kick out out the title here ya go Bill
Sooooo , let's return to the optical drive ... I think that's where we started.
Launch an elevated Command prompt and type the following commands
Dism /Online /Cleanup-Image /RestoreHealthNote: There's a space before each slash / in the command line
DISM uses Windows Update, so it's helpful be connected, otherwise I think it just uses the local WU information already on your machine, again ... not certain about that.
SFC runs locally on your machine and puts system files in the correct location if needed. (SFC might be redundant - not sure if DISM updates only the store or also updates any other reference location - technically they should be the same)
If either reported any errors, please let members know. They'll tell you when they finish.
The log is C:\Windows\Logs\CBS\CBS.log and it might be useful to see - but only if there are errors.