Same here. And if I would not be using a control surface for most of my mute, solo, arm I would have rolled back right away ...

Jim Lima [Cakewalk]
Hi folks,
We're looking into it.  We may PM some of you for more info.
 
Thanks,
Jim

Great thanks Jim, feel free to PM if I can do anything to help.
 
Cheers

Jim Lima- Here's some info that may or may not be helpful in your work on this issue.
I was thinking a reinstall of W10 was in order anyways. Doing so now with this issue might be interesting.
 
Reinistalled W10 via their recovery options ( all files/programs erased, start over)
Installed RME Drivers
Installed Command Center;  then most recent SONAR (and all associated VSTS)
Installed my own copy of AD2.
Installed Waves Central (approx 6 of their plugs)
 
Tested for issue. Still present despite the lean install at that stage.
Rolled back to prior SONAR. Issue gone.
 
Feel free to PM me if there's anything else about my setup or installed programs at this point that would be useful.

Another observation: this seems to be related to system specs, possibly graphic card installed as it happens on my main system (Radeon HD 5450) but not on the backup/test system (Intel HD 4000 graphics)

Rob[atSound-Rehab]
Another observation: this seems to be related to system specs, possibly graphic card installed as it happens on my main system (Radeon HD 5450) but not on the backup/test system (Intel HD 4000 graphics)

Weird because I have two @Radeon HD5450 (0n Win10Pro) and I don't have the issue.
 

Your mouse/mouse driver may be more the issue than your video card.
 

Intel HD 4600 On board graphics here, and I have the issue.
 
Basic everyday MS mouse and generic driver.

gustabo

Rob[atSound-Rehab]
Another observation: this seems to be related to system specs, possibly graphic card installed as it happens on my main system (Radeon HD 5450) but not on the backup/test system (Intel HD 4000 graphics)

Weird because I have two @Radeon HD5450 (0n Win10Pro) and I don't have the issue.

 
So I fired up the live rig and there it also works (again Intel graphics HD 4000)
 
 

msorrels
Your mouse/mouse driver may be more the issue than your video card.

Logitech mouse here with standard microsoft driver ...

I hope the CW crew is still looking into this. 
 
Problem is, those with issue HAVE to roll back and can no longer be testing possible causes.
It's not a minor annoyance...you literally can't get anything done.
I work with clients looking over my shoulder, so I can't be *hoping* to land the mouse pointers in exactly the right pixel, hoping my aim is good enough to enable record or mute :)
 
All we know so far from those who have chimed in:
 
Radeon HD5450: Issue present for some, not all
Intel HD4600: Issue present for one user (me)
Intel HD4000: Issue not present for one user
 
Not much to work with there, but I guess it's a start :)
 
 
 
 
 

dcmg
All we know so far from those who have chimed in:
 
Radeon HD5450: Issue present for some, not all
Intel HD4600: Issue present for one user (me)
Intel HD4000: Issue not present for one user

Same problem here with a Nvidia GTX 1060 & a Logitech Performance MX mouse, rolling back to 2017.04 solves all problems for me.
Edit: I also tried different older drivers for the Nvidia & in 4-5 new & old projects.