Jump to content

Registry Question: Broken Open Command


Recommended Posts

Guest Gruff the Elder
Posted

I scanned my XP Pro sp3 system with MalwareBytes AntiMalware and got the

following hit: "Broken.OpenCommand". The detail indicated a problem with the

registry entry at HKClasses_Root\scrfile\shell\open\command\

 

Under the column heading "Other" MB further indicated:

Bad ("%1" %*) Good ("%1" /S)

 

When I used regedit to look at this key, the value (REG_SZ) is indeed "%1" %*

 

So I infer that MB is saying that the value of this key should be changed to

"1%" /S

 

What does this key do; why is the first value bad; and should I change it to

the second value?

  • Replies 8
  • Created
  • Last Reply
Posted

RE: Registry Question: Broken Open Command

 

 

 

"Gruff the Elder" wrote:

> I scanned my XP Pro sp3 system with MalwareBytes AntiMalware and got the

> following hit: "Broken.OpenCommand". The detail indicated a problem with the

> registry entry at HKClasses_Root\scrfile\shell\open\command\

>

> Under the column heading "Other" MB further indicated:

> Bad ("%1" %*) Good ("%1" /S)

>

> When I used regedit to look at this key, the value (REG_SZ) is indeed "%1" %*

>

> So I infer that MB is saying that the value of this key should be changed to

> "1%" /S

>

> What does this key do; why is the first value bad; and should I change it to

> the second value?

 

Why you need to play with the registry and MalwareBytes can fix it for you!

http://www.malwarebytes.org/forums/lofiversion/index.php/t6195.html

let MalwareBytes fix it and run another scan to see if it will be picked

up again.

HTH,

nass

---

http://www.nasstec.co.uk

Guest Gruff the Elder
Posted

RE: Registry Question: Broken Open Command

 

"nass" wrote:

>

>

> "Gruff the Elder" wrote:

>

> > I scanned my XP Pro sp3 system with MalwareBytes AntiMalware and got the

> > following hit: "Broken.OpenCommand". The detail indicated a problem with the

> > registry entry at HKClasses_Root\scrfile\shell\open\command\

> >

> > Under the column heading "Other" MB further indicated:

> > Bad ("%1" %*) Good ("%1" /S)

> >

> > When I used regedit to look at this key, the value (REG_SZ) is indeed "%1" %*

> >

> > So I infer that MB is saying that the value of this key should be changed to

> > "1%" /S

> >

> > What does this key do; why is the first value bad; and should I change it to

> > the second value?

>

> Why you need to play with the registry and MalwareBytes can fix it for you!

> http://www.malwarebytes.org/forums/lofiversion/index.php/t6195.html

> let MalwareBytes fix it and run another scan to see if it will be picked

> up again.

> HTH,

> nass

> ---

> http://www.nasstec.co.uk

>

>

 

How nice of you to answer my questions. I suppose you also regularly run

registry cleaners and permit them to delete whatever registry entries they

claim are "bad".

Posted

RE: Registry Question: Broken Open Command

 

 

 

"Gruff the Elder" wrote:

> "nass" wrote:

>

> >

> >

> > "Gruff the Elder" wrote:

> >

> > > I scanned my XP Pro sp3 system with MalwareBytes AntiMalware and got the

> > > following hit: "Broken.OpenCommand". The detail indicated a problem with the

> > > registry entry at HKClasses_Root\scrfile\shell\open\command\

> > >

> > > Under the column heading "Other" MB further indicated:

> > > Bad ("%1" %*) Good ("%1" /S)

> > >

> > > When I used regedit to look at this key, the value (REG_SZ) is indeed "%1" %*

> > >

> > > So I infer that MB is saying that the value of this key should be changed to

> > > "1%" /S

> > >

> > > What does this key do; why is the first value bad; and should I change it to

> > > the second value?

> >

> > Why you need to play with the registry and MalwareBytes can fix it for you!

> > http://www.malwarebytes.org/forums/lofiversion/index.php/t6195.html

> > let MalwareBytes fix it and run another scan to see if it will be picked

> > up again.

> > HTH,

> > nass

> > ---

> > http://www.nasstec.co.uk

> >

> >

>

> How nice of you to answer my questions. I suppose you also regularly run

> registry cleaners and permit them to delete whatever registry entries they

> claim are "bad".

 

Just after checking what they are and if not sure if they are not orphans

left from old applications I uninstalled or doesn't exist anymore on the

machine!

 

This(scrfile) refer to a screensaver installed and may be fishy one or badly

written/programmed.

HTH,

nass

----

http://www.nasstec.co.uk

Guest Mick Murphy
Posted

RE: Registry Question: Broken Open Command

 

Gruff the Elder, this NASS is a FAKE.

Totally ignore him, and his shonky and shoddy computer repair business.

 

Do NOT click on his website address!!!!

Virus loaded.

He is a Scammer trolling here.

 

--

Mad Mike

 

 

"Gruff the Elder" wrote:

> "nass" wrote:

>

> >

> >

> > "Gruff the Elder" wrote:

> >

> > > I scanned my XP Pro sp3 system with MalwareBytes AntiMalware and got the

> > > following hit: "Broken.OpenCommand". The detail indicated a problem with the

> > > registry entry at HKClasses_Root\scrfile\shell\open\command\

> > >

> > > Under the column heading "Other" MB further indicated:

> > > Bad ("%1" %*) Good ("%1" /S)

> > >

> > > When I used regedit to look at this key, the value (REG_SZ) is indeed "%1" %*

> > >

> > > So I infer that MB is saying that the value of this key should be changed to

> > > "1%" /S

> > >

> > > What does this key do; why is the first value bad; and should I change it to

> > > the second value?

> >

> > Why you need to play with the registry and MalwareBytes can fix it for you!

> > http://www.malwarebytes.org/forums/lofiversion/index.php/t6195.html

> > let MalwareBytes fix it and run another scan to see if it will be picked

> > up again.

> > HTH,

> > nass

> > ---

> > http://www.nasstec.co.uk

> >

> >

>

> How nice of you to answer my questions. I suppose you also regularly run

> registry cleaners and permit them to delete whatever registry entries they

> claim are "bad".

Guest Mick Murphy
Posted

RE: Registry Question: Broken Open Command

 

 

And Also I'm a nasty old fart when I get CRANKED UP!!!

Be WARNED, faggot!!!!

You are a small mosquito.

--

Mad Mike

 

"Mick Murphy" wrote:

> Gruff the Elder, this NASS is a FAKE.

> Totally ignore him, and his shonky and shoddy computer repair business.

>

> Do NOT click on his website address!!!!

> Virus loaded.

> He is a Scammer trolling here.

>

> --

> Mad Mike

>

>

> "Gruff the Elder" wrote:

>

> > "nass" wrote:

> >

> > >

> > >

> > > "Gruff the Elder" wrote:

> > >

> > > > I scanned my XP Pro sp3 system with MalwareBytes AntiMalware and got the

> > > > following hit: "Broken.OpenCommand". The detail indicated a problem with the

> > > > registry entry at HKClasses_Root\scrfile\shell\open\command\

> > > >

> > > > Under the column heading "Other" MB further indicated:

> > > > Bad ("%1" %*) Good ("%1" /S)

> > > >

> > > > When I used regedit to look at this key, the value (REG_SZ) is indeed "%1" %*

> > > >

> > > > So I infer that MB is saying that the value of this key should be changed to

> > > > "1%" /S

> > > >

> > > > What does this key do; why is the first value bad; and should I change it to

> > > > the second value?

> > >

> > > Why you need to play with the registry and MalwareBytes can fix it for you!

> > > http://www.malwarebytes.org/forums/lofiversion/index.php/t6195.html

> > > let MalwareBytes fix it and run another scan to see if it will be picked

> > > up again.

> > > HTH,

> > > nass

> > > ---

> > > http://www.nasstec.co.uk

> > >

> > >

> >

> > How nice of you to answer my questions. I suppose you also regularly run

> > registry cleaners and permit them to delete whatever registry entries they

> > claim are "bad".

Guest Mick Murphy
Posted

RE: Registry Question: Broken Open Command

 

You claim to be the "smart" computer man here.

Pick the fake posts, idiot!

--

Mad Mike

 

 

"nass" wrote:

>

>

> "Gruff the Elder" wrote:

>

> > "nass" wrote:

> >

> > >

> > >

> > > "Gruff the Elder" wrote:

> > >

> > > > I scanned my XP Pro sp3 system with MalwareBytes AntiMalware and got the

> > > > following hit: "Broken.OpenCommand". The detail indicated a problem with the

> > > > registry entry at HKClasses_Root\scrfile\shell\open\command\

> > > >

> > > > Under the column heading "Other" MB further indicated:

> > > > Bad ("%1" %*) Good ("%1" /S)

> > > >

> > > > When I used regedit to look at this key, the value (REG_SZ) is indeed "%1" %*

> > > >

> > > > So I infer that MB is saying that the value of this key should be changed to

> > > > "1%" /S

> > > >

> > > > What does this key do; why is the first value bad; and should I change it to

> > > > the second value?

> > >

> > > Why you need to play with the registry and MalwareBytes can fix it for you!

> > > http://www.malwarebytes.org/forums/lofiversion/index.php/t6195.html

> > > let MalwareBytes fix it and run another scan to see if it will be picked

> > > up again.

> > > HTH,

> > > nass

> > > ---

> > > http://www.nasstec.co.uk

> > >

> > >

> >

> > How nice of you to answer my questions. I suppose you also regularly run

> > registry cleaners and permit them to delete whatever registry entries they

> > claim are "bad".

>

> Just after checking what they are and if not sure if they are not orphans

> left from old applications I uninstalled or doesn't exist anymore on the

> machine!

>

> This(scrfile) refer to a screensaver installed and may be fishy one or badly

> written/programmed.

> HTH,

> nass

> ----

> http://www.nasstec.co.uk

>

Guest Mick Murphy
Posted

Re: Registry Question: Broken Open Command

 

OOPS!!!!!!

Lost it there. I thought I had myself under control.

I've been doing SO good too!!

I'll try to do better.

Really. I promise. No more name-calling.

No more lies (about nass' site loaded with virus)

--

Bad Mike

 

 

I wrote:

>And Also I'm a nasty old fart when I get CRANKED UP!!!

>Be WARNED, faggot!!!!

>You are a small mosquito.

>--

>Mad Mike

>

>"Mick Murphy" wrote:

Posted

Re: Registry Question: Broken Open Command

 

Many Windows screen savers come with an .SCR extension

by default. Usually these will be found in the Windows main

directory. Use caution if you receive a screen saver file

via E-mail. These files can contain executable code and

can be worms or viruses.

 

Note: This file type can become infected and should be

carefully scanned if someone sends you a file with this

extension.

 

MalwareBytes is correct, let it change it.

 

 

ju.c

 

 

"Gruff the Elder" <GrufftheElder@discussions.microsoft.com> wrote in message

news:2563C8DE-E296-4CAA-8E96-9818A355C116@microsoft.com...

> I scanned my XP Pro sp3 system with MalwareBytes AntiMalware and got the

> following hit: "Broken.OpenCommand". The detail indicated a problem with the

> registry entry at HKClasses_Root\scrfile\shell\open\command\

>

> Under the column heading "Other" MB further indicated:

> Bad ("%1" %*) Good ("%1" /S)

>

> When I used regedit to look at this key, the value (REG_SZ) is indeed "%1" %*

>

> So I infer that MB is saying that the value of this key should be changed to

> "1%" /S

>

> What does this key do; why is the first value bad; and should I change it to

> the second value?

>

>


×
×
  • Create New...