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.
|
02-24-2017, 01:22 PM
Threaded Mode