Erroneous controller view in PRV Controller Pane

As I read the events list it is saying you have A wheel event on midi channel 4 at a time I can not read.
 
What instrument are you using?  I ask as I have not come across an instrument that uses multiple channels for wheel events.  
 
Are these used for articulations? 
 
As for the events list only showing the track number and not the patch name of that track perhaps you should report that as a bug in the problem report forum and here.

I doubt your first statement I have never seen Cakewalk software products write anything but the channel it has been told to use.
 
I did not state that you were using hardware instruments I asked what instrument be it Hard, soft or even slightly spongy.
 
Cake can not verify problems that are not reported.  The purpose of this forum is to allow people to report a problem and get it verified by a third party then allowing that problem to properly reported.
 
There will always be roadblocks you just have to learn how to negotiate them.

Changing track focus does not change what controllers/channels are displayed in the controller pane, but the controller events will be ghosted if they're on a track other than the one that has focus. This isn't evident from your screenshot, because you don't have enough of the controller lane showing.
 
 

In the image, yellow lines, it can't be clearer, can it?    The track in question has two controllers in use, as shown in PRV (I didn't change the default: it shows ALL controllers for ALL selected tracks for ALL channels).   But the Event List view of the SAME track shows OTHER controllers: a pitch bend on Channel 4, and a group of CC1,7,10,11 in EL above the yellow circle.      This is windows 7, sonar platinum, version 21.01.00 build 38 x64.
 
I didn't 'hide' anything in the PRV, there are controllers (pitch bend on channel 1 and on channel 3).   Brundlefly, as you can tell from the window labels, in each case there is only ONE track involved, so the 'ghosting' thing, while true, is not relevant here.
 
That's issue 1, the bug.
 
Issue 2, I suppose, is about how sonar adds different channels: it's true you can tell it what channel to use, and it obeys.  But if you DON'T select a channel explicitly, it uses some screwy logic of its own, track order or something, and you end up with a wide variety of channels in the same track.
 
Issue 3, The red lines show how irritating it is that sonar still refers to the SAME tracks in different ways depending on which view you use. 

Sorry wookie, I didn't think it relevant.    But this project uses Kontakt 5, VSTi, 5 instances, and GPlayer, VSTi, 3 instances.    Approximately 50 K5 instruments and 20 GP instruments loaded in the various VSTi instances.    I have a midi keyboard for input sometimes, Kurzweil 2500, but it is turned off.    No other instruments involved.

williamcopper
In the image, yellow lines, it can't be clearer, can it?    The track in question has two controllers in use, as shown in PRV (I didn't change the default: it shows ALL controllers for ALL selected tracks for ALL channels).   But the Event List view of the SAME track shows OTHER controllers: a pitch bend on Channel 4, and a group of CC1,7,10,11 in EL above the yellow circle.      This is windows 7, sonar platinum, version 21.01.00 build 38 x64.
 
I didn't 'hide' anything in the PRV, there are controllers (pitch bend on channel 1 and on channel 3).   Brundlefly, as you can tell from the window labels, in each case there is only ONE track involved, so the 'ghosting' thing, while true, is not relevant here.
 
That's issue 1, the bug.
 
Issue 2, I suppose, is about how sonar adds different channels: it's true you can tell it what channel to use, and it obeys.  But if you DON'T select a channel explicitly, it uses some screwy logic of its own, track order or something, and you end up with a wide variety of channels in the same track.
 
Issue 3, The red lines show how irritating it is that sonar still refers to the SAME tracks in different ways depending on which view you use. 

What's shown is clear, but how you got there is not. I could reproduce that screenshot quite easily without invoking any buggy behavior. Without the steps the screenshot by itself is not sufficient to demonstrate there's a bug.
 
The channel for new events is whatever your controller is sending if you're recording, or whatever the channel of the last touched event was if you're drawing in the PRV, or channel 1 if you've just opened the project and haven't touched anything. I don't believe any screwy logic is involved.