The versions on the website are identical to the versions CCC downloaded.  So that isn't a help.  Is it possible this has something to do with installing the demo version of TH3 way back? (just guessing here)
 

msorrels
Renaming the c:\ProgramData\Overloud\TH3 folder and running the BoutiqueFXSuiteSetup_1.0.1.14 didn't fix mine.  All it did was make a single "cakewalk.of2" file in the new TH3 directory.
 

Not sure what to say there...  Are you a local administrator on your machine....  ?  We'll have to wait and see if others have the same issue and if there is a response from the Bakers on this one....  Maybe post a thread in the "Problem reports" forum

I can't seem to get BoutiqueFXSuiteSetup_1.0.1.14 or BoutiqueFXSuiteSetup_1.0.1.11 to even make the files that should be in the C:\ProgramData\Overloud\TH3 directory.  I have to go back to BoutiqueFXSuiteSetup_1.0.1.6.exe for that.  Maybe it has something to do with my Cakewalk content dir location.  I've pretty much let the CCC take over most paths but still have Content going to my D: drive.  Whatever the magic is to make the 1.0.1.11 or the new 1.0.1.14 installers to do TH3 I don't seem to have it and no amount of deleting/renaming directories is changing it for me.
 

Ok I think I figured it out and I do believe it is related to the expired demo TH3.  I had a %appdata%\Overloud\TH3 directory.  The BoutiqueFXSuiteSetup_1.0.1.14 saw that and skips/aborts installing all of Cakewalk TH3.  Even though I have no TH3 demo installed anymore.  So nothing gets updated in the c:\ProgramData\Overloud\TH3 directory and things mostly fail.
 
I renamed the %appdata%\Overloud\TH3 directory and re-ran the BoutiqueFXSuiteSetup_1.0.1.14 and this time it made the C:\ProgramData\Overloud\TH3 dir and installed the .vst3 like it was supposed to.  And I now have the correct new version of TH3 for Cakewalk.

I think you are right about it being caused by an expired Demo as I also tried the demo version of TH3

I seem to remember it may have been TH3 Cakewalk itself which "offered" the demo version, so I suspect there will be at least a few users with this problem.  They clearly are trying to protect full install customers but need to make the installer just a bit smarter.
 
I'm also seeing a problem with the Softube Saturation Knob plugin and the new release.  Sonar keeps complaining it can't find the 32bit version CLSID in my plugin registry and has me pick which one it is every time I right click on a clip.  I've tried a bunch of different resets of my VST registry but so far haven't had any luck getting it to shut up about it. 
 
I may have brought this on my self though by installing Softube's Modular the other day, their all in one installer updated my copy of the non-pro channel Saturation Knob.  I think it has something to do with how Sonar handles the dos file name in plugins, I don't think my NTFS drive has dos 8.3 filenames enabled.  But the CLSID is the same so I'm not sure why it's complaining.  I didn't have this problem before the new release, so perhaps they changed something for the worse.

 
This is pretty much the last straw for me though, this release just isn't working and isn't worth it.

I have never installed the demo and had no issue. Early days, but the evidence mounts:)

tenfoot
I have never installed the demo and had no issue. Early days, but the evidence mounts:)

I guess this is why the Bakers started the early release program so issues like this can be ironed out before the public release....

Does that mean we all qualify for Beta-Testers pay? LOL

Sidroe
Does that mean we all qualify for Beta-Testers pay? LOL

 
We are already getting it:)