Thedoccal
Is this something that could be originating in the Mouse Properties in Control Panel?  Does it still happen if you choose a scheme like extra large?

Good Day,
Apparently, not I tried most all schemes, starting at none. (#18).
 
Cheers

Seth Kellogg [Cakewalk]
 
Edit/Update: Just found out QA/Dev may have squashed this for 06.2017, we're still investigating DPI changes and stuff though.

Great, hope so, anxious to move on to my next issue (LOL, just "rippling" you).
Cheers

Tracks Narrow or expanded, the resize icon was VERY difficult to work buttons, and not just on top track but ALL tracks.
 
 
g

gh4267
Tracks Narrow or expanded, the resize icon was VERY difficult to work buttons, and not just on top track but ALL tracks.
g

Same here.
Issue was present with every track and control I attempted to interact with; "working through it" was not an option. 
 

I'm selling my RX470 graphics card so am now on the default internal Intel HD graphics.
 
Tried the 2017.05 update again and same issue.
 
So zilch to do with the graphics card it would seem, at least on my end.

ESharpe
 
Had to rollback the update to get anything done in Sonar.

Me too. No chance in the world I could work with that ... whatever I tried to do at the track header in TV always only showed me the resize mouse pointer ...

I use a wacom pad and I have no issues. Don't know if anybody else has one they may need to know.

FWIW, I had posted earlier that I was not having the problem on my DAW desktop system.  I got my Laptop out today, updated to the latest Sonar and tried it on that and no problems either.  The Laptop is a Toshiba Touch Screen with Win 10 (Creator's Upgrade).

The new Early Release has solved my mouse problems and we seem to have more forgiveness with resizing location, as in, you don't have to be exactly on the pixel between tracks to resize them.  There does seem to be some unfinished work with the graphical layout, new bigger wasted space at top like the old old one.  inspector is cutoff when collapsed still clickable though. I think we're back in business overall.

Issue still partially exists in the take lanes, bottom of buttons in most cases.