Hi Lemon Drop,

 

That was suppose to happen.  MBAM fixed a small issue with the release of version 1.27.  Here is what they fixed. 

 

HKEY_CLASSES_ROOT\scrfile\shell\open\command\ (Broken.OpenCommand) -> Bad: ("%1" %*) Good: ("%1" /S)

 

Here is a post by ky311 regarding this.  click here

 

Hope this helps.

---

LemonDrop50 wrote: 
it wont let me quaranteen this so do i delete it? i dont know how to fix this

---

To clarify, for MBAM to "fix" this you need to delete it using the Remove Selected button 

well one person says it is ok and you say delete it i am saying if it isnt harming anything, being there then why fix? any way as i said it wont let me delete or quarantine anyway that is one reason i wrote incase it was bad how do i delete this thanks for the help

Ensuring the item is checked, clicking remove selected removes (on re-boot) the " bad " and replaces it with the " good " therefore "fixing" it.

 

HKEY_CLASSES_ROOT\scrfile\shell\open\command\(Broken.OpenCommand)-> Bad: ("%1" %*) Good: ("%1" /S)

-> No action taken.

 

Note the "data" in the pic:  "%1" /S, in your case, before MBAM "fixes" it it would be "%1" %*

 

 

LemonDrop50:

"any way as i said it wont let me delete or quarantine anyway"

 

Are you saying after checking the item, clicking remove selected and re-booting (if/when prompted), It doesn't do anything, a subsequent scan still detects this? 

well i didnt reboot so i will have to re run it an click delete and reboot thanks and i will let you know how it went thanks