When accessing a COM port, Docklight consumes a lot of CPU time (e.g. 25%), even if there is no communication. How can I fix this?

When accessing a COM port, Docklight consumes a lot of CPU time (e.g. 25%), even if there is no communication. How can I fix this?
When accessing a COM port, Docklight consumes a lot of CPU time (e.g. 25%), even if there is no communication. How can I fix this?
Posted in Support, Troubleshooting

Applies to: Docklight V2.4.5 / Docklight Scripting V2.4.5, Article ID: dl_prb060

This seems to the a behavior that appears on recent Windows 10 / Windows 11 installations. It is related to some minor change we introduced in v2.4.5 to improve the monitoring timing for Microsoft standard driver “usbser.sys” devices.

To fix this behavior, please update to the latest V2.4 release (V2.4.11 or higher) from the links below:

Docklight V2.4

Docklight Scripting V2.4

Tags: