I hope this is resolved soon.  Really looking forward to the new features but will not upgrade until there is a solution to this issue.

I am not having the problem.  I have Win 10 Pro with Creators Upgrade (V1703, OS Build 15063.296).  My mouse is a Microsoft wireless that is paired with a Microsoft wireless keyboard.  

 I have SONAR on two computers and I'm not having that problem after the upgrade.  (Logitech mouse and keyboard on both computers.)

I updated to 17.05 last night, and played around in a project. I noticed a problem only because I was searching for it. On the face of it, I'm not experiencing any serious mouse click issues.
 
EXCEPT:
I did notice that in Track view, if I click back and forth between Mute and Solo, AND the mouse position is on the top third of the button area, SONAR seems to not see the click until I move the mouse down to the lower 2/3 of the button.
 
It doesn't happen every time. It happens maybe 1/3 of the time. 
Clicking back and forth usually gets it working again.
 
This is not a show-stopper for me, by any means. But I wonder if it is the same underlying root cause, or perhaps it is something different? 
 
Anyway, that's my experience. You have to really look for this to see it, I can see how many folks might have this issue and just not notice it.
 
(Windows 10 1607, 100% scaling)
 

JohnEgan
Im having a small but annoying issue since update

Same here.

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

Yep, same issue here.
Hovering over a control ( mute, record, echo, etc) tool appears to be the resize tool. Will not execute any intended change.
 
Workaround is clicking in the bottom portion of the button; then the mouse tool changes to allow selection.

I just got a notification that my Logitech mouse has an update. Wonder if it's related to the recent Windows 10 update.

Anderton I just got a notification that my Logitech mouse has an update. Wonder if it's related to the recent Windows 10 update.

 
Standard MS mouse here, most recent W10 update was 5-28-17.
 

Had to roll back. While the "aim low" mouse pointing method somewhat works, it's not possible to get any real work done. All is working as it should after rolling back.
 
BTW, for those investigating this...some above mentioned that this issue was not consistent. I found the opposite on my system. Issue was present when interacting with any control in track view ( I'm never in console, so no info there).
Behavior was consistent across many project files, so it wasn't file specific.
 
Odd. Hope they get it figured out. I love what I saw in the new update...but dancing around that issue was not really an option.