New
#11
If you run task manager processes tab and right click on explorer.exe, then open file location, you will see that explorer.exe runs from:
C:Windows\explorer.exe by default.
I copied explorer.exe to system32 folder rebooted and explorer was still running from:
C:Windows\explorer.exe
This did not work for me.
Last edited by shuster; 15 Oct 2009 at 08:16.
For windows to start and get to your desktop it would have to execute explorer.exe from either the syswow64 folder or c:\windows folder since there is no explorer.exe in system32 folder by default. If your symptom is that windows never gets to the desktop, then I can believe you. If you are getting to the dektop and then at some point explorer crashes your theory cannot be correct.
System Drive/Windows/Explorer.exe -64bit
System Drive/Windows/SysWOW64/Explorer.exe -32bit
Why do i need an explorer.exe in System32 when its "pulling" the correct one from the previous links
Really strange,...it isn't missing anything...
The more the merrier.
If he is still not convinced, I would suggest deleting explorer.exe from the c:\windows folder and rebooting. But have a repair cd handy to replace it again to get back to the desktop.
Last edited by shuster; 15 Oct 2009 at 14:22.
I dunno, just a wild guess here. Is it possible that the explorer.exe is coded to look for itself in the wrong place, possibly under a specific condition (like a plugin installed or something)...thus that is why it doesn't crash when it's copied over to system32?
My theory is that it's not Windows itself looking for it there in system32...but explorer.exe or hook to it looking there. I can't understand any other way this fix would actually work.
*posted also in the other thread dealing with this issue*
I have the same issue with Windows 7 x64 Sig edition.
I have moved the explorer.exe to system32 and it made no difference.
I'm getting at least 5 explorer.exe crashes a day.
Because I'm hosting one of the release parties, they have a priority support ticket number. I've just been on the phone for an hour and the support guy took over my system, looked in the event viewer, did an sfc/ scannow and tried to get me to replicate the crash. Of course there was no crash when he was in my system while I was on the phone to him (sods law)
I am to use my system as normal over the weekend then contact him again on Monday by which time he will have done some research on the problem and check the crashes that I have over the weekend.
I was using build 7100 with zero problems before I got the Signature edition.
I'll report back on Monday to see what (or if there is one) the solution is.
I don't really want to host a party and be showing people my system with it crashing when I show them libraries.