HIBI

I would like to check just to be sure, this does not prevent the plug-ins from upsampling themselves, but only applies to upsampling done by Sonar for plug-ins that do not have upsampling capabilities, correct?

First of all, I personally think that changing the OS drive from HDD to SSD is worth more than the cost. This is because the processing speed associated with drive access will increase dramatically. However, your PC is not officially compatible with Windows 11. Support for Windows 10 will end in October, but do you have any plans after that? That will affect whether you should upgrade to an SSD or get a new PC.

This may be off the mark, but if you have a wireless mouse that uses a USB dongle type receiver, this could be the cause. In that case, try moving the USB receiver to a port a little further away (such as the front port).

This is BFD 3.5 beta, not BFD 4, correct?

This comment by Cakewalk staff below will further clarifies your view.

Does the level knob on channel 9/10 not work with USB output?

It sounds like the loopback function of the audio interface is working. If “Enable Loopback” is checked in the UR22mkII tab of the Yamaha Steinberg USB Driver setup screen, try unchecking it.

See FAQs - "What is Backstage Pass?" on the Cakewalk Sonar page.

What will be changed by step 1? (Is it mandatory?) Does step 3 simply scan without resetting?

Yes, I knew, that because it seems you were creating a folder with a different name (IK-TONEX), so my comment was not directly relevant to the problem you had. I was merely referring to what often happens with recent plugin updates in response to OutrageProductions' comment. Sorry if I confused you. Anyway, I'm glad to hear your problem has been resolved.

I am guessing that the problem may occur in the following case. If an old version "C:\Program Files\Common Files\VST3\PluginName.vst3 (actual plugin file)" is originally existed and it's already scanned with Cakewalk, and a subsequent update installed the actual plugin file "PluginName.vst3" under a folder named "PluginName.vst3", such as "C:\Program Files\Common Files\VST3\PluginName.vst3 (folder)\Contents\x86_64-win\PluginName.vst3 (actual plugin file)". In this case, resetting and rescanning the plugin may solve the problem. (Just rescanning is not enough) So, I believe the baker should review the behavior of "VstScan.exe".

Make sure you have the latest version of Command Center.

How about trying with "rick_hardy" without the "@" mark?

I don't know why, but sometimes the reactivation toast appears a few weeks after the latest version. In previous versions, it never showed up for 6 months.