Windows Explorer.exe Crashing

Mine is doing the same thing to me everytime I try and
right-click the C drive and then properties. I thought it
was just my computer but I'm glad to know it's not. Sorry
I couldn't help but maybe it added a little more info for
the people who know how to fix it.






-----Original Message-----
I just found out that Windows explorer.exe also crashes
if I try to do any
sharing operation.

Harold


"Harold" wrote in message
...
I have always used Windows explorer.exe to open
multiple files at the same
time by highlighting them, right clicking, and
choosing "Open." Never any
problems doing this until after installing XP's SP2
build 2162. Now when I
do the same procedure the files open but Windows
explorer.exe crashes
wanting to send a message to Microsoft and then it
closes down. My files
remain open but Windows explorer.exe shuts down. I
have tried doing a sfc
/scannow and boy was that a fiasco. In any case, it
didn't find any file
to replace but I'm not sure it was an accurate run but
that is a whole
other story.



Any suggestions on how to fix Windows explorer.exe
short of uninstalling
SP2?



Thanks



Harold




.

Harold--

I'm going to assume because you posted here and not in the Beta groups that
you have 2162 from one of the Beta sites like Neowin, Bink Nu, or MSFN that
always leak builds after MSFT has gone public with a beta of some app, and
in this case MSFT went public with RC2 (2149) the first week of June. I
have a suggestion way short of formatting your box and I don't think you are
seeing a legitimate beta bug that's reproducable on that box with your right
click problem. That problem is not unknown and right click problems and
sharing problems and the explorer problems you and silversparkle mention
show up not infrequently on xp groups.

So I would definitely not label that an SP2 problem --I'd label it a problem
with that particular OS on that particular box that you chose to install
2162 on. I bet if you download that to one of your other machines you don't
see the problem and then you begin to increase your statistical test pool by
a factor of 100%--one box with the problems and one box without.

Here's what I suggest:

1) Uninstall SP2 at Add/Remove. Since the Beta testers have to uninstall to
reinstall the new builds every time MSFT Beta tests anything that is what
they have asked to be done for years and they certainly do with the public
Beta RC2 on the Technet site, they have pretty carefully crafted an
uninstall that works although I'm sure with any Beta there could be problems
with uninstalls and installs. Having said that, I don't really believe RTM
is anything ever but a refined Beta in any Windows OS. That's why there are
these newsgroups with all the good help I get on them.

2) Now you'll be back to XP out of the box or probably if you're like most
people, XPSP1. Run SFC /purge cache (takes 5 seconds) then run SFC/Scannow
on that SP1 box. You will be prompted for your CD I believe, because by
default the registry points to the CD. Also SFC is not going to give you
the customary "attaboy" that you've run it successfully on that progress bar
on your desktop. You have to go to Event Viewer in Applications or Systems
and look for the entry "Windows File Protection" at the time you ran it.
The attaboy is hidden over in Event Viewer for SFC.

*Then you can do one of two things:*

3) You can then try SP2 on that box again. Or you can do what I'd probably
do and after you Run SFC, I'd do a repair install or what MSFT calls an
upgrade install only you are upgrading from your OS. It works wonderfully
well, but there is always the caveat that you don't have 100% guarantee that
you may not lose some information so do a current Back Up and a back up is
always an important step if you are going to play with a Beta--even the
later pubic beta RC2 or the one of these leaks from the Beta sites like
Neowin.

I believe a repair/upgrade install is going to fix that box so you can run
SP2 on it. In the 3rd week of August or thereabouts, SP2 is going RTM.

I would not go to the Recovery Console on that box with the 4 most commonly
used repair moves at RC because the RC should be respected as more of a last
ditch tool, perhaps with the exception of running chkdsk /r from it unless
you are one who is very experienced with a n umber of commands in it.

The more extreme step is to format that box, but I don't think you have to
do that at all at this point.

This is from a nice site from one of the MSFT XP MVP's:

http://www.michaelstevenstech.com/XPrepairinstall.htm

and this is the MSKB on a Repair versus Parallel Install:
How to install or upgrade to Windows XP
http://support.microsoft.com/default...&Product=winxp

I much prefer a *repair or upgrade* install to a parallel install because
the repair install will restore your settings perfectly and a parallel
install to another drive or another folder on your OS drive will be much
more inconvenient and have you trying to get your data out of it.

Good luck and post up what you do,

Chad Harris
__________________________________________________ _____________


"Harold" wrote in message
...
I have always used Windows explorer.exe to open multiple files at the same
time by highlighting them, right clicking, and choosing "Open." Never any
problems doing this until after installing XP's SP2 build 2162. Now when I
do the same procedure the files open but Windows explorer.exe crashes
wanting to send a message to Microsoft and then it closes down. My files
remain open but Windows explorer.exe shuts down. I have tried doing a sfc
/scannow and boy was that a fiasco. In any case, it didn't find any file
to replace but I'm not sure it was an accurate run but that is a whole
other story.



Any suggestions on how to fix Windows explorer.exe short of uninstalling
SP2?



Thanks



Harold

Thanks Chad. I'll try what I can. Did you see silversparkles reply?

"Chad Harris" wrote in message
...
Harold--

I'm going to assume because you posted here and not in the Beta groups
that
you have 2162 from one of the Beta sites like Neowin, Bink Nu, or MSFN
that
always leak builds after MSFT has gone public with a beta of some app,
and
in this case MSFT went public with RC2 (2149) the first week of June. I
have a suggestion way short of formatting your box and I don't think you
are
seeing a legitimate beta bug that's reproducable on that box with your
right
click problem. That problem is not unknown and right click problems and
sharing problems and the explorer problems you and silversparkle mention
show up not infrequently on xp groups.

So I would definitely not label that an SP2 problem --I'd label it a
problem
with that particular OS on that particular box that you chose to install
2162 on. I bet if you download that to one of your other machines you
don't
see the problem and then you begin to increase your statistical test pool
by
a factor of 100%--one box with the problems and one box without.

Here's what I suggest:

1) Uninstall SP2 at Add/Remove. Since the Beta testers have to uninstall
to
reinstall the new builds every time MSFT Beta tests anything that is what
they have asked to be done for years and they certainly do with the public
Beta RC2 on the Technet site, they have pretty carefully crafted an
uninstall that works although I'm sure with any Beta there could be
problems
with uninstalls and installs. Having said that, I don't really believe
RTM
is anything ever but a refined Beta in any Windows OS. That's why there
are
these newsgroups with all the good help I get on them.

2) Now you'll be back to XP out of the box or probably if you're like most
people, XPSP1. Run SFC /purge cache (takes 5 seconds) then run
SFC/Scannow
on that SP1 box. You will be prompted for your CD I believe, because by
default the registry points to the CD. Also SFC is not going to give you
the customary "attaboy" that you've run it successfully on that progress
bar
on your desktop. You have to go to Event Viewer in Applications or
Systems
and look for the entry "Windows File Protection" at the time you ran it.
The attaboy is hidden over in Event Viewer for SFC.

*Then you can do one of two things:*

3) You can then try SP2 on that box again. Or you can do what I'd
probably
do and after you Run SFC, I'd do a repair install or what MSFT calls an
upgrade install only you are upgrading from your OS. It works wonderfully
well, but there is always the caveat that you don't have 100% guarantee
that
you may not lose some information so do a current Back Up and a back up is
always an important step if you are going to play with a Beta--even the
later pubic beta RC2 or the one of these leaks from the Beta sites like
Neowin.

I believe a repair/upgrade install is going to fix that box so you can run
SP2 on it. In the 3rd week of August or thereabouts, SP2 is going RTM.

I would not go to the Recovery Console on that box with the 4 most
commonly
used repair moves at RC because the RC should be respected as more of a
last
ditch tool, perhaps with the exception of running chkdsk /r from it unless
you are one who is very experienced with a n umber of commands in it.

The more extreme step is to format that box, but I don't think you have to
do that at all at this point.

This is from a nice site from one of the MSFT XP MVP's:

http://www.michaelstevenstech.com/XPrepairinstall.htm

and this is the MSKB on a Repair versus Parallel Install:
How to install or upgrade to Windows XP

http://support.microsoft.com/default...&Product=winxp

I much prefer a *repair or upgrade* install to a parallel install because
the repair install will restore your settings perfectly and a parallel
install to another drive or another folder on your OS drive will be much
more inconvenient and have you trying to get your data out of it.

Good luck and post up what you do,

Chad Harris
__________________________________________________ _____________


"Harold" wrote in message
...
I have always used Windows explorer.exe to open multiple files at the
same
time by highlighting them, right clicking, and choosing "Open." Never
any
problems doing this until after installing XP's SP2 build 2162. Now when
I
do the same procedure the files open but Windows explorer.exe crashes
wanting to send a message to Microsoft and then it closes down. My files
remain open but Windows explorer.exe shuts down. I have tried doing a
sfc
/scannow and boy was that a fiasco. In any case, it didn't find any file
to replace but I'm not sure it was an accurate run but that is a whole
other story.



Any suggestions on how to fix Windows explorer.exe short of uninstalling
SP2?



Thanks



Harold

Harold--

1) I saw Silversparkle's reply. *He hasn't downloaded SP2 yet* and he's
having a similar problem. Did you see the google threads? There are
*hundreds of people* that have had right click problems of all stripes and
right click problems exactly like yours when doing various right click
actions with Windows Explorer and their files that don't have anything to do
with XP SP2.

Many of thoser right click problems have been around since Windows 95.

If you go to google groups with the same search words I used to get the Tiny
URL links I gave you, you will realize that.

2) If you aren't beta testing, you can still participate in the MSFT public
beta forums here, and all of the beta sites are discussing SP2 widely as are
other forums since it went Beta and you can look to see if this is a
frequent bug report in those places, but it does not seem to be the case.


3) From that error it appears your problem has nothing whatsoever to do with
Windows XP SP2, but instead is because on that box before you put on SP2 you
had an unstable browser extension some program brought in using using
RJHExtensions Organizer. You don't have to have a program remotely with that
name to have it. I'll bet if you do some looking on that box you will prove
to yourself once and for all that your problem is a BHO extension. It may
be possible that XP SP2's security buttoning down doesn't agree with this
app if you have it and then you've got a choice. You can use SP2, you can
continue with SP1 until the next service pack or Longhorn or XP reloaded, or
find a work around by contacting them at
http://www.rjhsoftware.com/contact.html

http://www.rjhsoftware.com/rjhextensions/


http://www.rjhsoftware.com/rjhextensions/rjhext.htm

3) I'd do a thorough search in your downloaded program files where I told
you to look for this BHO. I'd do a thorough spy scan.

A BHO and how to deal with them are defined he

Browser Helper Extensions
http://tinyurl.com/47dl3

See:

http://www.freelists.org/archives/pc.../msg00383.html

Best,

Chad harris

__________________________________________________


"Harold" wrote in message
...
Thanks Chad. I'll try what I can. Did you see silversparkles reply?

"Chad Harris" wrote in message
...
Harold--

I'm going to assume because you posted here and not in the Beta groups
that
you have 2162 from one of the Beta sites like Neowin, Bink Nu, or MSFN
that
always leak builds after MSFT has gone public with a beta of some app,
and
in this case MSFT went public with RC2 (2149) the first week of June. I
have a suggestion way short of formatting your box and I don't think you
are
seeing a legitimate beta bug that's reproducable on that box with your
right
click problem. That problem is not unknown and right click problems and
sharing problems and the explorer problems you and silversparkle mention
show up not infrequently on xp groups.

So I would definitely not label that an SP2 problem --I'd label it a
problem
with that particular OS on that particular box that you chose to install
2162 on. I bet if you download that to one of your other machines you
don't
see the problem and then you begin to increase your statistical test pool
by
a factor of 100%--one box with the problems and one box without.

Here's what I suggest:

1) Uninstall SP2 at Add/Remove. Since the Beta testers have to uninstall
to
reinstall the new builds every time MSFT Beta tests anything that is what
they have asked to be done for years and they certainly do with the
public
Beta RC2 on the Technet site, they have pretty carefully crafted an
uninstall that works although I'm sure with any Beta there could be
problems
with uninstalls and installs. Having said that, I don't really believe
RTM
is anything ever but a refined Beta in any Windows OS. That's why there
are
these newsgroups with all the good help I get on them.

2) Now you'll be back to XP out of the box or probably if you're like
most
people, XPSP1. Run SFC /purge cache (takes 5 seconds) then run
SFC/Scannow
on that SP1 box. You will be prompted for your CD I believe, because by
default the registry points to the CD. Also SFC is not going to give you
the customary "attaboy" that you've run it successfully on that progress
bar
on your desktop. You have to go to Event Viewer in Applications or
Systems
and look for the entry "Windows File Protection" at the time you ran it.
The attaboy is hidden over in Event Viewer for SFC.

*Then you can do one of two things:*

3) You can then try SP2 on that box again. Or you can do what I'd
probably
do and after you Run SFC, I'd do a repair install or what MSFT calls an
upgrade install only you are upgrading from your OS. It works wonderfully
well, but there is always the caveat that you don't have 100% guarantee
that
you may not lose some information so do a current Back Up and a back up
is
always an important step if you are going to play with a Beta--even the
later pubic beta RC2 or the one of these leaks from the Beta sites like
Neowin.

I believe a repair/upgrade install is going to fix that box so you can
run
SP2 on it. In the 3rd week of August or thereabouts, SP2 is going RTM.

I would not go to the Recovery Console on that box with the 4 most
commonly
used repair moves at RC because the RC should be respected as more of a
last
ditch tool, perhaps with the exception of running chkdsk /r from it
unless
you are one who is very experienced with a n umber of commands in it.

The more extreme step is to format that box, but I don't think you have
to
do that at all at this point.

This is from a nice site from one of the MSFT XP MVP's:

http://www.michaelstevenstech.com/XPrepairinstall.htm

and this is the MSKB on a Repair versus Parallel Install:
How to install or upgrade to Windows XP

http://support.microsoft.com/default...&Product=winxp

I much prefer a *repair or upgrade* install to a parallel install because
the repair install will restore your settings perfectly and a parallel
install to another drive or another folder on your OS drive will be much
more inconvenient and have you trying to get your data out of it.

Good luck and post up what you do,

Chad Harris
__________________________________________________ _____________


"Harold" wrote in message
...
I have always used Windows explorer.exe to open multiple files at the
same
time by highlighting them, right clicking, and choosing "Open." Never
any
problems doing this until after installing XP's SP2 build 2162. Now
when
I
do the same procedure the files open but Windows explorer.exe crashes
wanting to send a message to Microsoft and then it closes down. My
files
remain open but Windows explorer.exe shuts down. I have tried doing a
sfc
/scannow and boy was that a fiasco. In any case, it didn't find any
file
to replace but I'm not sure it was an accurate run but that is a whole
other story.



Any suggestions on how to fix Windows explorer.exe short of
uninstalling
SP2?



Thanks



Harold