Fix some applications not running on laptop GPU
Hi since the Windows 10 Anniversary update games or utilities i have in Steam valve dont seem to use the GPU on my laptop but instead use intel graphic the laptop i have is a Lenovo Y50
Marking completed with Windows 10 v1903 with KB4512941 (OS Build 18362.329) or newer (end of August 2019 patch).
Thank you all for confirming and your patience.
Should anyone see something unusual, please create a support ticket for individual investigation.
Tara Campbell commented
I just want to add that I'm having the exact issue Rick posted about - Acer Aspire VX 15 gaming laptop. It has to be unplugged from the dock completely, cannot just bypass the HDMI.
Another laptop (MSI GS63) is still working with the HDMI bypass method.
Adding my experience similar to those that have updated to 1903. I cannot get any games to work while plugged into a DisplayLink port replicator (HP3005) through the USB and an HDMI cable from the monitor connected directly to the laptop. I updated to the newest Nvidia Drivers, and the newest DisplayLink drivers. The GPU doesn't run the games, they crash right as they load (similar to everyone's experience below). I tried the Duplicate Screen work-around as noted by "Gil" with Windows+P, but it does not work, either.
Before this upgrade I could use the Nvidia GPU regardless if the port replicator was plugged in or not, I just had to connect the monitor via HDMI to the laptop directly. However, now even that doesn't work.
The only way any games work is if I use the laptop display without plugging any other display into it.
Same problem here, The applications crash and the control panel states I'm not connected to Nvidia hardware.
I can also confirm that games and the Nvidia control panel work when the screen mode in windows is set to duplicate and the games run when I switch to the second screen only but the Nvidia control panel reverts to stating I'm not connected Nvidia HW.
Im on a 1050 using the latest Nvidia drivers and Displaylink software
I solved the problem by choosing 'duplicate' in the Windows screen selection. Windows + P
After you have launched your GPU intensive app, you can switch back to '2nd screen only'
Well I was hoping that the release of 19H1 would solve this problem but I'd like to add my name to the list. Pre 19H1, my games that were designated to run in High Performance (NVIDIA) would simply run in Integrated in a degraded state. Now those applications will not run at all, they crash instantly. I'm not sure if this is an NVIDIA issue, Windows issue, or Displaylink issue. It appears that the GPU selection is being preserved but the app is crashing. I have tried this with multiple games.
I also updated to Windows 1903 today and my CAD software (Autodesk Fusion 360) will not even launch if I have both monitors plugged into the display link hub. It will launch if I right click and select launch with integrated graphics, but then the CAD is gimped. It works just fine with one monitor in the hub and the other directly connected to the laptop. This is all the exact same behavior as before the 1903 update.
Latest Nvidia drivers, latest displaylink drivers. Any ideas?
So after today’s update on Windows 1903, games directly crash after start. I’m running on latest nvidia drivers and displaylink version 9.1 M2. The game is listed just for a sec in the nvidia gpu activity window and then does crash...
Will the solution to this problem also be available for Windows 10 LTSC 2019?
LTSC 2019 ist based on Windows 10 1809.
Thank you in advance
Eamonn, I would need to know what your testing it with and how you change the GPU affinity. The change was made a while back so it would be in any current 19H1 ring, slow and fast as we're so close to release.
The change was validated with Dolphin CAD/CAM, because it is known to use Windows APIs correctly. Before, when an indirect display was primary, it would use the Intel iGPU even when the Windows UI is selecting the external GPU, leading to slower computation.
Now, the application renders using the secondary GPU regardless of which display is declared as "main display" when the high end GPU is selected in the Windows UI.
The laptop manufacturer and Microsoft both closed the issue as fixed.
There was no code change needed from us to address that issue.
(I am simplifying a bit as there are 2 activities here computing/composing and displaying, both can be done by different resources)
[Deleted User] commented
Is there a release or planned release date for DisplayLink drivers supporting this change? Waiting for the final build of 19H1?
This massively impacts my ability to use my 4k monitor, as all the load gets put on the CPU, and the frame rate of windows on that monitor slow to ~ 30. So I'd like it ASAP.
Alban, I believe I am running 19H1 in the insider fast ring and the issue persists. Is this update available for testing yet?
It seem like this problem should be resolved by now.... any news?
I know that this is an old issue but can anyone from DisplayLink update us on working with Microsoft to resolve this? I saw a bugfix for 19H1 that says "We fixed an issue from the previous flight that caused consistent black screens when using Remote Desktop, DisplayLink, or Miracast if you are on an AMD or Nvidia driver." Does this mean the issue will be resolved with 19H1?
I need help getting a targus ACP70USZ to work with ubuntu. I cannot seem to download the correct drivers to get the laptop to see the other displays.
Hello Team, I am using a Gigabyte Aero15 7700 with a 1060 and Win10 connected to a Targus dock APC70USZ with a USB-C to the dock's USB-B (I think it is USB-B). Whenever docked the GPU is inactive. Is there a work around yet for the issue? Only integrated graphics are being used and I cannot run anything demanding in graphics resources without a headache due to poor performance. I have went as far as telling the Nvidia control panel to use the 1060 with that application.
I have a Lenovo Thinkpad E450 laptop with 2 GPUs inside: Intel HD Graphics 5500 and AMD Radeon R7 M260. My OS is Windows 10 Pro (version 1803, build 17134.471).
When I use Wavlink docking station with DisplayLink the stronger Radeon GPU is ignored, only the Intel GPU is used which is too weak for running games.
There is no option to disable Intel GPU in BIOS.
Is there a solution to use the Radeon GPU?
@Daniel, you need to create a ticket with the logs (https://support.displaylink.com/knowledgebase/articles/533818-how-can-i-report-windows-issues-to-displaylink). Without data you can only get generic information. GPU works in any case so that message is, at best, misleading. Do you have a support case with DaVinci, if so, when you create your ticket by email with us, give contact details so we can contact DaVinci to understand what they rely on.
I have an Alienware R3 13" laptop, which has a Nvidia GTX 1060 GPU. When I connect it to my DisplayLink adapters and launch DaVinci Resolve 14, I get an error that the GPU won't work.
Mr. Alban Rampon, I'm from Brazil and unfortunately buyed a Dock Station 6000 from Dell in Brazil three weeks ago, you've said that this is a bug in Windows Operational System, and you CANNOT solve this for TWO YEARS! So, WHY DO YOU CONTINUE SELL YOUR PRODUCTS for Windows costumers aroud the world without this WARNING??? JUST STOP SELL or FIX IT!
Now, I cannot use my dedicated graphics card anymore, so I've a D6000 paper weight very expensive for Brazil reality!
I don't understand the unsupported defamatory accusations from Elrond when transparency has been used from the start.
Windows uses the POST graphics card. Windows cannot select the POST card. POST is before Windows boots, that's at BIOS level. The OS is getting changed not to always use the POST GPU, and, when the change is done, an indirect display driver will be able to select GPU affinity.
The GPU setting in the OS is for application rendering rather than display adapters and includes a bug.
Currently, the work around is to use a direct display (ie. native laptop display) as primary or main display. That means keeping the lid open, for instance. Daniel confirmed that earlier in the comments.
Unfortunately, very few people took the time to report this issue through the Windows 10 Feedback Hub so we had to wait until a computer manufacturer escalated this so it got prioritised.