A few things been going on lately. I don't know if it's windows or Sonar or a combination.
When I grab part of a track to edit it such as trim the end, crossfade or grab the track to move it. It doesn't always perform the 1st time, sometimes it takes a few time before it will let me do the operation.
 
i could be editing the volume in an automix on a track, so I grab the line to put it where I want it and it jumps up to zero for no reason, same with a fader, I could put the curser on it to move the fader down a bit and it will jump to zero as well. Clicking mute doesn't always work the first time either.
 
Even inserting a track cause the new track to fill the screen which I have to shrink down to a usable size.
 
I have no idea what is causing this nor can I figure it out.
i am on the latest build of Sonar from the command center.

I'm not sure if this is right or not, but try disabling the read or write buttons in the track first, then click them again when done editing. I had some volume envelopes that were a little finnicky and I think that's how I solved it. Also, is it a comped track? Don't know if that matters , just thinking , "something is hidden here that is making this not working for this person".

worth a try, I'll let ya know later today. Yes it was a comped track at first and then pretty much any track.

Is this just one project?

"Clicking mute doesn't always work the first time either" makes me wonder if this is a driver issue.

What is your audio interface? You could try uninstalling, rebooting and reinstalling the latest audio interface drivers (do this whether you have the latest drivers already installed or not).

For extra credit you could update your display drivers as well.

Nevermind this particular post. OP answered the question already I did not need to ask it (regard as dupe).

I'd suspect the mouse. When the buttons wear, they are prone to "button bounce" and sending spurious signals.
 
See if you can borrow another mouse and see if those problems go away. Or get a quality gaming mouse with sturdier buttons. If you are using an RF cordless mouse, consider going with a traditional corded model or IR, as RF transceivers are prone to interference that can also cause similar symptoms.

bitflipper
I'd suspect the mouse. When the buttons wear, they are prone to "button bounce" and sending spurious signals.
 
See if you can borrow another mouse and see if those problems go away. Or get a quality gaming mouse with sturdier buttons. If you are using an RF cordless mouse, consider going with a traditional corded model or IR, as RF transceivers are prone to interference that can also cause similar symptoms.

You were corect bitflipper. I switched the mouse from the laptop to the studio pc and visa versa and Sonar has worked fine since and now crazy stuff is going on with the laptop with that same mouse.