I have encountered problems with Bundle files when the project is expanded in a newer version (or an older version) of Sonar.  That being said, I frequently use them as a tool to clean up a project that is in progress and ensure that I have all of the correct files for the project. To me, bundle files are an important tool for cleaning up a project.
 
Glen

People have also had cwp files become corrupted but it's not the fault of the file type that has caused the problem. Neither is the file type the problem with bundle files. The fact is that any type of computer data can become corrupted.

Just as in all things computer, have a good backup strategy. I think the real caution with a cwb file is that if it fails to open you've done your data. Though Cakewalk will always help out with recovering the cwb file if you ask.

mudgel
People have also had cwp files become corrupted but it's not the fault of the file type that has caused the problem. Neither is the file type the problem with bundle files. The fact is that any type of computer data can become corrupted.

Just as in all things computer, have a good backup strategy. I think the real caution with a cwb file is that if it fails to open you've done your data. Though Cakewalk will always help out with recovering the cwb file if you ask.

Yes. But the ancient backup strategy advice quoted from  the Knowledge Base above ("delete the project file and clean audio disc after saving as bun!!")  is simply suicide and idiotic with the memory prices of today. 

gcolbert
I have encountered problems with Bundle files when the project is expanded in a newer version (or an older version) of Sonar.  That being said, I frequently use them as a tool to clean up a project that is in progress and ensure that I have all of the correct files for the project. To me, bundle files are an important tool for cleaning up a project.
 
Glen

"Save as" to a different location will do that anyway if you select the copy all audio to new location option.  I only use cwb files as a convenient way of packing up a project when sending to another Sonar user.

paulo

gcolbert
I have encountered problems with Bundle files when the project is expanded in a newer version (or an older version) of Sonar.  That being said, I frequently use them as a tool to clean up a project that is in progress and ensure that I have all of the correct files for the project. To me, bundle files are an important tool for cleaning up a project.
 
Glen

"Save as" to a different location will do that anyway if you select the copy all audio to new location option.  I only use cwb files as a convenient way of packing up a project when sending to another Sonar user.

Paulo has the right of it.

Well my self I have not used the Bun but I was wondering what the point of them was other than having a one icon delivery system as apposed to a project folder with a CWP icon and an audio folder inside. 
My self I find that straight forward. 
 
There seems to be  a steady stream of posts by people who have lost everything when using them. 
And this one guy, if you visit the old forum right now, seems to have 3 copies backed up and all are corrupted. He is mad because he followed the advice of Cakewalk. So therefor the reason for this thread. The information in the knowledge base is pour advice. You can tell it must be from 12 years ago too! 
 
I tried an experiment. 
I made a test project with a audio file and a Midi drum track. Nothing else. No efxs or instruments. I saved it as a CWP per project folder and noted the file size.
 
I did a save as a CWB  and noticed the file was exactly the same size. 
 
So to me the difference must be the audio and midi are all in that icon. One object instead of 2. So what's the point. 
As mentioned above performing a "save as" will clean up a CWP file. 
 
I always recommend when asked about back ups to include saving your project as a MIDI file as well as the CWp. This will give you a bullet proof safety copy that can be used on any DAW.

I've lost data using bun files. Never lost anything with basic per project file/folder storage.
 

Never had problem and have used them for 20 years.

I have not found a problem with bun files. Also as to why they are still an option is so those that do have them can access them. Nothing else will as far as I know.
 
Full disclosure I don't normally use them but the few I have work. My view is that a system that is working well should not have any trouble creating them. 

So this is a interesting topic.seems like a 50/50 split on love/ hate the bun. 
Now my curiosity is wondering what it is that makes these files go bad for some people and not for others? The error message most get says the audio format is corrupted? So is this a changed sample rate? Bit depth? what changed.  Or is the encryption code badly written.
If it's just the audio format changing then these people should have no trouble opening them if they re create the original environment, right? This is a regular case of user error.
But- If it's sloppy code then the "I hate the bun " club is justifiably correct.