I apologize for giving the (wrong) impression NOT TO search by myself in the first place. Believe me I don't like people having the lazy habit to ask others for a solution when they don't even try do do anything by themselves.
Actually I DID search the forum before starting this topic, but apparently I must have choosen inadequate search keywords, because I got no result on my search attempt.
Futhermore, since the warning appears in a Synback window, my first impression was that this problem somehow originated by a wrong use of Synback program.
I discovered later using GoogleSearch that Microsoft keeps dragging this 'known issue' from one Windows version to the next version, until M$ will take that to it's grave, without solution. Many people complain on internet about this unsolved bug (one more among so many).
If I find a pratical easy solution, I will come back.
Actually I DID search the forum before starting this topic, but apparently I must have choosen inadequate search keywords, because I got no result on my search attempt.
Futhermore, since the warning appears in a Synback window, my first impression was that this problem somehow originated by a wrong use of Synback program.
I discovered later using GoogleSearch that Microsoft keeps dragging this 'known issue' from one Windows version to the next version, until M$ will take that to it's grave, without solution. Many people complain on internet about this unsolved bug (one more among so many).
If I find a pratical easy solution, I will come back.