• SONAR
  • Looking for users who had the DLL issue Please add your info
2017/10/26 23:10:57
Cactus Music
Today there is yet another thread reguarding a user getting something like this: 
 
Sonarart.exe. Bad Image C:\Program Files\Cakewalk\Sonar Artist\CWVideoEngine.dll is either not designed to run on Windows or contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error Status 0x0000020."
 
I've read a few threads with this same error and someone did find a solution which was to have a back up copy of your Sonar folders and just replace the corupted dll with a good one. It is found the dll will show as 0 bytes. 
 I myself got this error and the dll was overloud. It seems dll is random. 
Also this has been users of X2- X3 and now Artist so it is not a Sonar issue at all.  
 
My suspision is that this is a W10 1703 update that has caused this so what I'm looking for is anyone who has had this issue to post and state:
 
*W10 version - you can view this  SETTINGS/ SYSTEM/ ABOUT ( bottom of list)   Example- 1703 or 1709
*Sonar version-  CCC. or from Help menu
*The dll that was corupted 
*and detail of when the message showed. 
 + Your anti Virus if any
 
Thanks, it would be nice to sort this out before it becomes worse. 
 
2017/10/26 23:52:19
.
Cactus Music
 
Hey how come there are only 9 pages back on this forum,, I was trying to see how far back these threads went? 
 
 



Down the bottom of the page you should find a drop down which allows you to select between a few different time spans including "From the beginning" which will show you 3518 pages.
2017/10/26 23:54:12
.
Just in case the above gets eaten, it doesn't seem to show it on individual thread pages, but if you select a Forum group page, eg 'SONAR' it should show the option at the bottom.
2017/10/27 00:15:37
bitflipper
I'd previously gone through those threads and made a list of which DLLs were affected. Unfortunately, I did not save that list. I think there were 5 different files, the only ones I can remember off the top of my head are ttslame.dll, ttslibsndfile.dll, cwvideoengine.dll.
 
I was looking for any pattern. There wasn't any that I could discern. A zero-byte file can be the result of disk corruption, but given the sudden spate of problems it would seem more likely to be the result of a file-overwrite operation that failed. That makes me suspect that some installer could be the culprit.
 
A couple of the files had recent datestamps (10-4-17) but the others were old files going back to 2007, so are unlikely to have been included in any recent SONAR incremental updates. (Presumably, the SONAR installers are smart enough not to overwrite existing files with the same internal version numbers.) One of them was a Microsoft file, part of the MFC collection IIRC, but the others were not and therefore unlikely to have been overwritten by a Windows update. Some other application might update MFC, but no other application would be overwriting those SONAR-specific libraries.
 
And that's about all I know at this time. 
 
One thing I did not make note of was the version of Windows everybody was running who had the issue. That could be significant.
2017/10/27 02:46:36
Cactus Music
Thanks Dave that is super helpful info. 
 
We have 3 W10 computers, all say 1703 and all say they are up to date when you manually run Windows updater. 
 
 
2017/10/27 07:51:43
Songroom
This issue is also being reported on other forums such as Unity3D. In the case of Unity the dll's affected are commonly FreeImage, ispc_texcomp, libcef, TextureConverter and OpenRL.

Originally it seemed that the issue was related to the latest W10 Creators Update (Version 1709 / Build 16299.19)  released on October 17th, but there have been error reports which precede this date. There's also reports linking the problem to Mcafee anti-virus.

Version 1709 is being rolled out gradually, so many users are yet to receive an update notification. To test it out, I manually downloaded the update to a test PC but I haven't experienced any dll errors so nothing gained.
2017/10/27 09:06:58
pwalpwal
iirc, someone was having the same dll go corrupt and were keeping a backup, to replace the corrupted file after updating - what about setting that file to "read only" before updating? might trigger some useful error message giving a clue...?
2017/10/27 12:20:58
bitflipper
That thought occurred to me, too - make all the DLLs read-only. The obvious problem with that solution is that any future updates that legitimately need to replace one of those files would fail. A better solution is to make a backup of the \program files\cakewalk tree and the %appdata%\cakewalk tree. Which is a good idea anyway because then you've got spare parts for any eventuality.
 
After my past disasters, I also religiously back up all my projects and sample libraries onto an external drive.
2017/10/27 12:32:55
pwalpwal
bitflipper
That thought occurred to me, too - make all the DLLs read-only. The obvious problem with that solution is that any future updates that legitimately need to replace one of those files would fail.

yeah, not suggested as a solution but rather something that might give more info, a part of troubleshooting... it 's all very weird...
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account