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...
Yes, as a troubleshooting tool: if the DLLs were all read only, you might get lucky and catch the errant installer in the act because it threw up an error dialog. Unfortunately, this problem seems to be sporadic so you might have to wait a long time.
I'm guessing most folks who've seen it are on Windows 10, just because more of us are on W10. Cactus, didn't you say in the other thread that you got hit with it on your W10 machine but not on your W7 laptop? Could be a clue, or maybe not - there could be a great many other variables between your two computers, e.g. you probably don't have as much software installed on the laptop as on your desktop machine.
CWvideoengine.dll seems to come up a lot, but only recently. I don't recall it being mentioned before a week or so ago. cwvideoengine.dll (Cakewalk Video Engine) is one of the files with a recent datestamp (10-4-17), so it's likely to have been installed as part of a recent SONAR update.
Here's a random thought: has anyone tried to do an update while SONAR was running? I haven't ever done that (being an old-school guy I shut down
everything before any install) but I'd expect the installer to raise an error when it tried to overwrite an open file. But what if it aborted mid-update and left some 0-byte files behind? Just a random thought.