Hi,
Perhaps. But a 15 year old 950 vs 11 year old 950q suggests that if both models were working in WinXP through Win10 1909, but not with 2004 or higher, then MS screwed up something that has worked perfectly fine for a decade.
The first obvious hint is in 2004, where the drivers install, but the A/V stutters. Something new added/adjusted within Win10 2004 is causing this stutter, similar to this thread's issue.
LatencyMon shows wdf01000.sys is the main detected file leading to high latency in 2004, much bigger than in prior win versions. Something in Windows changed to cause this (Hauppauge had previously posted a suggestion to try and turn off Core Isolation as a fix - didn't fix the problem).
...
Then in 20H1, the drivers don't want to start up - obviously something within Windows changed for the worse.
This device cannot start. (Code 10)
{Operation Failed}
The requested operation was unsuccessful.
Device USB\VID_2040&PID_6513\4027657310 was not migrated due to partial or ambiguous match.
Last Device Instance Id: USB\VID_058F&PID_6366\058F63666433
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path: PCIROOT(0)#PCI(1C03)#PCI(0000)#USBROOT(0)#USB(3)
Migration Rank: 0xF000FFFFFFFF0023
Present: false
Status: 0xC0000719
...
The problem may have stemmed from a point earlier than 2004.
For example, https://answers.microsoft.com/en-us/windows/forum/all/windows-10-build-1903-hauppauge-wintv-quadhd-tuner/c1d9f0cd-d03c-4022-bc60-04dd9caf1971
This person had an AV device issue as early as 1903.
https://answers.microsoft.com/en-us/windows/forum/all/windows-10-pro-crashing-after-1909-update/99025902-7c19-44ed-ae8f-bb8755c3e595?page=1
This person's issue began with 1909.
And, it is not related to simply 1 Hauppauge device as other A/V devices appear to be negatively affected.
https://answers.microsoft.com/en-us/windows/forum/all/windows-2004-update-causing-major-problems-with/18605086-48df-415d-b6c5-6efcf7c91fcc
...
So, it is a problem that's wider than just 1 device since a number of users with different A/V devices have problems since 1903.
I'll try the 3rd party programs noted, but it doesn't address the issue directly of many different A/V devices not working with many other users after something changed within Windows.