The fact that the problem is only observable when using a particular mouse driver hints strongly that the problem lies with the driver, although as long as it generates standard Windows mouse messages, I can't imagine this affecting only the UltraTree control. Assuming you have ruled out other controls having similar problem, it might be helpful to attach a small sample that demonstrates the problem here so we can take a closer look.