System32 Duplicates

[Guest]

Archived from groups: microsoft.public.windowsxp.basics (More info?)

In the folder Windows\System32 I have found a large number of duplicate
files of the form *(2).dll. Where do these duplicates come from and is it
safe to delete them? I assume the file without the (2) is the the current
file, is my assumption correct in all cases?

 

[Guest]

Archived from groups: microsoft.public.windowsxp.basics (More info?)

On Sat, 11 Dec 2004 12:27:50 -0000, Edward W. Thompson wrote:

> In the folder Windows\System32 I have found a large number of duplicate
> files of the form *(2).dll. Where do these duplicates come from and is it
> safe to delete them? I assume the file without the (2) is the the current
> file, is my assumption correct in all cases?

Do you use System Restore now and then? If yes, it is probably responsible
for creating the *(2).dll files. You're seeing the rule of one unique name
per file in any one folder in action. A restore point might encompass files
that have since been changed due to updates or software installations.
Instead of overwriting the existing file, a new name (filename(2)) is
created so that both are on hand.

If you are not pressed for space, leave the "extras" in place so that they
are available for undo operations with System Restore.

As for which file is the working copy, it would be the one without the (2).
A program's instructions will be looking for the original names, not the
altered names.

If a program pops up an error referring to one of these duo-named files,
then this would be another situation where it would be helpful to have the
(2) file still in existence. Rename the pair of files so that the (2) file
becomes the working copy. Or reinstall the program so that it has the exact
file version in place that it needs.

--
Sharon F
MS-MVP ~ Windows Shell/User

 

[Guest]

Archived from groups: microsoft.public.windowsxp.basics (More info?)

Many thanks for the explanation which I think others will also find most
useful.


"Sharon F" <sharonfDEL@ETEmvps.org> wrote in message
news:%23c0G4l63EHA.3368@TK2MSFTNGP10.phx.gbl...
> On Sat, 11 Dec 2004 12:27:50 -0000, Edward W. Thompson wrote:
>
>> In the folder Windows\System32 I have found a large number of duplicate
>> files of the form *(2).dll. Where do these duplicates come from and is
>> it
>> safe to delete them? I assume the file without the (2) is the the current
>> file, is my assumption correct in all cases?
>
> Do you use System Restore now and then? If yes, it is probably responsible
> for creating the *(2).dll files. You're seeing the rule of one unique name
> per file in any one folder in action. A restore point might encompass
> files
> that have since been changed due to updates or software installations.
> Instead of overwriting the existing file, a new name (filename(2)) is
> created so that both are on hand.
>
> If you are not pressed for space, leave the "extras" in place so that they
> are available for undo operations with System Restore.
>
> As for which file is the working copy, it would be the one without the
> (2).
> A program's instructions will be looking for the original names, not the
> altered names.
>
> If a program pops up an error referring to one of these duo-named files,
> then this would be another situation where it would be helpful to have the
> (2) file still in existence. Rename the pair of files so that the (2) file
> becomes the working copy. Or reinstall the program so that it has the
> exact
> file version in place that it needs.
>
> --
> Sharon F
> MS-MVP ~ Windows Shell/User

 

[Guest]

Archived from groups: microsoft.public.windowsxp.basics (More info?)

On Sat, 11 Dec 2004 21:13:57 -0000, Edward W. Thompson wrote:

> Many thanks for the explanation which I think others will also find most
> useful.

You're most welcome and glad to have helped.

--
Sharon F
MS-MVP ~ Windows Shell/User