Info
 

Perhaps it would be better to ask for the contents of the resulting zip file from the Support Tool? Anyway, here is what I got within reason.


1. Windows 10 Build Number
Microsoft Surface Book
OS: Microsoft Windows 10 Pro (x64-based PC), No Service Pack, English
OS Build: 10.0.14393.0 (Debug = False)
OS Build Label: 14393.rs1_release.161220-1747

2. Enumerate each display, its resolution and if it is connected to the graphics card or a USB adapter:

Both monitors are 1920 x 1200 and using USB adapter to Surface Book.
VS24A Manufacturer: ACI ProductCode: 24D1 Serial: F9LMQS066306 Built: 38/2015
ASUS VW266H Manufacturer: ACI ProductCode: 26A4 Serial: 96LMTF180980 Built: 27/2009

3. The CPU ***full*** name including the numbers after iX (available from System_Details.txt as well). Generation is more important to understand the architecture rather than if it is an i3 or i7.

CPU: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz
Number of Cores: 4
Might be Skylake?


4. The GPU details (available from System_Details.txt as well).

Graphics: NVIDIA GeForce GPU (NVIDIA)
Graphics Driver: 21.21.13.6961 Dated 2016/10/20
Graphics: Intel(R) HD Graphics 520 (Intel Corporation)
Graphics Driver: 20.19.15.4463 Dated 2016/07/06
Graphics: DisplayLink USB Device (DisplayLink)
Graphics Driver: 8.1.843.0 Dated 2016/12/01
Graphics: DisplayLink USB Device (DisplayLink)
Graphics Driver: 8.1.843.0 Dated 2016/12/01
WEI Base Score is 6.4, CPU 7.5, RAM 8.2, GPU 6.4, Gaming 9.9, Disk 8.8

5. What you include in your CPU usage (which processes: overall, WUDF, DWM...). Note: I really need WUDF more than the rest as DWM is a Windows process).
Not sure precisely what you mean - but the top 5 when at-rest are:
WDF
Task Mgr
Windows Explorer
DWM
Chrome

6. The value of CPU being used.
Not sure what you mean here - typical CPU usage details are below.

7. What happens on ALL indirect displays (indirect = through USB). If you have Task Manager on an indirect display, then it is NOT idling as content changes!!! This is really one of the most important point. Here are some examples:

7a. Content fully static: nothing changes at all, and I mean nothing, not the clock, not the mouse pointer.
Ehhh - how do you want me to capture CPU % without anything open? Run a CPU logger? Is that of any value? I suspect WDF would be less than 2% and total CPU is around 8%

7b. Some little area changes: like for instance you only have some numbers on the clock or the numbers in Task Manager.
WDF anywhere from .5% - 2%
Total CPU is around 8%

7c. Only the mouse pointer across indirect displays. (if you do this, please do NOT use the mouse trail accessibility feature or this is the same use case as 7b).
WDF 28% - 30%
Total CPU is about 60% as other extraneous processes start to take up a little more CPU when I move the mouse.

7d. Moving a window. Indicate an idea of the size of the window... I mean moving a 10x10 pixels windows is obviously fundamentally different to moving a 4kx4k one.
A full-size-ish window (not maximized but filling a 1920 x 1200 display)
WDF – 30% - 38%

7e. Playing video on VLC
Video maximized on one screen.
WDF about 30%
VLC about 15%
DWM about 5%

7f. Playing video on a browser (and the value is constant across browsers). Our driver CANNOT differentiate which browser is playing.

With YouTube maximized on one of the screens (task manager on the other)
Total CPU = 100%
WDF 38%
Chrome 28%
Chrome 22%
DWM 3%
Task manager 2%



7g. Game, full screen or windowed? Games do NOT use the same as video playback.
Haven’t tried playing games (I don’t actually have any installed), I’m sure it would be catastrophic.

8. Which version of DisplayLink driver you are running as, like Windows builds, they don't all have the same features. (available from System_Details.txt as well).

DisplayLink Version: 8.1.843.0
DisplayLink Installer Source: Normal or WU installed
DisplayLink Audio Version: 1.54.0.0 (DisplayLink USB Audio 2.0 Class Driver)
DisplayLink Ethernet Version: 2.34.17.0 (DisplayLink USB CDC NCM Driver)
No DL USB I/O drivers found.s
DisplayLink RS Version:8.1.843.0 (DisplayLink Core Software v8.1.843.0)

This is my work setup below. I take the laptop home where I have the same dock, but different monitor setup. There I have one monitor connected via the laptops built in miniDP port to DP on the monitor, then two others via HDMI on the dock (laptop lid is closed, so screen is not in use). Incidentally I have to use the miniDP on the laptop as the DP port on the dock refuses to work. The monitor just flickers between no signal and powered off (another non-displaylink dock with a different laptop works fine with DP).

Happy to try beta/alpha builds. I work in software and beta test for other companies, so know how to provide decent feedback etc.

1. Windows 10 Build Number
Computer: Dell Inc. - XPS 13 9343 4Q5GT32
OS: Microsoft Windows 10 Pro (x64-based PC), No Service Pack, English
OS Build: 10.0.14393.0 (Debug = False)
OS Build Label: 14393.rs1_release.161220-1747

2. Enumerate each display, its resolution and if it is connected to the graphics card or a USB adapter
Primary Resolution: 1920x1080x32
Desktop Size: 5760x1080
Number of Monitors Connected: 3
Monitors Connected:
Manufacturer: SHP ProductCode: 1420 Serial: 0 Built: 2/2015
S240HL Manufacturer: ACR ProductCode: 0289 Serial: LU5EE0018536 Built: 46/2015
S240HL Manufacturer: ACR ProductCode: 0289 Serial: LU5EE0018536 Built: 46/2015
In english: one laptop screen and two Acer S240HL 1080p screens both connected via Dell D3100 dock on HDMI.

3. The CPU ***full*** name
Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz

4. The GPU details
Intel(R) HD Graphics 5500

5. What you include in your CPU usage
With no activity on the indirect displays, WDF is < 1% (average of 0.5%). Activity causes CPU to increase. I can get it to 100% with a youtube video playing on each connected display,with WDUF competing with Chrome for CPU.

6. The value of CPU being used.
By WDF? Anywhere from 0.5% to 30% depending on activity

7. What happens on ALL indirect display
7a. Content fully static
WDF - 0.5%

7b. Some little area changes:
WDF - averages around 1-2%

7c. Only the mouse pointer across indirect displays
WDF - 1.5% on build in screen, 20% on indirect displays

7d. Moving a window
Dragging full 1080p Outlook window around
WDF - 1% on build in screen, 25% on indirect displays

7e. Playing video on VLC
Don't have VLC

7f. Playing video on a browser
WDF - 2% if browser is on built in screen - 30% if either of the connected displays

7g. Game, full screen or windowed?
I don't play games - it's a work PC

8. Which version of DisplayLink driver you are running as
DisplayLink Version: 8.1.843.0
DisplayLink Installer Source: Normal or WU installed
DisplayLink Audio Version: 1.54.0.0 (DisplayLink USB Audio 2.0 Class Driver)
DisplayLink Ethernet Version: 2.34.17.0 (DisplayLink USB CDC NCM Driver)
No DL USB I/O drivers found.
DisplayLink RS Version:8.1.843.0 (DisplayLink Core Software v8.1.843.0)

I had posted a ton of details on here yesterday and now it is deleted. Why? That took a lot of time and research to help you all out and hopefully fix the problem? I found that the CPU being eaten up was due to the driver calling a directx 11 DLL as well as provided the numbered list requested. Did I violate some kind of TOS?

Nothing is getting deleted. Like many, many but many forums, posts with attachments are moderated. The number of spam/porn/fake medicine messages that don't invade your inbox because of this measure is relatively high.

So why was it removed? It wasn't spam, it was all technical detail on this problem.

You removed it from public view pending review when you added attachments.

Thanks for clearing it up, I had thought I did something wrong, and only want to help.

This issue makes using the dock for Skype meetings or Webex impossible. I have to log into my VDI through my windows Phone and Continuum dock to join any meetings that have presentations or undock my laptop.

Workaround until driver update
 

I have been fighting with my workstation for several weeks with resource issues. Locking up, running out of memory, cpu running way with resources, fan that sounds like a jet engine, etc...

After a lot of research I stumbled upon this post as I was looking at Windows processes and Endpoint protection as the cause of the issues. However I have now unplugged my dock, uninstalled the current DisplayLink driver issued on December 18 and rebooted my machine. On reboot I inserted the dock USB into a different port and let it install the driver through Windows. I am happy to report that my machine has returned back to normal...so far...

Running Windows 10 Anniversary. After letting windows install the driver the display adapter appears as "USB3.0 Dual Video Dock" Driver Provider: DisplayLink Driver Date: 8/17/2016 Driver Version: 8.0.762.0 Along with the display adapter I have "USB Giga-Ethernet" Driver Provider: DisplayLink Driver Date: 5/20/2016 Driver Version: 8.0.403.0

Fingers are crossed but it appears to have solved my issue!

Hello,

Would you please be able to share your CPU+GPU details?
Also what kind of resolution are you external displays?
If I can understand the CPU issue, I don't get the high memory usage...



As a general update, I have created support tickets with details from the different posters here in preparation to share a development build to test. However, during tests, an unrelated issue was found so I have not yet shared anything as I am not satisfied with the quality.


Kind regards,
Alban

Nice to see you are having some success. I just went through the steps you outlined here, and my problem persists. Just moving the mouse on the screen causes WUDFHost to still jump from 4-25% CPU.

It took a while for windows to recognize the display adapters, but my keyboard and mouse it had no issue with.

1. OS Build Info

OS Build: 10.0.14393.0 (Debug = False)
OS Build Label: 14393.rs1_release.161220-1747

2. Monitors Connected:

SMS24A650 Manufacturer: SAM ProductCode: 082A Serial: HVRB900381 Built: 38/2011
SMS24A650 Manufacturer: SAM ProductCode: 082A Serial: HVRB900369 Built: 38/2011

3. CPU

CPU: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz

4. GPU Details

Graphics: Intel(R) HD Graphics 520 (Intel Corporation)
Graphics Driver: 21.20.16.4534 Dated 2016/10/07
Graphics: DisplayLink USB Device (DisplayLink)
Graphics Driver: 8.1.843.0 Dated 2016/12/01
Graphics: DisplayLink USB Device (DisplayLink)
Graphics Driver: 8.1.843.0 Dated 2016/12/01
Graphics: DisplayLink USB Device (DisplayLink)
Graphics Driver: 8.1.843.0 Dated 2016/12/01
Graphics: DisplayLink USB Device (DisplayLink)
Graphics Driver: 8.1.843.0 Dated 2016/12/01

The Intel internal graphics is used to take the load off the CPU when streaming through Open Broadcast Studio.

5. CPU Usages
WUDF mainly 5-35%

6. Total CPU Usage
20%-100%

7. Analysis

7a: Content fully static: WUDF idles at around 0%-2% CPU usage.

7b: Same as 7a

7c: When just moving the mouse around the displays WUDF uses around 6-12% of the CPU.

7d: When moving a window around WUDF usage goes up to around 20-28% of the CPU.

7e: Not installed

7f: Full screen video on:
Opera = 15-22%
Edge = 14- 20%


7g: No games to test.

8. Display Link Driver Installed

DisplayLink Graphics Driver (8.1.848.0) on 2017/01/10 Status is Installed

Also happens with multiple documents in Word - 6 external screens
 

1. Windows 10 Build Number
OS: Microsoft Windows 10 Home (x64-based PC), No Service Pack, English
OS Build: 10.0.14393.0 (Debug = False)
OS Build Label: 14393.rs1_release.161220-1747

2. Enumerate each display, its resolution and if it is connected to the graphics card or a USB adapter:

Manufacturer: AUO ProductCode: 139E Serial: 0 Built: 1/2009 - 1600x900 - AMD Radeon 6600M
ACER V243HQ Manufacturer: ACR ProductCode: 00B0 Serial: LG8080074221 Built: 20/2011 -1920x1080 -USB\\VID_17E9&PID_0360
ACER V243HQ Manufacturer: ACR ProductCode: 00B0 Serial: LG8080074221 Built: 20/2011 -1920x1080 -USB\\VID_17E9&PID_0360
ACER V243HQ Manufacturer: ACR ProductCode: 00B0 Serial: LG8080074221 Built: 19/2011 -1920x1080 -USB\\VID_17E9&PID_0360
ACER V243HQ Manufacturer: ACR ProductCode: 00B0 Serial: LG8080074221 Built: 20/2011 -1920x1080 -USB\\VID_17E9&PID_0360
ACER V243HQ Manufacturer: ACR ProductCode: 00B0 Serial: LG8080074221 Built: 20/2011 -1920x1080 -USB\\VID_17E9&PID_0360
ACER V243HQ Manufacturer: ACR ProductCode: 00B0 Serial: LG8080074221 Built: 20/2011 -1920x1080 -USB\\VID_17E9&PID_0360

3. The CPU ***full*** name including the numbers after iX (available from System_Details.txt as well). Generation is more important to understand the architecture rather than if it is an i3 or i7.

CPU: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz
Number of Cores: 8


4. The GPU details (available from System_Details.txt as well).

Graphics: AMD Radeon 6600M and 6700M Series (Advanced Micro Devices, Inc.)
Graphics Driver: 15.201.1151.1008 Dated 2015/11/04
Graphics: DisplayLink USB Device (DisplayLink)
Graphics Driver: 8.1.843.0 Dated 2016/12/01
Graphics: DisplayLink USB Device (DisplayLink)
Graphics Driver: 8.1.843.0 Dated 2016/12/01
Graphics: DisplayLink USB Device (DisplayLink)
Graphics Driver: 8.1.843.0 Dated 2016/12/01
Graphics: DisplayLink USB Device (DisplayLink)
Graphics Driver: 8.1.843.0 Dated 2016/12/01
Graphics: DisplayLink USB Device (DisplayLink)
Graphics Driver: 8.1.843.0 Dated 2016/12/01
Graphics: DisplayLink USB Device (DisplayLink)
Graphics Driver: 8.1.843.0 Dated 2016/12/01
WEI Base Score is 4.5, CPU 7.4, RAM 7.4, GPU 4.5, Gaming 6.1, Disk 7.9


5. What you include in your CPU usage (which processes: overall, WUDF, DWM...). Note: I really need WUDF more than the rest as DWM is a Windows process).

6. The value of CPU being used.
Total CPU
Total % but when I look at the resource monitor it is spread across all 8 cores
7. What happens on ALL indirect displays (indirect = through USB). If you have Task Manager on an indirect display, then it is NOT idling as content changes!!! This is really one of the most important point. Here are some examples:
7a. Content fully static: nothing changes at all, and I mean nothing, not the clock, not the mouse pointer.
With 3 x USB\\VID_17E9&PID_0360 connected 5%
With 6 x USB\\VID_17E9&PID_0360 connected fluctuates 12%
7b. Some little area changes: like for instance you only have some numbers on the clock or the numbers in Task Manager.
7c. Only the mouse pointer across indirect displays. (if you do this, please do NOT use the mouse trail accessibility feature or this is the same use case as 7b).
With 3 x USB\\VID_17E9&PID_0360 connected fluctuates from 30-50% with 6 Word documents open on these screens
With 6 x USB\\VID_17E9&PID_0360 connected fluctuates from 30-70% with 6 Word documents open on these screens

7d. Moving a window. Indicate an idea of the size of the window... I mean moving a 10x10 pixels windows is obviously fundamentally different to moving a 4kx4k one.
With 3 x USB\\VID_17E9&PID_0360 connected fluctuates from 30-50% with 6 Word documents open on these screens
With 6 x USB\\VID_17E9&PID_0360 connected fluctuates from 30-100% with 6 Word documents open on these screens, mouse and keyboard stutter and Windows starts reporting USB device errors

WUDF is always the top of usage list. Screens are landscape with each document occupying have of one screen. ie 960x1080
7e. Playing video on VLC
Not tested.
7f. Playing video on a browser (and the value is constant across browsers). Our driver CANNOT differentiate which browser is playing.
Not Tested.
7g. Game, full screen or windowed? Games do NOT use the same as video playback.
No games.
8. Which version of DisplayLink driver you are running as, like Windows builds, they don't all have the same features. (available from System_Details.txt as well).
Graphics Driver: 8.1.843.0 Dated 2016/12/01

With 6 x USB\\VID_17E9&PID_0360 connected and the CPU above peaking across all threads when we resize, edit and copy/paste the CPU temp rises to over 90 degrees C and the CPU throttles and the documents drop back to the laptop. It is as though Windows has reset the USB port/s.

Current workaround is to use only 3 of the 6 x USB\\VID_17E9&PID_0360 until patch available. The 6 x USB\\VID_17E9&PID_0360 have worked well for years under Windows 7 and then Windows 10 and started misbehaving with the Windows Anniversary edition.

Possibly found a temporay workaround/fix for lagging
 

Hi all,

I'm following this thread since the lag & high load issues started with the Win 10 Anniversary Update and still waiting for the solution.

I have the same mouse lag (= screen update lag) that has been reported by others, and it especially appears when I launch my eclipse development environment or watch youtube videos etc. on the Displaylink screen.

Now the lag fix for me was the processes priority:

In the task manager, I go to services and I always see a single WUDFHost.exe, which behaves completely normal and has a process priority set to HIGH by default it seems.

As soon as the Displaylink monitor is attached I have a second WUDFHost.exe process in the task manager, so 2 in total.
This second "new" one always uses a lot more RAM than the first (40 - 50 MB) and causes high CPU load depending on the Displaylink screen changes.
Now I changed the proccess priority for this one from default NORMAL to HIGH and the mouse lag (screen update lag) was gone completely.

Note this does not lower the CPU load or something, but there is simply no screen lag any longer.
I hope this works for someone else.

Keep in mind that the task manager keeps this information only for the current session, the priority setting is back to normal at the next start of windows. There are some tools and command line scripts or batch jobs to trigger this for each startup.

#UPDATE#
Setup: Dell XPS 13 9350 + FHD Monitor (USB Displaylink) + FHD Monitor (USB C/HDMI via DA200)

Best Regards

This dramatically reduced my input and system lag. It is not completely gone, but is by far not as noticeable as before.

Dell XPS13 and D3100 (2 x 2560x1440 screens)

Hi Domdus, and all,

Because of the delay in getting the development build out, I am changing strategy a bit.
I should have an 8.2 Alpha available around Friday and I'll create a dedicated forum board for it as it includes more than this.

Some priority changes has been done in the driver. There are other priority changes that can be done but they are not straight forward: the OS scheduler will penalise you with lower priority than low if you claim highest all the time... Unless, like some game, you decide to decrease the "responsiveness" index but we're not ready to do that.

The alpha has other changes around smoothness. We've been running them this week over dual-4K display setups.
As soon as the 8.2 Alpha is available, I will add a link to the thread about it.

Kind regards,
Alban

Good afternoon everyone,

Here are links to the 8.2 Beta forum I created for the feedback on that version.

8.2 Beta 1 - 8.2.1336 17th February 2017 to get the file with its limitations.
Please create a new thread in 8.2 Beta for Windows with your feedback about that version.

The focus for that version has been addressing performance first. There is also CPU reduction for some tasks. The reduction will depend on the application being used. For instance, Windows Photo Viewer sends full screen updates even when displaying a static photo... Improving the behaviour with non-optimal applications will come later.

I'd like to attract your attention to the known bugs listed under the limitations.

Have a nice weekend,
Alban

Fixed for me
 

The service was taking an average of 20% cpu for me until I disabled it then rebooted and then enabled it again as manual. I noticed that the original startup mode was manual (triggered) so I suppose it was constantly being triggered. Note that your displaylink monitors will not work after the disable reboot but set the service to manual and reboot again and you should be good to go.

I suppose this is more of a workaround but I have not seen any negative consequences yet so ignorance is bliss.

High load is anything that spins up the CPU fan. But I was relating behaviour that seems wrong to me. Your forum does not allow me easily include a screenshot, so I just paste some of the events from procmon below. Procmon keeps rolling with events like these,
about 5 loops per second.

10:31:07.7011935 WUDFHost.exe 13160 RegOpenKey HKLM SUCCESS Desired Access: Maximum Allowed, Granted Access: Read
10:31:07.7012609 WUDFHost.exe 13160 RegQueryKey HKLM SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7013444 WUDFHost.exe 13160 RegOpenKey HKLM\Software SUCCESS Desired Access: Read
10:31:07.7014379 WUDFHost.exe 13160 RegCloseKey HKLM SUCCESS
10:31:07.7015207 WUDFHost.exe 13160 RegQueryKey HKLM\SOFTWARE SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7016392 WUDFHost.exe 13160 RegOpenKey HKLM\SOFTWARE\DisplayLink SUCCESS Desired Access: Read
10:31:07.7017298 WUDFHost.exe 13160 RegCloseKey HKLM\SOFTWARE SUCCESS
10:31:07.7018942 WUDFHost.exe 13160 RegQueryKey HKLM\SOFTWARE\DisplayLink SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7020779 WUDFHost.exe 13160 RegOpenKey HKLM\SOFTWARE\DisplayLink\NivoManager NAME NOT FOUND Desired Access: Read
10:31:07.7021925 WUDFHost.exe 13160 RegCloseKey HKLM\SOFTWARE\DisplayLink SUCCESS
10:31:07.7026075 WUDFHost.exe 13160 RegOpenKey HKU\S-1-5-19 SUCCESS Desired Access: Read/Write
10:31:07.7027246 WUDFHost.exe 13160 RegQueryKey HKU\S-1-5-19 SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7029168 WUDFHost.exe 13160 RegOpenKey HKU\S-1-5-19\Software SUCCESS Desired Access: Read
10:31:07.7029901 WUDFHost.exe 13160 RegCloseKey HKU\S-1-5-19 SUCCESS
10:31:07.7030455 WUDFHost.exe 13160 RegQueryKey HKU\S-1-5-19\SOFTWARE SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7031177 WUDFHost.exe 13160 RegOpenKey HKU\S-1-5-19\SOFTWARE\DisplayLink SUCCESS Desired Access: Read
10:31:07.7032101 WUDFHost.exe 13160 RegCloseKey HKU\S-1-5-19\SOFTWARE SUCCESS
10:31:07.7032718 WUDFHost.exe 13160 RegQueryKey HKU\S-1-5-19\SOFTWARE\DisplayLink SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7035197 WUDFHost.exe 13160 RegOpenKey HKU\S-1-5-19\SOFTWARE\DisplayLink\NivoManager NAME NOT FOUND Desired Access: Read
10:31:07.7036576 WUDFHost.exe 13160 RegCloseKey HKU\S-1-5-19\SOFTWARE\DisplayLink SUCCESS
10:31:07.7038434 WUDFHost.exe 13160 RegOpenKey HKLM SUCCESS Desired Access: Maximum Allowed, Granted Access: Read
10:31:07.7041241 WUDFHost.exe 13160 RegQueryKey HKLM SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7045469 WUDFHost.exe 13160 RegOpenKey HKLM\Software SUCCESS Desired Access: Read
10:31:07.7047906 WUDFHost.exe 13160 RegCloseKey HKLM SUCCESS
10:31:07.7049175 WUDFHost.exe 13160 RegQueryKey HKLM\SOFTWARE SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7051393 WUDFHost.exe 13160 RegOpenKey HKLM\SOFTWARE\DisplayLink SUCCESS Desired Access: Read
10:31:07.7052162 WUDFHost.exe 13160 RegCloseKey HKLM\SOFTWARE SUCCESS
10:31:07.7052990 WUDFHost.exe 13160 RegQueryKey HKLM\SOFTWARE\DisplayLink SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7055088 WUDFHost.exe 13160 RegOpenKey HKLM\SOFTWARE\DisplayLink\NivoManager NAME NOT FOUND Desired Access: Read
10:31:07.7056492 WUDFHost.exe 13160 RegCloseKey HKLM\SOFTWARE\DisplayLink SUCCESS
10:31:07.7058230 WUDFHost.exe 13160 RegOpenKey HKU\S-1-5-19 SUCCESS Desired Access: Read/Write
10:31:07.7059278 WUDFHost.exe 13160 RegQueryKey HKU\S-1-5-19 SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7060480 WUDFHost.exe 13160 RegOpenKey HKU\S-1-5-19\Software SUCCESS Desired Access: Read
10:31:07.7062546 WUDFHost.exe 13160 RegCloseKey HKU\S-1-5-19 SUCCESS
10:31:07.7063505 WUDFHost.exe 13160 RegQueryKey HKU\S-1-5-19\SOFTWARE SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7065572 WUDFHost.exe 13160 RegOpenKey HKU\S-1-5-19\SOFTWARE\DisplayLink SUCCESS Desired Access: Read
10:31:07.7067363 WUDFHost.exe 13160 RegCloseKey HKU\S-1-5-19\SOFTWARE SUCCESS
10:31:07.7068287 WUDFHost.exe 13160 RegQueryKey HKU\S-1-5-19\SOFTWARE\DisplayLink SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7073661 WUDFHost.exe 13160 RegOpenKey HKU\S-1-5-19\SOFTWARE\DisplayLink\NivoManager NAME NOT FOUND Desired Access: Read
10:31:07.7075117 WUDFHost.exe 13160 RegCloseKey HKU\S-1-5-19\SOFTWARE\DisplayLink SUCCESS

I installed DisplayLink 8.2 Beta For Windows 8.2 Beta 1.exe, and WUDFHost.exe is still misbehaving.

Experiencing the same issues.
 

High Memory usage through the DisplayLink Driver. Has there been a fix or update to this issue yet? Thanks!

Same issue on a XPS13 with Dell D3100...do someone need some debuging stuff?!

Greetings, Dirk

8.2 Beta !2! with big change
 

Hi,

I tested 8.2 Beta 1 - 8.2.1336 for last weeks which had a slightly better performance than versions before. I still applied the fix at the processes priority for WUDFHost.exe, I mentioned earlier here.

Now I found and tried out the 8.2 Beta 2 and it resolves my issues completely.

In detail, it seems there is only one instance of the WUDFHost.exe in the list of processes (not many) and it does not show any high load behavior - no matter what I do in the display link screen.
Lagging is gone is well.

Best Regards

Also happens with Dell D1000 Dock on Dell Systems
 

We are seeing this issue across our organization. We have Latitude E5570 with Dell D1000 docks. We use these docks for two monitors, USB inputs, and Ethernet. Our display cables are Display Port and (can be any of the following) HDMI-to-DVI/VGA-to-VGA/HDMI-to-HDMI. We may also use audio if the users have the auxiliary speakers attached.

Please let me know if there's anything I can do to help or any additional details you need about our environment.

Here's my system info:
1. Windows 10 Build Number (available from System_Details.txt of our Customer Support Tool). Home/Pro/Enterprise is not needed.

OS Build: 10.0.14393.0

2. Enumerate each display, its resolution and if it is connected to the graphics card or a USB adapter (available from System_Details.txt as well).

DELL P2214H Manufacturer: DEL ProductCode: A097 Serial: KW14V478528L Built: 28/2014
DELL P2214H Manufacturer: DEL ProductCode: A098 Serial: KW14V4CF27KL Built: 51/2014

3. The CPU ***full*** name including the numbers after iX (available from System_Details.txt as well). Generation is more important to understand the architecture rather than if it is an i3 or i7.

Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz

4. The GPU details (available from System_Details.txt as well).

Graphics: DisplayLink USB Device (DisplayLink)
Graphics Driver: 8.0.762.0 Dated 2016/08/17
Graphics: DisplayLink USB Device (DisplayLink)
Graphics Driver: 8.0.762.0 Dated 2016/08/17
Graphics: Intel(R) HD Graphics 520 (Intel Corporation)
Graphics Driver: 21.20.16.4574 Dated 2016/12/23

5. What you include in your CPU usage (which processes: overall, WUDF, DWM...). Note: I really need WUDF more than the rest as DWM is a Windows process).

WUDFHost.exe @ 30% when active. Using Skype, jumps to 70%.
Desktop Window Manager stays between .7% and 3%.

6. The value of CPU being used.

50-70% with normal usage.

7. What happens on ALL indirect displays (indirect = through USB). If you have Task Manager on an indirect display, then it is NOT idling as content changes!!! This is really one of the most important point. Here are some examples:
7a. Content fully static: nothing changes at all, and I mean nothing, not the clock, not the mouse pointer.

WUDF idles between .2% and 3%.

7b. Some little area changes: like for instance you only have some numbers on the clock or the numbers in Task Manager.

WUDF idles the same as 7a.

7c. Only the mouse pointer across indirect displays. (if you do this, please do NOT use the mouse trail accessibility feature or this is the same use case as 7b).

WUDF is active 26-33%.

7d. Moving a window. Indicate an idea of the size of the window... I mean moving a 10x10 pixels windows is obviously fundamentally different to moving a 4kx4k one.

WUDF is active 38-46% moving a Chrome window half the size of one of my monitors. Oddly enough, Chrome usage spikes.
WUDF is active 38-42% moving a Skype for Business 2016 window 1/3 the size of one of my monitors. Even more odd, the input lag from moving the single window is several seconds, whereas the Chrome window had very little.

7e. Playing video on VLC

WUDF is active 30-45%.

7f. Playing video on a browser (and the value is constant across browsers). Our driver CANNOT differentiate which browser is playing.

WUDF is active from 28-40%.

7g. Game, full screen or windowed? Games do NOT use the same as video playback.

No games are installed on our PCs.

8. Which version of DisplayLink driver you are running as, like Windows builds, they don't all have the same features. (available from System_Details.txt as well).

DisplayLink Graphics Driver (8.0.778.0) on 2017/03/20 Status is Installed
This is the driver available from Dell's site for the D1000 USB docking station. Will be attempting the same tests with the latest drivers as well after seeing this thread.

I am having high CPU issues as well with a D3100

1. OS Build: 10.0.14393.0
OS Build Label: 14393.rs1_release.161220-1747

2. Monitors Connected:
DELL P2414H Manufacturer: DEL ProductCode: A09A Serial: 524N34CR7NJU Built: 52/2014 (1920x1080)
DELL P2414H Manufacturer: DEL ProductCode: A09B Serial: 524N34CR89FU Built: 52/2014 (1920x1080)

3. CPU: Intel(R) Core(TM) i5-6300HQ CPU @ 2.30GHz
Number of Cores: 4

4. Graphics: NVIDIA Quadro M1000M (NVIDIA)

5&6. WUDF typically between 38% and 48%

7. Only using external displays (details above), all screen refresh is delayed. Minimizing/resizing windows, dragging windows around the desktop when not in full-screen mode, videos are always choppy (especially noticeable in browser, like youtube for example)

8. Graphics: DisplayLink USB Device (DisplayLink)
Graphics Driver: 8.2.1407.0 Dated 2017/03/06

Laptop is a Dell Precision 5510

My laptop often completely hangs to the point where I need to forcibly shutdown

Hello,

Thank you for those who have tested 8.2 Beta 2 and sent their feedback.
8.2 M0 has now been delivered and includes some performance improvements.

A team is allocated full time to looking at the CPU usage in some particular use cases based on your reports.
Some applications are not really good citizens and send us constant full screen updates when they show static content (like the inbox Photos application, or Spotify). Improving the behaviour for these suboptimal applications is a longer term feature.
The team has also identified particular situations with video playback where we can save some calculations and therefore lighten the load significantly.

We have had to build dedicated test rigs and code to make sure we can make reliable measurements instead of relying on subjective impressions.
A second team will join the effort when they have finished current commitments.

We keep putting significant money and development resource into delivering incremental improvements.

Kind regards,
Alban

Alban, thanks for your and your team's efforts on delivering this update and working with your users. I just installed it and although I have not yet put the computer through its normal paces, I can "hear" some improvement... meaning the fan is not spinning up as much due to high CPU use.

Logging
 

Is there a way to log which applications are not being good citizens and doing full screen refreshes ? maybe we can force their owners to modify.

Also, since the Indirect Display Driver stuff, how do we force Microsoft to take action on performance issues ? i.e. i think i understood that OpenGL isn`t accelerated anymore because Indirect drivers doesn`t yet have OpenGL passthrough...

Thanks, Erik.

The Windows creator update finally fixed all my issues! No lag anymore and no high CPU usage for WUDFHost.exe :)

Hi Erik, I advise you to use the Windows Feedback Hub to ask for the OpenGL ones.
I know they are working on it. There are two different aspects, OpenGL and OpenGL ES.

For the full screen updates, I don't know how you can get that without a development environment showing frames. I was wrong about the Photo app, it behaves correctly.

Creators' Update
 

I updated to Windows 10 1703 (Creators' Update) and now every time I connect to my HooToo DisplayLink Certified docking station my CPU pegs at 100%. Made sure all my drivers were up to date and even tried using the DisplayLink Cleanup utility to fully rip out the old DisplayLink driver(s) and install the most current (8.2) but the issue persists. The issue immediately goes away as soon as I disconnect the USB docking station. This same computer/docking station have been functioning just fine for over 2 years. I ended up reverting back to Win10 1607 and the issue has cleared up. Please advise..... Logs attached.

While 8.2 M0 on windows 10 1703 is much better than before, its still basically unusable anytime video content is being displayed. If I am on a conference call using Cisco Jabber or Webex my CPU pins it self to 100% usage and makes everything like a slideshow. Screensharing does not have this effect. If I hide the video window, CPU usage drops back down to a much more reasonable level.

If I use a non-displaylink dock there are no issues. This has been tested on several vairants of Dell and Microsoft devices all with the same impact. using a higher end device with a top of the line I7, SSD, 32gb ram results in the same 100% cpu usage.

This was not a problem before anniversary update or back on windows 7.

8.2 M1 works great for me, CPU dropped significantly.
Thanks.
Machine is Dell XPS 13

Hello Patty and all,

We are delivering incremental improvements based on use cases reported at the time.
Some will see change, and some won't. That seems a better approach rather than not delivering anything to anyone when we have something beneficial to distribute.

8.3 will be bringing additional improvements in some use cases. There are also others planned for 8.4.
I'm trying to get an 8.3 Alpha version made available early June to get feedback on this, and other items. At that time, I'll create a dedicated forum board and post here.

Kind regards,
Alban

CPU load
 

Hi

I have read the many posts about the WUDFHost.exe causing a high CPU-load and since I have this issue I have already tried like everything:
- Cleaning up the display link drivers
- Installing older versions of the display link driver
- Reinstalling all kinds of drivers
- and so on and so on...

I think this problem came up after the recent windows update last week, but I am not 100% sure.

My issue:
I am using a USB 3.0 docking station by Lenovo (ThinkPad USB 3.0 Ultra Dock, Driver version: 8.2.1952.0, but I have already tried with 8.3 too) and via HDMI I have connected a monitor to it. When I remove the HDMI cable from the docking station, the CPU-load goes down and the fans are going back to a normal noise level again. What I have also recognized is that when I stop "explorer.exe" the CPU-load of "WUDFHost.exe" goes down too (to around 0.2 - 0.8%), even though the HDMI cable is still connected to the docking station and the monitor is still working. When I close the most CPU-consuming "WUDFHost.exe" the load goes down as well but this time it (of course) detaches the monitor.
"Windows Explorer" and the "Windows Driver Foundation - User-mode Driver Framework Host Process" are together using around 50% of the CPU when the laptop is connected to the monitor through the docking station.

My hardware & OS:
Laptop: Lenovo Yoga 900-13 ISK
OS: Windows 10 Enterprise
OS Version: 1703
OS Build: 15063.483
Docking Station: ThinkPad USB 3.0 Ultra Dock

Any help would be highly appreciated! Thank you and have a great day.

Cheers,
Kris

Still not solved
 

Hi,

Yesterday I downloaded this version again:
DisplayLink USB Graphics Software for Windows - DEV BUILD NR-135298-LS-1 (8.3.1852)

First nothing changed but then, after a few minutes, all of a sudden the CPU-load went down. Both for "explorer.exe" and "WUDFHost.exe". Today the CPU-load is going crazy again: Both processes consume around 50% together. So I am back to where I was.


UPDATE:
I just disabled the visual effects in windows and the CPU-load went down immediately. Does this mean that the docking station + the display link driver does not work well when the visual effects are enabled?
This is my setting for now but I will keep an eye on it to make sure if this really was the solution to switch to "Adjust for best performance":

http://manibela.ch/performance_options.PNG

Cheers,
Kris

This helps a little bit, but it is part of a bigger problem. we've found that pretty much any app that uses fades, transitions, or animations can bring the driver framework (and thus displaylink) to its knees. Its really unfortunate there isn't a good fix though at the moment though as we heavily rely on video conferencing and the experience is pretty much that you get choppy video and cannot really do anything else with your machine.

Currently trying out the 8.4 alpha, and its not much difference performance wise on the machines i've tried it on which is unfortunate.

Hello,

Here is an answer with numbers taken using an Intel 6th generation Core m5.
Measurements were automated with moving cursors, moving windows, browsers... to make them repeatable and comparable.

From 8.0 to 8.1, the CPU usage was decreased by ~20% during idling and moving mouse cursor.
From 8.1. to 8.2 M3, the CPU usage was decreased by about ~25%, in conditions like moving browsers.
From 8.2 M3 to 8.3, the reduction is about ~5% with applications and web browsing.
The work continues for 8.4 and beyond. We're doing both short term and long term investments.

Interesting find about the transitions (and things like that in browsers). I don't believe the issue is with the UMDF, but could be OpenGL pass-through not working correctly on Windows 10 indirect displays. Microsoft is pushing hard to get engagement with Intel but Intel has been unresponsive.
This means that some activities which could be hardware accelerated are done is CPU. This stays on the agenda of my weekly call with the MS graphics team. Microsoft or DisplayLink have no intention of giving up!
The next step though will be OpenGL ES to be optimal on browsers like Chrome and their WebGL. That engagement is also in progress.

For the video conferencing, I think this could potentially be something else. You need to do real-time transcoding. In a use case like that, the bottleneck might be around memory bandwidth (moving data). There's work ongoing on video playback too.

Kind regards,
Alban

Just got a new Dell Latitude E7480 with a D6000 docking station. And then I had to find about this annoyance.
Playing full screen video on my external 2560x1440 monitor is with one exception impossible without getting eye cancer because of stutter, tearing etc.

For detailed log see attachement.

1. Windows 10 Build Number
W10 1703. But it was the same in the previous version. I only got the update to 1703 today and even did uninstall DisplayLink, used the cleaner and reinstalled. No difference.

6. The value of CPU being used.

?

7. What happens on ALL indirect displays (indirect = through USB). If you have Task Manager on an indirect display, then it is NOT idling as content changes!!! This is really one of the most important point. Here are some examples:
7a. Content fully static: nothing changes at all, and I mean nothing, not the clock, not the mouse pointer.

Actually with a cursor blinking and the clock changing every minute, the CPU load is 1%, just as expected for an idle system.

7b. Some little area changes: like for instance you only have some numbers on the clock or the numbers in Task Manager.

With the task manager maximized and high update frequency, CPU load is 7% with the CPU graph and 10% with the detailed process list.

7c. Only the mouse pointer across indirect displays. (if you do this, please do NOT use the mouse trail accessibility feature or this is the same use case as 7b).

6-7%

7d. Moving a window. Indicate an idea of the size of the window... I mean moving a 10x10 pixels windows is obviously fundamentally different to moving a 4kx4k one.

Standard CMD window 20%. Explorer with file list about half the size of the monitor: 20-40%, depending on speed.

7e. Playing video on VLC

Standard settings: 70% but choppy, laggy playback with tearing.
With OpenGL as output renderer the playback is almost ok, but CPU goes up to 90% total.
Other renderers are not a noticable improvement in playback quality.
With MPC-HD all renderers yield bad results.
Interestingly the built-in Windows 10 player ("Filme&TV" in German) and the WMP both manage to play the video fine, since they seem to use incredibly little CPU for playback, around 5%. Still WUDF uses about 40%. Total is between 40-50%. Looks like with these players, the PC isn't choked, but it is still unacceptable.

7f. Playing video on a browser (and the value is constant across browsers). Our driver CANNOT differentiate which browser is playing.

Firefox and Chrome both choke with 90-100% load when playing https://www.youtube.com/watch?v=eminWvN1O88. Playback quality is unacceptable.
Edge seems to cope well. 50-70% CPU load and playback is not as back as with the other browsers, still it is not as good as playing a local copy. But still MS software seems to use a different pipeline than other programs. And while this mitigates the issue, it doesn't solve it.

7g. Game, full screen or windowed? Games do NOT use the same as video playback.

No games available, but just zooming in Photoshop CS4, which is OpenGL accelerated, yields 30+% WUDF load.


Overall the issue is proportional to the amount of changed screen estate. Playing videos in smaller windows works. Using the mouse sometimes feels like dragging it through honey when the system is peaking.

So, when can we expect usable drivers? The reports are going on for months and DisplayLink isn't around since yesterday. I'm using the latest release drivers and there aren't even newer alpha or beta drivers to test. We were promised the devs are working on the issue, but I've yet to see any breakthrough on the issue. Please don't test this with external FullHD monitors and announce that everything works fine. DisplayLink advertises 4K@60 and I assumed this included changing screen content, not static images.

Updated to 8.3.1905.0. Still the same bad performance.

Windows 10 Insider Preview Redstone 3 - Key Performance Upgrade
 

I wanted to post a reply to this thread that I've been watching for almost a year now. As many of you have experienced, since the Anniversary Update (v1607) of Windows 10, and now the Creators Update (v1703), performance over DisplayLink has been very poor.

Although improvements have been made through various driver releases, they never could reach the performance seen with Threshold 2 (v1511) of Windows 10.

To make this short, on the advice of a support representative of one of the major suppliers of docking stations running DisplayLink technology, we tested the Windows 10 Insider Preview (which is deploying the Falls Creators Update or v1709) as word was Microsoft had made a change to the driver framework that might help. I'm happy to report that indeed the Insider Preview for the Falls Creator Update of Windows 10 is showing some drastic difference in CPU utilization in comparison (both on 8.2 M3 and 8.3 M0.)

We've done some extensive testing and it looks like the performance is now more inline with what was experienced in v1511.

The only bad news is you'll have to wait until October for the official release as Microsoft delayed the intended release a month to work on some additional issues.

For those that have been holding off from going from v1511 to v1607 or v1703 because of this issue, I hope this is as much of a relief for you as it is for us. This is especially important because Microsoft will not release any new security updates for v1511 past the final cumulative update slated October 10th.

I also hope DisplayLink continues to work with Microsoft in regards to the Driver Framework changes they introduced back with v1607. It's very possible that what was introduced then will reappear down the road with any future upgrades.

Thanks

C