Partial input lag fix #996
Posted: 20 Jun 2025, 12:47
In HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e96f-e325-11ce-bfc1-08002be10318}\0000
modify the DWORD called DriverDateData.
For example mine ends with 01 and I changed it to 00.
I usually try to use AI for automation only, but I was really thinking about how this one could affect anything, so here is the answer it gave:
"You almost certainly triggered a driver-reload or filter-stack change, not altered a live datapath • When you flipped DriverDateData you forced Windows PnP to think “this INF is different,” so it re-installed or re-initialized the mouse/touchpad stack at the next reboot. • That re-install can drop OEM filter drivers (or swap you onto the pure Microsoft HID/mouclass.sys stack) and reset internal buffers/timers. In short, you ended up using a “leaner” driver chain without realizing it."
It's also worth doing this for devices, like storage, generic pnp monitor, usb root hub, usb xhci, everything that has DriverDateData under HKLM\SYSTEM\CurrentControlSet\Control\Class
modify the DWORD called DriverDateData.
For example mine ends with 01 and I changed it to 00.
I usually try to use AI for automation only, but I was really thinking about how this one could affect anything, so here is the answer it gave:
"You almost certainly triggered a driver-reload or filter-stack change, not altered a live datapath • When you flipped DriverDateData you forced Windows PnP to think “this INF is different,” so it re-installed or re-initialized the mouse/touchpad stack at the next reboot. • That re-install can drop OEM filter drivers (or swap you onto the pure Microsoft HID/mouclass.sys stack) and reset internal buffers/timers. In short, you ended up using a “leaner” driver chain without realizing it."
It's also worth doing this for devices, like storage, generic pnp monitor, usb root hub, usb xhci, everything that has DriverDateData under HKLM\SYSTEM\CurrentControlSet\Control\Class