Jump to content

3.26.08 cleanup continues still?


Recommended Posts

Malwarebytes' Anti-Malware 1.27

Database version: 1128

Windows 5.1.2600 Service Pack 3

9/8/2008 6:28:54 AM

mbam-log-2008-09-08 (06-28-54).txt

Scan type: Quick Scan

Objects scanned: 43727

Time elapsed: 2 minute(s), 2 second(s)

Memory Processes Infected: 0

Memory Modules Infected: 0

Registry Keys Infected: 0

Registry Values Infected: 0

Registry Data Items Infected: 1

Folders Infected: 0

Files Infected: 0

Memory Processes Infected:

(No malicious items detected)

Memory Modules Infected:

(No malicious items detected)

Registry Keys Infected:

(No malicious items detected)

Registry Values Infected:

(No malicious items detected)

Registry Data Items Infected:

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

Folders Infected:

(No malicious items detected)

Files Infected:

(No malicious items detected)

after I hit remove selected MBAM closed and then rebooted computer and then there was no quaratine entry?

Link to post
Share on other sites

  • Staff

There was a glitch in the way we corrected this key in the past , this undoes that . The glitch would not cause any problems which is why no one had a bug report for it .

The value being set today is the value that MS installs when you install windows .

This is not actually fixing a problem , only setting a value exactly the way it would be set when windows is installed .

Link to post
Share on other sites

There was a glitch in the way we corrected this key in the past , this undoes that . The glitch would not cause any problems which is why no one had a bug report for it .

The value being set today is the value that MS installs when you install windows .

This is not actually fixing a problem , only setting a value exactly the way it would be set when windows is installed .

I had both the security program one & the broken.opencommand a few minutes ago. I downloaded the fix for the broken security command & it fixed it right away. Then I ran another scan & still have the Broken.OpenCommand showing up. What do I do with it? Is there a fix for that one? What do I do with it? I'm afraid to delete it without knowing? Thanks~

Link to post
Share on other sites

I had both the security program one & the broken.opencommand a few minutes ago. I downloaded the fix for the broken security command & it fixed it right away. Then I ran another scan & still have the Broken.OpenCommand showing up. What do I do with it? Is there a fix for that one? What do I do with it? I'm afraid to delete it without knowing? Thanks~

Did you download version 1.27 and let it run? It will fix both errors.

Link to post
Share on other sites

Let version 1.27 do its thing. Click "remove" when it finds the two registry values. Let it remove and reboot your system. Bad values will be corrected and MBAM will no longer find the bad registry values.

The fix I downloaded to my desktop & ran already fixed the broken securityprovider one, it's the broken.opencommand that is still here. The other poster said that after removing it, his Quarrantine tab was gone, will that corrupt mine too? Thanx~

Link to post
Share on other sites

Hello,

What is ultimately the good solution: to delete or not to delete the key HKEY_CLASSES_ROOT\scrfile\shell\open\command\ (Broken.OpenCommand) -> Bad: ("%1" %*) Good: ("%1" /S) ?

In advance, thanks for your reply.

I'm not sure actually. I'm not very computer savvy, that's why I'm double checking. I just want to make sure I don't mess things up, ok? Thanx~~

Link to post
Share on other sites

The fix I downloaded to my desktop & ran already fixed the broken securityprovider one, it's the broken.opencommand that is still here. The other poster said that after removing it, his Quarrantine tab was gone, will that corrupt mine too? Thanx~

I let MBAM version 1.27 fix both the broken.securityprovider and the broken.opencommand. When it found both, I selected "remove". MBAM made the correction to both, rebotted my system, and everything is running fine. I have encountered no problems such as described by others. I am running WinXP SP3 on a Dell.

Link to post
Share on other sites

Malwarebytes' Anti-Malware 1.27

Database version: 1128

Windows 5.1.2600 Service Pack 3

9/8/2008 6:28:54 AM

mbam-log-2008-09-08 (06-28-54).txt

Scan type: Quick Scan

Objects scanned: 43727

Time elapsed: 2 minute(s), 2 second(s)

Memory Processes Infected: 0

Memory Modules Infected: 0

Registry Keys Infected: 0

Registry Values Infected: 0

Registry Data Items Infected: 1

Folders Infected: 0

Files Infected: 0

Memory Processes Infected:

(No malicious items detected)

Memory Modules Infected:

(No malicious items detected)

Registry Keys Infected:

(No malicious items detected)

Registry Values Infected:

(No malicious items detected)

Registry Data Items Infected:

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

Folders Infected:

(No malicious items detected)

Files Infected:

(No malicious items detected)

after I hit remove selected MBAM closed and then rebooted computer and then there was no quaratine entry?

Ditto. MBAM doesn't actually "remove" or "quarantine" anything, it merely fixes a registry problem. Nothing will show up in the quarantine, the fix will only show up in your log filex.

Link to post
Share on other sites

I let MBAM version 1.27 fix both the broken.securityprovider and the broken.opencommand. When it found both, I selected "remove". MBAM made the correction to both, rebotted my system, and everything is running fine. I have encountered no problems such as described by others. I am running WinXP SP3 on a Dell.

Thanks, now I feel better about it. I will do that now. I was just unsure. I'm running WinXP pro SP3 on an HP. again, Thanx~

Link to post
Share on other sites

Hello,

What is ultimately the good solution: to delete or not to delete the key HKEY_CLASSES_ROOT\scrfile\shell\open\command\ (Broken.OpenCommand) -> Bad: ("%1" %*) Good: ("%1" /S) ?

In advance, thanks for your reply.

I let MBAM version 1.27 fix both the broken.securityprovider and the broken.opencommand. When it found both, I selected "remove". MBAM made the correction to both, rebotted my system, and everything is running fine. I have encountered no problems such as described by others. I am running WinXP SP3 on a Dell.

Link to post
Share on other sites

I let MBAM version 1.27 fix both the broken.securityprovider and the broken.opencommand. When it found both, I selected "remove". MBAM made the correction to both, rebotted my system, and everything is running fine. I have encountered no problems such as described by others. I am running WinXP SP3 on a Dell.

I did remove it & then rebooted & all's fine now. Clean scan! Thanx~~

Link to post
Share on other sites

  • 11 months later...
There was a glitch in the way we corrected this key in the past , this undoes that . The glitch would not cause any problems which is why no one had a bug report for it .

The value being set today is the value that MS installs when you install windows .

This is not actually fixing a problem , only setting a value exactly the way it would be set when windows is installed .

I lately have problems with my winzip, i cant unzip files, and sometimes after i run my scan it works, can you hlep me check out that one? Cause im really annoyed about my winzip :( , thanks ;) Oops, sorry forgot to mention the virus,

as far as i believe i think it is Broken.OpenCommand, help me out!! thanks

Link to post
Share on other sites

I lately have problems with my winzip, i cant unzip files, and sometimes after i run my scan it works, can you hlep me check out that one? Cause im really annoyed about my winzip :( , thanks ;) Oops, sorry forgot to mention the virus,

as far as i believe i think it is Broken.OpenCommand, help me out!! thanks

Hi and welcome to the forum! :)

Scan and post logs - read note at bottom in green

If you're having Malware related issues with your computer that you're unable to resolve.

1. Please read and follow the instructions provided here: I'm infected - What do I do now?

2. If needed please post your logs in a NEW topic here: Malware Removal - HijackThis Logs

3. When posting logs please do not use any Quote, Code, or other tags. Please copy/paste directly into your post and do not attach files unless requested.

* Please do not post any logs in the General forum. We do not work on any logs posted in the General forum.

* Please do not install any software or use any removal/scanning tool except for those you're requested to run by the Helper that will assist you.

* Using these other tools often makes the cleanup task more difficult and time consuming.

* If you have already submitted for assistance at one of the other support sites on the Internet then you should not post a new log here, you should stay working with the Helper from that site until the issue is resolved.

* Do not assume you're clean because you don't see something in the logs. Please wait until the person assisting you provides feedback.

* There are often many others that require asistance as well, so please be patient. If no one has responded within 48 hours then please go ahead and post a request for review

* NOTE: If for some reason you're unable to run some or any of the tools in the first link, then skip that step and move on to the next one. If you can't even run HijackThis, then just proceed and post a NEW topic as shown in the second link describing your issues and someone will assist you as soon as they can.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.