What are files with names like this - shell32(2).dll

  • Thread starter Thread starter davexnet
  • Start date Start date
D

davexnet

I've about 8 - 10 files that have a (2) in the name,
and same again with a (3).

Is this a vestige of some operation, maybe repair, or system
restore and these files are left over and essentially dead?
Or could they still be live files ?

I looked at a few at random for a reference in the registry
but came up empty.

TIA for any info.
Dave
 
davexnet said:
I've about 8 - 10 files that have a (2) in the name,
and same again with a (3).

Is this a vestige of some operation, maybe repair, or system
restore and these files are left over and essentially dead?
Click to expand...

I'd guess probably.
Or could they still be live files ?
Click to expand...

Possibly. Of course, if they are locked, you won't be able to delete them,
anyway.
I looked at a few at random for a reference in the registry
but came up empty.

TIA for any info.
Dave
Click to expand...

Could you give some specific filename examples here? Sometimes you can
get a clue from the filenames, as to what programs they may have been
associated with.
 
I've about 8 - 10 files that have a (2) in the name,
and same again with a (3).

Is this a vestige of some operation, maybe repair, or system
restore and these files are left over and essentially dead?
Or could they still be live files ?

I looked at a few at random for a reference in the registry
but came up empty.

TIA for any info.
Dave
Click to expand...

Please do this first, then start guessing:

Perform some scans for malicious software, then fix any remaining
issues:

Download, install, update and do a full scan with these free malware
detection programs:

Malwarebytes (MBAM): http://malwarebytes.org/
SUPERAntiSpyware: (SAS): http://www.superantispyware.com/

They can be uninstalled later if desired.
 
Thanks for your suggestions. I've had MBAM installed for some time, no
malware detected.
Nor does my AV (Avast home 4.8) find anything.

Here's the actual names - I've left them on the HDD for now,
until I can get a feeling about them one way or the other.
dnsapi(2)(2).dll
mswsock(2)(2).dll
shell32(2).dll
SHFOLDER(2).DLL
wdmaud(2).drv
url(3).dll
urlmon(3).dll
wdmaud(3).drv
wininet(3).dll
wdmaud(4).drv

all the above files are in \windows\system32



I've about 8 - 10 files that have a (2) in the name,
and same again with a (3).

Is this a vestige of some operation, maybe repair, or system
restore and these files are left over and essentially dead?
Or could they still be live files ?

I looked at a few at random for a reference in the registry
but came up empty.

TIA for any info.
Dave
Click to expand...

Please do this first, then start guessing:

Perform some scans for malicious software, then fix any remaining
issues:

Download, install, update and do a full scan with these free malware
detection programs:

Malwarebytes (MBAM): http://malwarebytes.org/
SUPERAntiSpyware: (SAS): http://www.superantispyware.com/

They can be uninstalled later if desired.
 
Thanks for your suggestions.  I've had MBAM installed for some time, no
malware detected.
Nor does my AV (Avast home 4.8) find anything.

Here's the actual names - I've left them on the HDD for now,
until I can get a feeling about them one way or the other.
dnsapi(2)(2).dll
mswsock(2)(2).dll
shell32(2).dll
SHFOLDER(2).DLL
wdmaud(2).drv
url(3).dll
urlmon(3).dll
wdmaud(3).drv
wininet(3).dll
wdmaud(4).drv

all the above files are in \windows\system32







Please do this first, then start guessing:

Perform some scans for malicious software, then fix any remaining
issues:

Download, install, update and do a full scan with these free malware
detection programs:

Malwarebytes (MBAM):  http://malwarebytes.org/
SUPERAntiSpyware: (SAS):  http://www.superantispyware.com/

They can be uninstalled later if desired.
Click to expand...

You have MBAM and AVG installed. That's fine.

Did you update and run a full scan with MBAM and SAS?

MBAM and AVG don't know about everything!
 
davexnet said:
I've about 8 - 10 files that have a (2) in the name,
and same again with a (3).

Is this a vestige of some operation, maybe repair, or system
restore and these files are left over and essentially dead?
Or could they still be live files ?

I looked at a few at random for a reference in the registry
but came up empty.
Click to expand...

They could be residuals from restore or copy operations.

You can use the COMP command to see if they are identical to their
namesakes:

COMP {file-1} {file-2}

If they are identical, you can probably remove them with no adverse effects.
 
Back
Top