This is not a tech support thread. I find it amusing that windows 10 has consistently been doing this for a few months now. This is on a laptop. Surely microsoft has statistics on this kind of stuff and this is not just happening to me, right? How has a problem like this gone unfixed for so long?
I think you underestimate the sheer number of unique hardware devices that are running Windows 10. The same models can be running different versions of the OS, with a variety of configurations, and various machine specific problems which could cause such an issue.
Now if every single person running your particular model of laptop is having the exact same problem, then perhaps they'd take notice and make a change to the driver repository. The likely issue is that the .inf file this driver uses is not properly identifying the driver or device and Windows keeps ranking the installed driver lower than the available one, so it tries installing it again and again.
This is not a tech support thread. I find it amusing that windows 10 has consistently been doing this for a few months now. This is on a laptop. Surely microsoft has statistics on this kind of stuff and this is not just happening to me, right? How has a problem like this gone unfixed for so long?
I think you underestimate the sheer number of unique hardware devices that are running Windows 10. The same models can be running different versions of the OS, with a variety of configurations, and various machine specific problems which could cause such an issue.
Now if every single person running your particular model of laptop is having the exact same problem, then perhaps they'd take notice and make a change to the driver repository. The likely issue is that the .inf file this driver uses is not properly identifying the driver or device and Windows keeps ranking the installed driver lower than the available one, so it tries installing it again and again.