Chrome Extensions invisible (Win10 Anniversary & 8.M1)

[box2k2]

Hi,

Anyone seen this one? All was well before the Anniversary update.

Using Chrome browser on the Displaylink Adapter certain extensions are invisble (uBlock, Pushbullet), while others work ok (Lastpass).



Moving Chrome to the laptop's adapter and all works well.



Issue was the same with 8.M0 driver too.

[box2k2]

Forgot to mentions dock is a Lenovo Dual DVI USB 3, so I think it's a DL-3900 based device.

[AlbanRampon]

Hello,
Unfortunately, I don't see any picture to look at.

Could you please use Print Screen and paste in Paint?
Do you see the extensions there or are they missing too?

Kind regards,
Alban

[box2k2]

Alban,

Sorry. Moved something and broke the links. Now fixed.

Laptop display is bottom right. Top two screens are DisplayLink.

[AlbanRampon]

Thanks,
From the way they look, I think I know the reply but can you confirm:
1- did you take the screenshots using Print Screen?
2- was the application visible in the Print Screen?
Does the behaviour change without Chrome graphics acceleration? (http://www.pcadvisor.co.uk/how-to/in...hrome-3605455/)
The reproduction looks very easy.
Alban

[box2k2]

1. Screenshot was using Print Screen (but it is an accurate representation of the issue)
2. Not sure I understand. The extension is not visible in the 1st screenshot (Chrome on DisplyLink), but is visible in the 2nd (Chrome on Laptop adpator). The extension works on both as I can click on where it should be and get the appropriate action, it's just not visible on the DisplayLink adapter.
3. Hardware acceleration is ON

Ok, so I've turned hardware acceleration off and the issue is resolved. Turn it back on and problem is back.

Question for you - Why is this a problem now, as it was OK prior to Windows Anniversary & DisplayLink v8 drivers?

[AlbanRampon]

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

[AlbanRampon]

Hello Box,
MS would like more information to proceed.
May you please rename the linked script to "Collect_Logs.CMD", and run as an administrator against the machine(s) that reproduce this issue. Then, please compress all files together and post so I can attach them to the bug to MS.
Kind regards,
Alban

[box2k2]

Originally Posted by AlbanRampon

Hello Box,
MS would like more information to proceed.
May you please rename the linked script to "Collect_Logs.CMD", and run as an administrator against the machine(s) that reproduce this issue. Then, please compress all files together and post so I can attach them to the bug to MS.
Kind regards,
Alban

Alban,

Sorry for not responding sooner. I'd considered this sufficiently resolved.

I run the script, but there's some form of error with dxdiag and directshow. I've managed to save the dxdiag info manually however and PMd you a link for the data requested.

Cheers,

Martin

[AlbanRampon]

Thank you Martin,

After 2 months without answer, the ticket to Microsoft was closed as blocked.

Kind regards,
Alban