Start\run\regedit just removes all the icons on the desktop for a few seconds and they then re-appear.
Any help appreciated.

atandhmb wrote:

> Start\run\regedit just removes all the icons on the desktop for a few
> seconds and they then re-appear. Any help appreciated.

This is very unlikely to have been caused by a Windows Update. It sounds
much more likely that your computer is infected. Be sure it's not:

http://www.elephantboycomputers.com/...moving_Malware

However, if you're really convinced that the computer is clean and that a
Windows Update caused this, go to Add/Remove Programs, click the show all
updates box at the top, and uninstall the update(s) that you think caused
this. Don't forget to reboot. If uninstalling the update(s) solves the
issue, install them back one at a time testing after each. If you can
pinpoint the culprit, contact Microsoft for free help with this update.

Start a free Windows Update support incident request -
https://support.microsoft.com/oas/de...spx?gprid=6527
Support for Windows Update - http://support.microsoft.com/gp/wusupport

For home users, no-charge support is available by calling 1-866-PCSAFETY in
the United States and in Canada or by contacting your local Microsoft
subsidiary. There is no-charge for support calls that are associated with
security updates. When you call, clearly state that your problem is
related to a Security Update and cite the update's KB number (e.g.,
KB958644).

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ

On May 4, 7:42*am, "atandhmb" <zen18...@zen.co.uk> wrote:
> Start\run\regedit just removes all the icons on the desktop for a few seconds and they then re-appear.
> Any help appreciated.

....and what happens when you try to open Command (how do you do that
and what do you see).

Download Malwarebytes free software, update it, and run a full scan
and see what that does for you.

"Jose" <jose_ease******.com> wrote in message
news:88a2733e-0cdd-45a6-ab51-963621e9dd57@m24g2000vbp.googlegroups.com...
On May 4, 7:42 am, "atandhmb" <zen18...@zen.co.uk> wrote:
> Start\run\regedit just removes all the icons on the desktop for a few
> seconds and they then re-appear.
> Any help appreciated.

....and what happens when you try to open Command (how do you do that
and what do you see).

Very interesting: I have always used the short form, i.e. cmd.
start|run|cmd behaves in same way as Regedit (above), however
start|run|command is OK. Is there a clue anywhere here.


Download Malwarebytes free software, update it, and run a full scan
and see what that does for you.

atandhmb wrote:

>
> "Jose" <jose_ease******.com> wrote in message
> news:88a2733e-0cdd-45a6-ab51-963621e9dd57@m24g2000vbp.googlegroups.com...
> On May 4, 7:42 am, "atandhmb" <zen18...@zen.co.uk> wrote:
>> Start\run\regedit just removes all the icons on the desktop for a few
>> seconds and they then re-appear.
>> Any help appreciated.
>
> ...and what happens when you try to open Command (how do you do that
> and what do you see).
>
> Very interesting: I have always used the short form, i.e. cmd.
> start|run|cmd behaves in same way as Regedit (above), however
> start|run|command is OK. Is there a clue anywhere here.

Yes, that is a clue. Command is the older 16-bit program included in XP only
to provide backwards compatibility for older (*much* older) programs. The
correct command prompt program to use in XP is cmd.exe. Since you can't run
it, you need to follow the advice given previously by me and by Jose and
scan your computer for malware.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ

"Malke" <malke@invalid.invalid> wrote in message
news:%23IVyD0MzJHA.4272@TK2MSFTNGP06.phx.gbl...
> atandhmb wrote:
>
>>
>> "Jose" <jose_ease******.com> wrote in message
>> news:88a2733e-0cdd-45a6-ab51-963621e9dd57@m24g2000vbp.googlegroups.com...
>> On May 4, 7:42 am, "atandhmb" <zen18...@zen.co.uk> wrote:
>>> Start\run\regedit just removes all the icons on the desktop for a few
>>> seconds and they then re-appear.
>>> Any help appreciated.
>>
>> ...and what happens when you try to open Command (how do you do that
>> and what do you see).
>>
>> Very interesting: I have always used the short form, i.e. cmd.
>> start|run|cmd behaves in same way as Regedit (above), however
>> start|run|command is OK. Is there a clue anywhere here.
>
> Yes, that is a clue. Command is the older 16-bit program included in XP
> only
> to provide backwards compatibility for older (*much* older) programs. The
> correct command prompt program to use in XP is cmd.exe. Since you can't
> run
> it, you need to follow the advice given previously by me and by Jose and
> scan your computer for malware.
>
> Malke
> --
> MS-MVP
> Elephant Boy Computers - Don't Panic!
> http://www.elephantboycomputers.com/#FAQ

Thanks. I will do that. meantime I have just restored, back to 1st May. The
options I had were 1st, 2nd, 3rd and 4th May only.
Another possible clue. AVG8 will not update. I cannot bring up the message
again, but I did message to the effect that "access is forbidden by the
server". I would think that is another clue.
I have used AVG and ZoneAlarm for many years on all my computers.
Thanks again.

@malke: cf.
http://groups.google.com/group/micro...0bd8561379794b

Better yet, read the thread in your newsreader as all posts were HTML.

Subject: XP Pro Microsoft Updates reverting messages folder back to default
NGs: OE General; OE6
--
~Robear

Malke wrote:
> atandhmb wrote:
>
>> Start\run\regedit just removes all the icons on the desktop for a few
>> seconds and they then re-appear. Any help appreciated.
>
> This is very unlikely to have been caused by a Windows Update. It sounds
> much more likely that your computer is infected. Be sure it's not:
>
> http://www.elephantboycomputers.com/...moving_Malware
>
> However, if you're really convinced that the computer is clean and that a
> Windows Update caused this, go to Add/Remove Programs, click the show all
> updates box at the top, and uninstall the update(s) that you think caused
> this. Don't forget to reboot. If uninstalling the update(s) solves the
> issue, install them back one at a time testing after each. If you can
> pinpoint the culprit, contact Microsoft for free help with this update.
>
> Start a free Windows Update support incident request -
> https://support.microsoft.com/oas/de...spx?gprid=6527
> Support for Windows Update - http://support.microsoft.com/gp/wusupport
>
> For home users, no-charge support is available by calling 1-866-PCSAFETY
> in
> the United States and in Canada or by contacting your local Microsoft
> subsidiary. There is no-charge for support calls that are associated with
> security updates. When you call, clearly state that your problem is
> related to a Security Update and cite the update's KB number (e.g.,
> KB958644).
>
> Malke

atandhmb wrote:
> "Malke" <malke@invalid.invalid> wrote in message
> news:%23IVyD0MzJHA.4272@TK2MSFTNGP06.phx.gbl...
>> atandhmb wrote:
>>
>>>
>>> "Jose" <jose_ease******.com> wrote in message
>>> news:88a2733e-0cdd-45a6-ab51-963621e9dd57@m24g2000vbp.googlegroups.com...
>>> On May 4, 7:42 am, "atandhmb" <zen18...@zen.co.uk> wrote:
>>>> Start\run\regedit just removes all the icons on the desktop for a few
>>>> seconds and they then re-appear.
>>>> Any help appreciated.
>>>
>>> ...and what happens when you try to open Command (how do you do that
>>> and what do you see).
>>>
>>> Very interesting: I have always used the short form, i.e. cmd.
>>> start|run|cmd behaves in same way as Regedit (above), however
>>> start|run|command is OK. Is there a clue anywhere here.
>>
>> Yes, that is a clue. Command is the older 16-bit program included in XP
>> only
>> to provide backwards compatibility for older (*much* older) programs. The
>> correct command prompt program to use in XP is cmd.exe. Since you can't
>> run
>> it, you need to follow the advice given previously by me and by Jose and
>> scan your computer for malware.
>>
>> Malke
>> --
>> MS-MVP
>> Elephant Boy Computers - Don't Panic!
>> http://www.elephantboycomputers.com/#FAQ
>
> Thanks. I will do that. meantime I have just restored, back to 1st May.
> The
> options I had were 1st, 2nd, 3rd and 4th May only.
> Another possible clue. AVG8 will not update. I cannot bring up the message
> again, but I did message to the effect that "access is forbidden by the
> server". I would think that is another clue.
> I have used AVG and ZoneAlarm for many years on all my computers.
> Thanks again.

You've definitely got a hijackware infection on your hands! You should NOT
use System Restore as a workaround for these problems.
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002

PA Bear [MS MVP] wrote:

> @malke: cf.
>
http://groups.google.com/group/micro...0bd8561379794b
>
> Better yet, read the thread in your newsreader as all posts were HTML.
>
> Subject: XP Pro Microsoft Updates reverting messages folder back to
> default NGs: OE General; OE6

Thanks, Robear. Lordy, I hate when posters do this. He's now got tons of
people working on his issue in two separate places. And he's still not
taking care of bidness. [sigh]

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ

Malke wrote:
> PA Bear [MS MVP] wrote:
>
>> @malke: cf.
>>
> http://groups.google.com/group/micro...0bd8561379794b
>>
>> Better yet, read the thread in your newsreader as all posts were HTML.
>>
>> Subject: XP Pro Microsoft Updates reverting messages folder back to
>> default NGs: OE General; OE6
>
> Thanks, Robear. Lordy, I hate when posters do this. He's now got tons of
> people working on his issue in two separate places. And he's still not
> taking care of bidness. [sigh]

@htandhmb: Post any/all further follow-up in a reply to *this* thread only.
(Plain Text preferred.)
--
~PA Bear

"PA Bear [MS MVP]" <PABearMVP******.com> wrote in message
news:%23FEn4ZPzJHA.480@TK2MSFTNGP06.phx.gbl...
> Malke wrote:
>> PA Bear [MS MVP] wrote:
>>
>>> @malke: cf.
>>>
>> http://groups.google.com/group/micro...0bd8561379794b
>>>
>>> Better yet, read the thread in your newsreader as all posts were HTML.
>>>
>>> Subject: XP Pro Microsoft Updates reverting messages folder back to
>>> default NGs: OE General; OE6
>>
>> Thanks, Robear. Lordy, I hate when posters do this. He's now got tons of
>> people working on his issue in two separate places. And he's still not
>> taking care of bidness. [sigh]
>
This was originally posted on the OE site as the problem as perceived by me
was OE.
When it became obvious that it was more appropriate to the "XP" site I then
raised it here some 3 days later.
If you take the trouble to read my first post on this site, you will note I
make no mention of OE issues and give very specific information.
I have posted 3 times here with facts, which incidentally still hold.
I have posted replies to the OE site as a matter of courtesy to P A Bear who
has given time to my problem.
And, incidentally, I have been following advice. As a start, last night I
ran the Windows Live One Care safety scanner, but this proved unsuccessful.
This was following P A Bears advice and I will follow in order what he has
suggested.
I had hoped the message from AVG Update - "access is forbidden by the
server" might have provided a clue.
If I am doing something wrong I am happy to fall in line with any reasonable
suggestion as I do appreciate the time that knowledgeable people give to
helping others who are struggling, but don't forget that it is natural to
follow one's own inclinations as well.
Incidentally, what is "bidness".
@htandhmb: Post any/all further follow-up in a reply to *this* thread only.
> (Plain Text preferred.)
> --
> ~PA Bear

atandhmb wrote:

Snip all else except the relevant bit:

> Incidentally, what is "bidness".

It means that numerous people have given you very specific troubleshooting
steps and you haven't done them.

My original post to you said for you to do two separate troubleshooting
paths:

1. Make sure the computer is 100% virus/malware-free.
http://www.elephantboycomputers.com/...moving_Malware

My steps are very thorough, require a fair amount of prep work, and also
require getting various tools/updates from a known-clean machine. Perhaps
I've missed it in this overly-long thread, but I don't see where you've
done this.

Scanning for malware must be a) systematic; and b) thorough or you don't
know if you are working from a clean base. Scanning with an online scanner
doesn't cut it as far as I'm concerned. PA Bear wanted you to start there
(I don't include online scanners in my malware removal process but I
respect that he does) but the operating words in that sentence are "start
there". Simply attempting an online scan - which you couldn't complete -
isn't enough. The fact that you couldn't complete it is in itself a clue
that the machine could be infected.

And the AVG message just tells us something is wrong and the first thing to
determine when your antivirus says something is wrong is whether the
something that is wrong is caused by malware infection. That coupled with
the inability to run cmd and regedit points to infection. In all my many
years as a professional computer tech, I've never seen a Windows Update
disable cmd and regedit and but I have seen viruses/malware do it many,
many times.

2. If the computer is proved to be completely clean - and *only* after that
has happened - uninstall the updates that you think caused the issue and
test. If all is well, then install the updates one at a time testing after
each change.

Because you haven't done any of this and *reported back the results*, we
can't go forward with more troubleshooting. And that is what I meant when I
said you weren't taking care of "bidness" (business).

If you can't do the work yourself - and there is no shame in admitting this
isn't your cup of tea - take the machine to a professional computer tech
for diagnosis and repair. I don't recommend using a
BigComputerStore/GeekSquad type of place.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ

Seconded.
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002

Malke wrote:
> atandhmb wrote:
>
> Snip all else except the relevant bit:
>
>> Incidentally, what is "bidness".
>
> It means that numerous people have given you very specific troubleshooting
> steps and you haven't done them.
>
> My original post to you said for you to do two separate troubleshooting
> paths:
>
> 1. Make sure the computer is 100% virus/malware-free.
> http://www.elephantboycomputers.com/...moving_Malware
>
> My steps are very thorough, require a fair amount of prep work, and also
> require getting various tools/updates from a known-clean machine. Perhaps
> I've missed it in this overly-long thread, but I don't see where you've
> done this.
>
> Scanning for malware must be a) systematic; and b) thorough or you don't
> know if you are working from a clean base. Scanning with an online scanner
> doesn't cut it as far as I'm concerned. PA Bear wanted you to start there
> (I don't include online scanners in my malware removal process but I
> respect that he does) but the operating words in that sentence are "start
> there". Simply attempting an online scan - which you couldn't complete -
> isn't enough. The fact that you couldn't complete it is in itself a clue
> that the machine could be infected.
>
> And the AVG message just tells us something is wrong and the first thing
> to
> determine when your antivirus says something is wrong is whether the
> something that is wrong is caused by malware infection. That coupled with
> the inability to run cmd and regedit points to infection. In all my many
> years as a professional computer tech, I've never seen a Windows Update
> disable cmd and regedit and but I have seen viruses/malware do it many,
> many times.
>
> 2. If the computer is proved to be completely clean - and *only* after
> that
> has happened - uninstall the updates that you think caused the issue and
> test. If all is well, then install the updates one at a time testing after
> each change.
>
> Because you haven't done any of this and *reported back the results*, we
> can't go forward with more troubleshooting. And that is what I meant when
> I
> said you weren't taking care of "bidness" (business).
>
> If you can't do the work yourself - and there is no shame in admitting
> this
> isn't your cup of tea - take the machine to a professional computer tech
> for diagnosis and repair. I don't recommend using a
> BigComputerStore/GeekSquad type of place.
>
> Malke

On May 5, 9:35*am, "atandhmb" <zen18...@zen.co.uk> wrote:
> "PA Bear [MS MVP]" <PABear...******.com> wrote in messagenews:%23FEn4ZPzJHA.480@TK2MSFTNGP06.phx.gbl ...
>
> > Malke wrote:
> >> PA Bear [MS MVP] wrote:
>
> >>> @malke: cf.
>
> >>http://groups.google.com/group/micro...express.genera....
>
> >>> Better yet, read the thread in your newsreader as all posts were HTML..
>
> >>> Subject: XP Pro Microsoft Updates reverting messages folder back to
> >>> default NGs: OE General; OE6
>
> >> Thanks, Robear. Lordy, I hate when posters do this. He's now got tons of
> >> people working on his issue in two separate places. And he's still not
> >> taking care of bidness. [sigh]
>
> This was originally posted on the OE site as the problem as perceived by me
> was OE.
> When it became obvious that it was more appropriate to the "XP" site I then
> raised it here some 3 days later.
> If you take the trouble to read my first post on this site, you will noteI
> make no mention of OE issues and give very specific information.
> I have posted 3 times here with facts, which incidentally still hold.
> I have posted replies to the OE site as a matter of courtesy to P A Bear who
> has given time to my problem.
> And, incidentally, I have been following advice. As a start, last night I
> ran the Windows Live One Care safety scanner, but this proved unsuccessful.
> This was following P A Bears advice and I will follow in order what he has
> suggested.
> I had hoped the message from AVG Update - "access is forbidden by the
> server" might have provided a clue.
> If I am doing something wrong I am happy to fall in line with any reasonable
> suggestion as I do appreciate the time that knowledgeable people give to
> helping others who are struggling, but don't forget that it is natural to
> follow one's own inclinations as well.
> Incidentally, what is "bidness".
> @htandhmb: Post any/all further follow-up in a reply to *this* thread only.
>
> > (Plain Text preferred.)
> > --
> > ~PA Bear

If you do a Google search for: cmd and regedit don't work

you will get some hits. Some more interesting that others and some
are quite useless, but look at the ones like this from
bleepingcomputer.com:

http://www.bleepingcomputer.com/foru...p/t221879.html

These sufferers have also tried many things with your similar or
exactly problem to no avail.

There is another post that has the user run ComboFix and his (your)
problem was solved. I think they may have sent a PM (Private Message)
or two that is not in some of the posts, but they have your esact
problem, tried a lot of things and these bleeping people got them
running.

The helpers there will look at your Hijack and ComboFix reports and
seem to do quite a detailed analysis and lots of easy to follow
instructions, they seem very patient, but you have to register and all
that stuff to get help and I don't have your problem...

If I were you, I think I would try these people. It would be most
helpful to know later what fixes your problem.

Do NOT use ComboFix without expert guidance!!

Jose wrote:
<snip>
> There is another post that has the user run ComboFix and his (your)
> problem was solved...