Hi behsci,
Just a quick question, is this thread a result of receiving a Bot Notice from Constant Guard via either phone call or email from Comcast? It really doesn't matter, but I was just curious.
I have seen some references to the " Broken.OpenCommand" being fixed using MalwareBytes.
Specifically, the following are provided by quietman7 over on Bleeping Computer ( a well respsected Security Expert/ $soft MVP )
He asks: "Do you have a program installed that prevents registry changes from taking place or have used a tool to fix associations?"
Then replies:
Quote
"Malwarebytes sees and reports that the association for these files are not the default ones as set by Windows (since malware may alter these associations as well). When you select to remove in mbam, mbam restores it to the default associations again (as set by Windows). So you have 2 choices here... Or you ignore the detection in mbam, or you don't let System mechanic modify the default associations"
explanation by miekiemoes, Administrators at Malwarebytes
Quote
"It simply means that one of the file associations are no longer using the default Windows setting. This could be on purpose by you or software that you use but it is also a method used by Malware so we flag it. If you're telling MBAM to change it and it comes back then some program you're using is either blocking the change in the Registry or maybe a program you use is reverting it back."
Quote
"If you chose it and want it to remain that way then you can ignore it. If you did not chose that then have MBAM fix it and if you have software that blocks Registry changes then you need to tell the program to allow MBAM to make the change".
Quote
"There is at least one tool that disables these as a "security fix" . MBAM cant tell why a modification has happened , only that it has."
explanation by Malwarebytes Staff
That said, since the userinit.exe is located in the normal default location of C:/Windows/System 32 and MBAM has already deleted the keys, I belive the reinstallation is acceptable and is merely placing the default association back. As I see it, if you run MBAM again and the Broken, Open Commmand appears and is deleted again, then there is something on your system changing the default association under one of the conditions listed above.
I am not an Outlook user, however I remember from Outlook Express (that seems so long ago) that from time to time a message would get hung up and needed to be deleted in order to restore peace to the client. I can not rememebr what I had to do to locate and delete the one message that kept trying to be sent, but once I did it - all was good.
So bottom line, I think your OPutlook problem may be caused by one corrupted email trying to be sent.
I am sure others may have other ideas. Keep us posted!