theBlackman on 3/3/2010 at 02:41
OK techies. I seem to have damaged, or gotten damaged, the Explorer.Exe file.
I do have a copy (In a Bart Boot build ).
I don't want to reinstall the system and the apps. Where is it supposed to "live" and can I just plug the clean copy into the area it is supposed to occupy?
Every now and then when Explorer is attempting to, or is, running, it runs my CPU up to 100 percent and clogs the system, sometimes to the point of my needing to Power-off and reboot.
Any comments would be appreciated, even "It can't be done".
Not that it should make any difference, but Specs: XP Pro, AMD CPU, 2 Gig RAM.
Thanks
Enchantermon on 3/3/2010 at 03:26
Instead of rebooting, you could just kill the process and run it again.
The file resides in C:\Windows on 7, I would assume that it's the same on XP (or C:\Winnt if you have that instead).
Honestly, I wouldn't think replacing it would be a problem, but someone more knowledgeable should make that call; messing with system files is Risky Business™.
theBlackman on 3/3/2010 at 06:07
Thanks. I don't see it in WINDOWS but if I blow the game, I'll not be that much worse off.
I'll try the Task Mgr, stop the process and see what happens.
ffox on 3/3/2010 at 11:39
On my XP Home (SP3) machine, explorer.exe is in 3 places. The newest version is in C:\WINDOWS and there is a copy of it in C:\WINDOWS\ServicePackFiles\i386.
The version I've got is 6.0.2900.5512, size 1,033,728 bytes
I mention this because I have heard of "something else" replacing explorer.exe. Perhaps a scan is in order?
I have also seen reports that a corrupt .avi file/compressed file may cause explorer to hog 100% of the CPU. Apparently this bug was fixed in SP3.