Explorer not responding.Could it be wowexec.exe? Repost with OS details.

  • Thread starter Thread starter Stryker
  • Start date Start date
S

Stryker

OS XP Pro+SP2 I used a slipstream install to upgrade and now sfc /scannow
won't work because it doesn't like either the slipstreamCD or SP2 upgrade
CD.

Following excellent advice received in this NG I am trying to identify the
cause of explorer not responding when trying to open partitions.

I have identified most of the files running using "Filemon" but only
wowexec.exe looks out of place.

I believe this is a 16 bit MS file which I don't think I need but I would
prefer an expert view before doing anything silly.

TIA

Stryker
 
Stryker wrote:
| OS XP Pro+SP2 I used a slipstream install to upgrade and now sfc
| /scannow won't work because it doesn't like either the slipstreamCD
| or SP2 upgrade CD.
|
| Following excellent advice received in this NG I am trying to
| identify the cause of explorer not responding when trying to open
| partitions.
|
| I have identified most of the files running using "Filemon" but only
| wowexec.exe looks out of place.
|
| I believe this is a 16 bit MS file which I don't think I need but I
| would prefer an expert view before doing anything silly.
|
| TIA
|
| Stryker

Do a google for wowexec. Also dig down in the registry for the
windows setup source. Make sure that the drive letters are correct.
This kind of thing comes up when _fooling_ with partitions.
 
BBUNNY said:
Stryker wrote:
| OS XP Pro+SP2 I used a slipstream install to upgrade and now sfc
| /scannow won't work because it doesn't like either the slipstreamCD
| or SP2 upgrade CD.
|
| Following excellent advice received in this NG I am trying to
| identify the cause of explorer not responding when trying to open
| partitions.
|
| I have identified most of the files running using "Filemon" but only
| wowexec.exe looks out of place.
|
| I believe this is a 16 bit MS file which I don't think I need but I
| would prefer an expert view before doing anything silly.
|
| TIA
|
| Stryker

Do a google for wowexec. Also dig down in the registry for the
windows setup source. Make sure that the drive letters are correct.
This kind of thing comes up when _fooling_ with partitions.
Click to expand...

Thank you for your help.

Googled for wowexec.exe but have not found anything to relate it to the
problem of explorer not responding.

What do I search for in the registry to find windows setup source. "windows
setup" does not return anything.

Silver surfer needs a bit of extra help.

TIA

Stryker
 
Thank you for your help.

Googled for wowexec.exe but have not found anything to relate it to the
problem of explorer not responding.

What do I search for in the registry to find windows setup source.
"windows setup" does not return anything.

Silver surfer needs a bit of extra help.

TIA

Stryker
Click to expand...

Can you run this command at a command prompt:

tasklist.exe /m /FI "IMAGENAME eq explorer.exe" > C:\TLOut.log

This should create a file called C:\TLOut.log. Can you post the contents of
this file?

wowexec.exe only opens up if there is a 16-bit Windows program/DLL loaded.
The command above will identify which DLLs are loaded by Explorer.

The only problem is, you'll need to run this command at the exact moment
explorer stops responding.


--
------------------------------------------------------------------------
oshah [shexec32]
Control Panel -> System -> Advanced -> Error Reporting -> Choose Programs
-> Do not report errors for these programs:

Acrobat.exe
waol.exe

------------------------------------------------------------------------
 
Back
Top