deleting duplicate files in win 2000

[Guest]

Hi

I have Win 2000 SP4

I ran Norton Cleansweep for duplicate files and found out that there are at least 100 mb bogged down in duplicate files. I would like some input to help me decide whether to delete or not

most files are paired in these folder-couples
1) \WINNT\system32\ and \WINNT\ServicePackFiles\i3862) \WINNT\system32\ and \WINNT\dllcache3) \WINNT\Driver Cache\i386\ and \WINNT\ServicePackFiles\i38
The duplicate files are mainly dll's, sys's or msi's. They have same name and size, and sometimes also same date

I guess it would be a good idea to keep files in the system32 folder but can I delete from the dllcache or the ServPack.... folder

Also, if I have duplicate files elsewhere in different application folders, can I delete one files and move the other to a folder in the PATH so that both programs can find it when they need it? Or can this be risky

Thanks for all input

/peter

 

[George Hester]

Just because you have duplicate files means nothing. In Windows 2000 there is something called System File Protection. Now what this means is that if a file that is used gets corrupted which can turn your Windows 2000 system into Jelly, the system can obtain a non-corrupted version because you have it saved somewhere where it is never used and so cannot become corrupted. At least that is the idea.

What you are asking about is just the repository that is used by System File Protection to get uncorrupted versions of files if needed.

If you remove those files you will likely turn your operatring system into Jelly. Don't do it.

 

[Steve Nielsen]

SFC pulls replacement files off the Windows CD unless you specify
another location. The locations the OP listed look more like backup
locations for Service Pack and hotfix installatins to me.

Steve

 

[Josef Stalin]

Hi,

I have Win 2000 SP4.

I ran Norton Cleansweep for duplicate files and found out that there are

at least 100 mb bogged down in duplicate files. I would like some input to
help me decide whether to delete or not.

most files are paired in these folder-couples:
1) \WINNT\system32\ and

\WINNT\ServicePackFiles\i3862) \WINNT\system32\ and
\WINNT\dllcache3) \WINNT\Driver Cache\i386\ and
\WINNT\ServicePackFiles\i386

The duplicate files are mainly dll's, sys's or msi's. They have same name

and size, and sometimes also same date.

I guess it would be a good idea to keep files in the system32 folder but

can I delete from the dllcache or the ServPack.... folder?

Also, if I have duplicate files elsewhere in different application

folders, can I delete one files and move the other to a folder in the PATH
so that both programs can find it when they need it? Or can this be risky?

Thanks for all input!

/peter

I was curious about that myself so I searched google and this is what I
found:

http://support.microsoft.com/default.aspx?scid=kb;en-us;290402

"The ServicePackFiles folder contains the updated versions of the Windows
2000 system files installed by the Service Pack. This folder is used when
additional components are installed to ensure that the most recent version
of the files are used. This folder is also used by the Windows File
Protection system to restore corrupt or missing versions of the Service Pack
files."

My take on this is to leave well enough alone,

Uncle Joey

 

[George Hester]

Yes those are the files he was thinking of removing. Furthermore that is not the whole story. But go ahead and remove the darn files. Likely you won't be able to anyway but it's always a good idea to wreak your vehicle just so you had some idea what it was like when it ran.

 

[Gary Smith]

SFC pulls replacement files off the Windows CD unless you specify
another location. The locations the OP listed look more like backup
locations for Service Pack and hotfix installatins to me.

SFC pulls replacement files first from the dllcache folder and only when
that fails does it use the Windows CD. You may be able to get away with
deleting files from dllcache, but SFC may insist on putting some of them
back.

 

[Guest]

ok, it seems it is best to leave things be then...

thanks all

/p

 

[Torgeir Bakken (MVP)]

SFC pulls replacement files first from the dllcache folder and only when
that fails does it use the Windows CD. You may be able to get away with
deleting files from dllcache, but SFC may insist on putting some of them
back.

Hi

It is one more place that the system tries to find files from, the
ServicePackFiles folder (if it exists):

Dllcache folder --> ServicePackFiles folder --> Windows CD/Install source



--
torgeir
Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of the 1328 page
Scripting Guide:
http://www.microsoft.com/technet/community/scriptcenter/default.mspx

 

[Steve Nielsen]

Thanks for setting me straight on that.

Steve

Gary Smith wrote:




Hi

It is one more place that the system tries to find files from, the
ServicePackFiles folder (if it exists):

Dllcache folder --> ServicePackFiles folder --> Windows CD/Install source



--
torgeir
Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of the 1328 page
Scripting Guide:
http://www.microsoft.com/technet/community/scriptcenter/default.mspx