One thing to keep in mind is that upgrading in-place from one Insider build to the next should mean that existing, installed (and working!) drivers get migrated.
Going from 10130 to 10158, 10159 and 10162 was relatively painless for me. With 10162, Windows did note that drivers didn't fully install for some DisplayLink devices, but that was fixed by using the Update Driver option from Device Manager, and scanning the C: Drive to pick up the drivers.
For me, the real test will come once the final RTM version of Windows is released, so I can try installing a clean install from an ISO. At that stage, I'm hoping there'll also be either a new release of the DisplayLink software, or at least backed up copies of the current drivers which I can use as a fallback.
Video performance is much better for me with 10162 (no major display refresh lags). The main problem I have is with audio not working fully (and not helped, as I'm using a Corsair headset with its own support issues). For example, the Sound applet shows connected sound devices, but right-clicking and choosing Test produces the error "Failed to play test tone.".
As others have commented, it's all still a work in progress - I think the fact we're using relatively stable beta software is a testament to Microsoft really getting their act together (and supported by first class OEMs and ISVs, like DisplayLink).
|