I'm not sure if this is a known issue or not, but I just purchased U-He's Satin plugin and I'm attempting to register it. However, anytime I press a key on my keyboard, Sonar is reacting to it by initiating the shortcuts. In other words, even though my cursor is on the blank field box within Satin's registration, Sonar is overriding my keyboard input. I've tried to CTRL+C/CTRL+V but I simply can't input anything into the registration fields. What do I do?!

Look in the top right corner of the synth window. You'll see a little button with a keyboard icon. Click it - Sonar will then give it's keystrokes to the plugin. Turn it off when you're done. 
 
I forget to turn it on sometimes. There's nothing worse than to start typing something and realize that you're triggering God knows what keyboard shortcuts. It's enough to make me quit without saving and load the project again 

sharke
Look in the top right corner of the synth window. You'll see a little button with a keyboard icon. Click it - Sonar will then give it's keystrokes to the plugin. Turn it off when you're done. 
 
I forget to turn it on sometimes. There's nothing worse than to start typing something and realize that you're triggering God knows what keyboard shortcuts. It's enough to make me quit without saving and load the project again 

I didn't know about that button. But even pushing it isn't working for me. Basically, I load Satin into an audio track's FX bin. As soon as I load it up I'm presented with the UI as well as a separate window (not actually a part of the plugin's UI) that has three clickable options. One of them is "enter your registration codes". I click on this an then another window pops open that has the two blank fields for me to enter my Name and Registration Number. However, even after hitting the keyboard icon I still can't bypass the issue. What in the world!?

If anyone wants to check if they get the same issue, you can download a free trial of Satin and attempt to type into the registration field yourself. I sent an email to U-He's customer support, but I'd love it if anyone could figure out a workaround as soon as possible. I want to get back to this mix I'm working on and I'd love to use Satin on it :)

This has been mentioned before in conjunction with U-He synths. I think the solution someone proposed was writing the text down and pasting it in the box. Or if there's a stand-alone mode, maybe you could register it that way? I don't think there's a fix from either U-He or Cakewalk on this yet.

Anderton
This has been mentioned before in conjunction with U-He synths. I think the solution someone proposed was writing the text down and pasting it in the box. Or if there's a stand-alone mode, maybe you could register it that way? I don't think there's a fix from either U-He or Cakewalk on this yet.

When I tried copying and pasting the code before I swear it wouldn't work. This time I tried it again and I was able to paste the text into the box. So, even when pressing the keyboard icon to give all keystrokes to the plugin you can't type, but it seems that doing so will at least allow you to copy and paste. Problem solved. Yay!

I'm glad you got it registered, but I think there may still be an issue with parameter entry. This happens with some other plug-ins, although it's not common. I'm hoping the source of the problem can be identified, then fixed once and for all.

I concur, Craig - there remains an issue lurking for some future plugin to have the same sort of thing happen, and it should be addressed.
 
To the OP - if you haven['t done so, I would urge you to open a support ticket with Cakewalk Technical Support, as well as with the vendor for this plugin, since this plugin can repeatedly expose this issue.  
 
This way, both companies have a repeatable scenario from which they should be able to figure out why that plugin exposes this issue, and then perhaps a permanent fix can be engineered.
 
When you open the support tickets, go to your initial post for the thread and grab the Permalink for it, and paste that into both support tickets, and perhaps also update the tickets after you create them both, so that you can update each ticket with the problem numbers for both companies - which might help them work together on fixing the issues.
 
In any case, glad you stuck with it, and even more glad you got past it :)
 
Bob Bone