Hello,
What you take using a Print Screen is not always what is displayed on the monitors but is what Windows is sending to the graphics driver to be displayed on the monitor.
Print Screen, despite its name, is before the graphics driver. Windows doesn't go and fetch what is actually displayed on the screen through the graphics card and drivers.
Because what you show in your screenshot shows the issue, then the issue is before DisplayLink driver as what is sent to DisplayLink driver is already missing the information.
I asked about the graphics hardware acceleration because Microsoft changed the graphics subsystem in the anniversary update. Even if it's called Windows 10, the new version is really different than the previous Windows 10. The same way Apple Mac OS changes every year but has been called 10 for a few years now.
You will see that now adapters using DisplayLink technology are shown in the Graphics Adapter section, not the USB Display Adapters. This is because we are now using the new OS feature in co-development with Microsoft for that last two years.
Because this is now part of the OS, we have to follow the rules if we want the driver signed and available through Windows Update.
In your particular case, I think it could be either because the primary graphics card driver doesn't handle this new OS feature fully yet, or if you only see this with Chrome, it could be that Chrome wants to be clever and addresses the card directly instead of using Windows API and in this case that won't work as USB displays NEVER did graphics acceleration... Even in previous versions of Windows (7 - 10 Threshold 2) this was always handled by the graphics card but we could redirect the call.
May I recommend you use Alt+Shift+I in Chrome to report an issue, including the screenshot and explaining you use Windows 10 Redstone with its new indirect display through USB?
I will create a bug report to Microsoft.
Kind regards,
Alban
|