Skip to content

Commit

Permalink
Merge branch 'main' of github.com:liyafe1997/DisplaylinkLaggyFix
Browse files Browse the repository at this point in the history
  • Loading branch information
liyafe1997 committed Dec 28, 2022
2 parents 767dcff + 9659251 commit b5b0053
Showing 1 changed file with 22 additions and 0 deletions.
22 changes: 22 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
# Background
DisplayLink Windows driver uses a User-Mode process to render graphics to the device. As default, the process CPU priority is NORMAL. So, when the CPU load is high, the DisplayLink graphics will become laggy.

In Windows 10 and above, the DisplayLink driver use [WUDFHost.exe] to load its driver. The dll be loaded is [dlidusb3.dll] or [dlidusb2.dll] (From the name, seems it will load different dll when the DisplayLink device is connected to different USB Bus, USB2.0/USB3.0).

In Windows 7/8/8.1, the process is [DisplayLinkManager.exe], no [dlidusbx.dll].

This program will automatically find the DisplayLink process and set the priority to high. It uses WMI to listening a specific process starts (In Windows 10/11, it is WUDFHost.exe), then will check the dll with specific name prefix is loaded or not. Finally it will set the process priority to HIGH.

# Usage
Be careful, please use the 64-bit (x64) version in 64-bit Windows. (32-bit version does not work in 64-bit OS because 32-bit process can not access 64-bit process in 64-bit Windows)

The first argument is the process name to be looked for (without .exe). The second argument is the dll name prefix to be looked for.

In Windows 10+, you can just run it without any arguments. it will set [WUDFHost] as the process name and [dlidusb] as the dll name prefix.

In Windows 7/8/8.1, you can run:
```
DisplaylinkLaggyFix_x64.exe DisplayLinkManager DisplayLinkManager
```
You have to run this program with Administrator privileged. You can run it from the desktop to test it at the first time.
Once you found it is working well, it is suggested to run this program by Windows's Task Scheduler, set the trigger is when computer is started. And set the runner user is set to [SYSTEM].

0 comments on commit b5b0053

Please sign in to comment.