Right Tech, I will try and clarify for you.
JEAN* was disappointed in my answer, in thinking that with MBAM finding what it though was a problem relating to scrfile (screen saver files) in the registry, that he though would resolve his problem with screen savers.
My response two posts before the one you quoted, said that this entry was the same as the one in my registry and also detected by MBAM, but I chose to Ignore it as a) I hadn't changed that from the default settings and b) I didn't think it was malicious.
JEAN* chose to allow MBAM to change it and now his screen saver works.
That one you have shown from the last MBAM scan I have it Ignored from when it was detected on my system.
Looking at it it looks more like it is complaining about the syntax of the string "%1" %* which it classes as Bad (though I for the life of me can't see why, which is why I chose to Ignore it) and "%1" /S which it considers Good. Again I don't know why as this relatively new system hasn't been amended since it was purchased in regard to screen saver files.
I don't know if the /S switch after the "%1" is safer than the %* in the event a malicious screen saver attempting to be installed. But, it doesn't mean you have something malicious on your system.
So why changing this worked fore JEAN* I have no idea as my screen saver works with the original settings "%1" %* the ones MBAM considered bad. So in theory those settings should also have worked for JEAN*
The main thing is that JEAN*'s problem is resolved.