Thanks Henrik,

As I said, I didn't change ANYTHING to my path & filenames passing from MCS v3.0.0.5 to v4.0.0.0, meaning, it was working well "as is" in the previous version.

Although there is a workaround (btw not tested yet), I was more rising a question about if somebody else experienced this problem too.

Am I the only one out there getting this warning message?