unexpected Error code

Looks as if a file didn't get bundled correctly - maybe because it contained illegal characters in the filename, or it got moved/deleted. Could be the .wav from your bounce.

try opening it in Sonar's "safe mode". Hold shift when you click the file to open it. It'll open without loading the plug-ins.

hmmm.... I'd probably start trying things (grasping at straws!) that don't necessarily have a lot of reason to it. Try putting the file on a different drive & trying to open it from there, or maybe opening it on a different computer that has Sonar, or even a different version of Sonar. Not very scientific, but I'd had luck doing some of those things before.

Was just going to suggest that. It will ignore the headers and load it as one big wave file, but could give a clue as to what's missing.

If you don't see the extentions after files, turn Hide Extensions for Known File Types in Tools/Folder options.

I don`t know why

Probably because it didn't write the file itself, so had to build up its internal 'cache view' or whatever you call it for it, from scratch. That probably got corrupted somehow on the old install.

Maybe just drop this at CW tech support too, to go on the list of to-be-checked's for the next update.

Glad it's solved, but should not have happened - bundles are pretty useful, whatever some people may say about them.

Up please, it's very important

I know this is an old thread, but just recently had this problem, and hopefully this will help someone else.
 
I traced it back to a program that I was using to Overclock my system.   It was EasyTune 6 that was not handling the memory timing in the overclock, and was screwing up the bundling.    After removing Easytune 6, the problem disappeared.   Tuns out it was corrupting anything memory dependant.
 
To the above post, you can use both mono and stereo files, but they cannot be bundled.  Use per project saving, and it works fine.
 
 

Another good reason steer away from using bundles if at all possible.