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.
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).
Re: XP Pro: Following MS updates, now unable to open Regedit orCommand
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.
Re: XP Pro: Following MS updates, now unable to open Regedit or Command
"Jose" <jose_ease@yahoo.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.
Re: XP Pro: Following MS updates, now unable to open Regedit or Command
atandhmb wrote:
>
> "Jose" <jose_ease@yahoo.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.
Re: XP Pro: Following MS updates, now unable to open Regedit or Command
"Malke" <malke@invalid.invalid> wrote in message
news:%23IVyD0MzJHA.4272@TK2MSFTNGP06.phx.gbl...
> atandhmb wrote:
>
>>
>> "Jose" <jose_ease@yahoo.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.
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
Re: XP Pro: Following MS updates, now unable to open Regedit or Command
atandhmb wrote:
> "Malke" <malke@invalid.invalid> wrote in message
> news:%23IVyD0MzJHA.4272@TK2MSFTNGP06.phx.gbl...
>> atandhmb wrote:
>>
>>>
>>> "Jose" <jose_ease@yahoo.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
Re: XP Pro: Following MS updates, now unable to open Regedit or Command
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]
Re: XP Pro: Following MS updates, now unable to open Regedit or Command
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