Solafide
[.........The only other thing I have done is use ccleaner to clean the registry, but I think that was before the windows 8.1 update.......
 

This app is well known to, oft-times cause damage to  OS systems. It is recommended to NOT use apps like this unless you are prepared to cross -check every listing it pops up. I am not saying it HAS caused your issues, but I would be quite su****ious that it has altered something. Why would you want to use it anyway if you had just performed a "clean" W8 install?
 
PS: How does "susspicous" get blocked by the forum bots that is a new one!!!

Just to add, that the days of needing to "tweak" out Windows for audio purposes are long gone . Windows 7 and now 8 are pretty much rock-solid o.o.t.b. now. Running the Power Performance tweaks are about all you need to do, as well as disabling the selective USB suspend, and also disabling the "allow applications to take exclusive control..." which can sometimes affect audio interfaces by locking them down to specific apps.
 

joden

Solafide
[.........The only other thing I have done is use ccleaner to clean the registry, but I think that was before the windows 8.1 update.......
 

This app is well known to, oft-times cause damage to  OS systems. It is recommended to NOT use apps like this unless you are prepared to cross -check every listing it pops up. I am not saying it HAS caused your issues, but I would be quite su****ious that it has altered something. Why would you want to use it anyway if you had just performed a "clean" W8 install?
 
PS: How does "sus****ous" get blocked by the forum bots that is a new one!!!

Good advice - Ill avoid it in the future.  The reason I had used it was I had some latency issues with my Nvidia video card when I first loaded up windows 8.  I tried a few different drivers to see if any of them improved the situation, and I cleaned the registry in between drivers.

joden

Solafide
[.........The only other thing I have done is use ccleaner to clean the registry, but I think that was before the windows 8.1 update.......
 

This app is well known to, oft-times cause damage to  OS systems. It is recommended to NOT use apps like this unless you are prepared to cross -check every listing it pops up. I am not saying it HAS caused your issues, but I would be quite su****ious that it has altered something. Why would you want to use it anyway if you had just performed a "clean" W8 install?
 
PS: How does "sus****ous" get blocked by the forum bots that is a new one!!!

I've use CCleaner for years (since it was called 'Crap Cleaner') and never found any problems with it.
I've run it on many user systems without any problems. I volunteer in our local Senior Center to fix broken computers. This tool is one of the first things I run after getting things working.
 
If you really think it caused a registry problem, then just reload the registry changes it saves for you or do a system restore.
 

joden
+1 sharke...not one issue on my system either. Everything ran exactly as before, I even managed to import some older CWB data with no issues! I suspect (and all due respect to posters) that perhaps the issues are with systems rather than CW. What else would explain the many differences, and why the vast majority of upgraders have no problems. Stands to reason doesn't it - I mean there must have been thousands of upgrade downloads already, but, relatively, only a handful of folks with issues.
 
And I guess it is human nature to not fully admit what someone has tweaked without knowledge, to avoid embarrassment. I come across it all the time in repairing PC systems for folk. They swear black and blue they have touched nothing and done nothing, but it always ends up with a sheepish admission usually after a couple of hours of problem hunting and elimination . Not saying that is the case here, but anecdotally, it is remarkably similar.
 

I guess that includes the guys at Cake, too, who have reproduced the Console Emulation hiss, and are working to fix it now.  I believe it was caused by some changes made to VST3.
 
The reason why only some people seethe bugs may be legion.  In this case only affecting systems using the 64 bit Double Precision Engine.  As it is off by default, most people weren't affected.  Workflow is another.  If someone didn't use the CE, they would be fine.  Etc., etc.
 
I'm sure it can often be system issues, but to make such a blanket statement is ludicrous.
 
 

jb101

joden
+1 sharke...not one issue on my system either. Everything ran exactly as before, I even managed to import some older CWB data with no issues! I suspect (and all due respect to posters) that perhaps the issues are with systems rather than CW. What else would explain the many differences, and why the vast majority of upgraders have no problems. Stands to reason doesn't it - I mean there must have been thousands of upgrade downloads already, but, relatively, only a handful of folks with issues.
 
And I guess it is human nature to not fully admit what someone has tweaked without knowledge, to avoid embarrassment. I come across it all the time in repairing PC systems for folk. They swear black and blue they have touched nothing and done nothing, but it always ends up with a sheepish admission usually after a couple of hours of problem hunting and elimination . Not saying that is the case here, but anecdotally, it is remarkably similar.
 

I guess that includes the guys at Cake, too, who have reproduced the Console Emulation hiss, and are working to fix it now.  I believe it was caused by some changes made to VST3.
 
The reason why only some people seethe bugs may be legion.  In this case only affecting systems using the 64 bit Double Precision Engine.  As it is off by default, most people weren't affected.  Workflow is another.  If someone didn't use the CE, they would be fine.  Etc., etc.
 
I'm sure it can often be system issues, but to make such a blanket statement is ludicrous.
 
 

 
I wonder why it only affects some with 64-bit DPE though. I have it turned on and have tried all modes of the Console Emulation on both stereo and mono tracks and I'm just not hearing it (or seeing it on the spectrum analyzer). 
 

I use ccleaner all the time too - and I've never had a problem with it.

sharke

jb101

joden
+1 sharke...not one issue on my system either. Everything ran exactly as before, I even managed to import some older CWB data with no issues! I suspect (and all due respect to posters) that perhaps the issues are with systems rather than CW. What else would explain the many differences, and why the vast majority of upgraders have no problems. Stands to reason doesn't it - I mean there must have been thousands of upgrade downloads already, but, relatively, only a handful of folks with issues.
 
And I guess it is human nature to not fully admit what someone has tweaked without knowledge, to avoid embarrassment. I come across it all the time in repairing PC systems for folk. They swear black and blue they have touched nothing and done nothing, but it always ends up with a sheepish admission usually after a couple of hours of problem hunting and elimination . Not saying that is the case here, but anecdotally, it is remarkably similar.
 

I guess that includes the guys at Cake, too, who have reproduced the Console Emulation hiss, and are working to fix it now.  I believe it was caused by some changes made to VST3.
 
The reason why only some people seethe bugs may be legion.  In this case only affecting systems using the 64 bit Double Precision Engine.  As it is off by default, most people weren't affected.  Workflow is another.  If someone didn't use the CE, they would be fine.  Etc., etc.
 
I'm sure it can often be system issues, but to make such a blanket statement is ludicrous.
 
 

 
I wonder why it only affects some with 64-bit DPE though. I have it turned on and have tried all modes of the Console Emulation on both stereo and mono tracks and I'm just not hearing it (or seeing it on the spectrum analyzer). 
 

Did you close Sonar and restart it after turning 64 bit DPE on?  Did you play audio through it?  Did you look at a mono interleave track with the CE on, preferably the A-type?  What were your settings on the CE - trim, drive?
 
That's just a few that we know relate to this issue so far.  Others might be - are your preferences set up exactly the same, are you using same bit depth, etc., etc., etc.. 

FWIW I have a project that I started in X3a. It worked fine in X3b. I installed X3c, loaded it up and got the hum. I am not going to swear I didn't do anything else on my system in between X3b and X3c but would could I have done that would cause it to hum?
 
The flyout PC EQ seems to be fine though. I just get the humming sound.

I don't know if you re-scanned your plug-ins after doing the update, but if you didn't, it seems to be an important step.