How To Fix Explorer.exe Crashing In Windows 7 x64

I saw this many times and there is a quick fix for some. You see Windows 7 x64 actually uses System32 explorer.exe and not SysWOW64. This is a problem because there is no explorer.exe in System32 (least not for me).

The quick fix is this. Copy (not move) the explorer.exe from system then paste it in the System32 folder.

Yes,it works for me in x64.

You have to copy Explorer.exe from SysWOW64 folder in System32 folder.

No crashes anymore.

ViciouslyCold said:

I saw this many times and there is a quick fix for some. You see Windows 7 x64 actually uses System32 explorer.exe and not SysWOW64. This is a problem because there is no explorer.exe in System32 (least not for me).

The quick fix is this. Copy (not move) the explorer.exe from system then paste it in the System32 folder.

How is it managing to crash if it doesn't exist?

Great. Thanks. Hopefully this will fix the Explorer crashes.

This has been annoying me since I installed my W7 Ultimate from the Microsoft party pack. I was using build 7100 before with no problems at all..

It doesn't matter if you copy it from system or sysWOW64.

and H2 it manages to crash because Windows is looking for explorer.exe in Windows32. So whenever it doesn't find it, windows crashes. I guess Windows does things in cycles which is why it crashes randomly instead of never works.

ViciouslyCold said:

It doesn't matter if you copy it from system or sysWOW64.

and H2 it manages to crash because Windows is looking for explorer.exe in Windows32. So whenever it doesn't find it, windows crashes. I guess Windows does things in cycles which is why it crashes randomly instead of never works.

Why would it be looking for it in ..\system32 when it lives in \Windows?

How does it manage to find it when it needs to start it, only to then "forget" and look in the wrong place whenever a crash occurs?

H2SO4 said:

ViciouslyCold said:

It doesn't matter if you copy it from system or sysWOW64.

and H2 it manages to crash because Windows is looking for explorer.exe in Windows32. So whenever it doesn't find it, windows crashes. I guess Windows does things in cycles which is why it crashes randomly instead of never works.

Why would it be looking for it in ..\system32 when it lives in \Windows?

How does it manage to find it when it needs to start it, only to then "forget" and look in the wrong place whenever a crash occurs?

You'd have to ask Microsoft. All I know is one day I was using Auslogics Task Manager and clicked on the explorer.exe to see where it was located and it sent me to System32 and no explorer.exe was in there.

ViciouslyCold said:

You'd have to ask Microsoft. All I know is one day I was using Auslogics Task Manager and clicked on the explorer.exe to see where it was located and it sent me to System32 and no explorer.exe was in there.

Since the (64-bit) Explorer.exe resides in \Windows, and not \Windows\System32, I'm tempted to conclude that the Auslogics product produced an incorrect result for reasons of its own.

H2SO4 said:

ViciouslyCold said:

You'd have to ask Microsoft. All I know is one day I was using Auslogics Task Manager and clicked on the explorer.exe to see where it was located and it sent me to System32 and no explorer.exe was in there.

Since the (64-bit) Explorer.exe resides in \Windows, and not \Windows\System32, I'm tempted to conclude that the Auslogics product produced an incorrect result for reasons of its own.

Well as u can tell by other people's posts putting explorer.exe in system32 fixes crashing so clearly its not wrong. If it were wrong my advice would fail because system32 wouldn't matter then.

ViciouslyCold said:

Well as u can tell by other people's posts putting explorer.exe in system32 fixes crashing so clearly its not wrong. If it were wrong my advice would fail because system32 wouldn't matter then.

Good on ya for helping others :)