Slimming Down Windows Xp Part 5: Windows Folders Options

[Bold_Fortune]

Slimming Down Windows XP: The Complete Guide PART 5

WINDOWS Folders


Individual Files I remove from C:\WINDOWS:

Any *.bak files

Any *.bmp files

Any *.log files

The "WindowsUpdate.log" can only be deleted if the Automatic Updates Service is stopped.

Any *.old files

Any *.tmp files

Any *.txt files

The "SchedLgU.Txt" can only be deleted if the Task Scheduler Service is stopped.

_default........(Shortcut to MS-DOS Program). An invalid 16-bit program in XP.

bootstat.dat....

clock.avi.......

control.ini.....A zero-length file.

desktop.ini.....

hh.exe..........(Microsoft® HTML Help Executable). Part of Microsoft's HTML Help (.chm) format. One of three files needed to open *.chm help files. Also need to open *.chm help files are the hhctrl.ocx and the itss.dll, both located in the system32 folder.

msdfmap.ini.....

ODBCINST.INI....

system.ini......(For 16-bit app support). XP doesn't use this. However, it usually returns after awhile anyway, so I just leave it alone.

TASKMAN.EXE.....Task Manager

---------------------------------------

TWAIN, a programming interface that lets a graphics application, such as an image editing program or desktop publishing program, activate a scanner, frame grabber or other image-capturing device.

twain.dll......Twain Source Manager (Image Acquisition Interface).

twain_32.dll...Twain_32 Source Manager (Image Acquisition Interface).

A thunk typically occurs when a 16-bit application is running in a 32-bit address space, and its 16-bit segmented address must be converted into a full 32-bit flat address. On the other hand, if a 32-bit program calls a 16-bit DLL, then the thunk is in the opposite direction: from 32 bit to 16 bit.

twunk_16.exe....(Twain_32.dll Client's 16-Bit Thunking Server). Allows 16-bit DOS applications to make 32-bit calls.

twunk_32.exe....(Twain.dll Client's 32-Bit Thunking Server). Allows 32-bit DOS applications to make 16-bit calls.

---------------------------------------

vb.ini..........
vbaddin.ini.....
vmmreg32.dll....Windows VMM Registry Library

win.ini.........(For 16-bit app support). XP just ignores it anyway.
WINHELP.EXE.....(Windows Help Engine application file). A 16-bit Windows Help reader.

winhlp32.exe....(Microsoft® Help). When you click on the question mark in the upper corner of a dialog box (such as in System Properties or Display Properties) your cursor changes to a question mark. Then when you click on something in the dialog box that you have a question about, a .hlp file tooltip comes into view. The WINHLP32.EXE displays these .hlp file tooltips. Since I usually remove any .hlp files from my system, I have no need for this function, so I remove WINHLP32.EXE.

WMSysPr9.prx....From what I can gather when I open this file in Notepad, it appears to belong to Windows Streaming Media for a Dial-up Connection.

WORDPAD.INI.....Only the WORDPAD.INI usually returns.

---------------------------------------

C:\WINDOWS\$hf_mig$
I delete the $hf_mig$ folder and its contents.

Per Microsoft: When a security update, critical update, update, update rollup, driver, or feature pack installs GDR (General Distribution Releases) version files, the hotfix files are also copied to the %windir%\$hf_mig$ folder. This supports migration to the appropriate files if you later install a hotfix or service pack that includes earlier versions of these files. For example, consider the following scenario:

1. You apply a security update that installs a GDR version of File.dll with a version number of 5.2.3790.1000 and copies a hotfix version of File.dll with a version number of 5.2.3790.1000 to the %windir%\$hf_mig$ folder.

2. You apply a hotfix that includes a hotfix version of File.dll with a version number of 5.2.3790.0000.
In this scenario the hotfix installation in step 2 installs the hotfix version of File.dll (version number 5.2.3790.1000) from the %windir%\$hf_mig$ folder instead of the hotfix version of File.dll (version number 5.2.3790.0000) from the hotfix package.

C:\WINDOWS\$MSI31Uninstall_KB893803v2$
I delete the $NtServicePackUninstallIDNMitigationAPIs$ folder and its contents.

Windows Installer 3.1 uninstall files.

The Microsoft Windows Installer 3.1 is the application installation and configuration service for Windows.

C:\WINDOWS\$NtServicePackUninstallIDNMitigationAPIs$ and C:\WINDOWS\$NtServicePackUninstallNLSDownlevelMapping$ (Installed by Internet Explorer 7.)

I delete both these folders and their contents.

These folders each contain necessary files for the uninstallation of Internet Explorer 7. You can uninstall IE7 through the Add/Remove Programs window, but these folders and their contents must be present in order to do so.

These folders and their contents have absolutely nothing to do with Internet Explorer 7 being in good working order. If you are certain you won't need to uninstall IE7, then by all means, delete these folders and their contents.

C:\WINDOWS\$NtUninstallKBxxxxxx$
I delete all the $NtUninstallKBxxxxxx$ folders and their contents.

These $NtUninstallKBxxxxxx$ folders contain the uninstall files for the Windows Updates.

They have nothing to do with the Updates being in good working order on your system. If you are certain that you won't need to uninstall any of these Updates, by all means, delete these folders.

---------------------------------------

C:\WINDOWS\addins
I delete the addins folder.

ActiveX controls (.ocx) files.

The addins folder is always empty on my system.

---------------------------------------

C:\WINDOWS\AppPatch

The AppPatch folder contains the Program Compatibility Engine, which allows Windows to modify how individual applications run, forcing poorly-programmed or older applications to run satisfactorily under XP. The AppPatch folder contains certain application compatibility .dlls and Appfix packages.

You can delete the AppPatch folder and its contents if you want. However, you may start receiving Application Popup Errors when opening certain applications. Your applications should still function properly (under most circumstances) after these Application Popup Errors appear.

Personally, I will not delete any file or folder from my system that will cause errors. I really dislike seeing error messages on my system.

I've found that if I keep these 3 files in the AppPatch folder, while deleting the other 7 files, I won't receive any Application Popup Errors when opening certain programs:

ACGENRAL.DLL....Windows Compatibility DLL

DRVMAIN.SDB.....

SYSMAIN.SDB.....

Note: A recent Windows Security Update (KB920213) installs an additional file to the AppPatch folder, acadproc.dll. I also delete this new file. The apph_sp.sdb is one of the files in the AppPatch folder I normally delete. It is re-installed with the same Security Update. I delete it again.

Then I delete these individual files from C:\WINDOWS\system32:

ahui.exe........(Application Compatibility UI). Program Compatibility Engine.

APPHELP.DLL.....(Application Compatibility Client Library). The Windows Media Player 11 installation may deliver the message that the APPHELP.DLL cannot be found. The installation will proceed without it after clicking OK on the message. You may also receive the same message upon your first reboot after installing WMP11.

compatUI.dll....(CompatUI Module). Help Center Interface for Application Compatibility Engine.

---------------------------------------

C:\WINDOWS\Config
I delete the Config folder.

The Config folder contains configuration .idf files used by the MIDI sound system. Depending on system configuration, this folder might be empty.

C:\WINDOWS\Connection Wizard
I delete the Connections Wizard folder.

The Connection Wizard folder contains files used for establishing Internet connectivity. It can be an empty folder.

C:\WINDOWS\Cursors
Here you can delete any cursors and animated cursors you think you will never use.

The Cursors folder contains static and animated cursor files. You can use these files by configuring the Mouse applet in the Control Panel.

C:\WINDOWS\Debug

Log files

I delete the Usermode subfolder.
I delete the WPD subfolder and its contents.

The Debug folder contains .log files that can be used to debug network connectivity and other setup functions.

C:\WINDOWS\Downloaded Installations
I delete the Download Installations folder and its contents.

C:\WINDOWS\Downloaded Program Files
I delete the contents of the Download Installations folder.

The Downloaded Program Files folder contains ActiveX controls and Java applets that have been downloaded from the Internet.

Alternatively, you can view and delete these ActiveX controls or Java applets by going into Internet Properties. Under the "General" tab, under "Temporary Internet files," click on the "Settings" button. Then under "Temporary Internet files folder," in the window that opens up, click on "View Objects."

C:\WINDOWS\Driver Cache\i386
I delete the drivers.cab and the sp2.cab.

The Driver Cache folder contains a platform subdirectory and a copy of the driver.cab file so that new devices can be easily installed without needing the Windows XP CD. Might contain sp1.cab or sp2.cab if installing an integrated copy of the operating system (Slipstreamed CD).

Sometimes Windows updates will replace earlier versions of files contained in these cabs with newer versions. Placing them in the i386 folder, not in the cabs themselves.

You're not going to have these newer versions of files on your Installation CD. For that reason, you may want to consider keeping these newer versions of individual files, and deleting only drivers.cab and sp2.cab.

---------------------------------------

C:\WINDOWS\Fonts


Fonts with .FON Extensions

Many FON extension fonts (The red "A" fonts) are hidden. Do a search for *.fon in Search Assistant. In Search Assistant, be sure that under "More Advanced Options" you have "Search for hidden files and folders" selected. About 138 of these Fonts should show up.

I move the great majority of these fonts (124 to be exact) to another location with a batch file I created. If you do not wish to go through the tedious and time-comsuming process of creating a batch file which singles out and moves over a hundred fonts, here is a neat little trick for you.

Highlight these specific Fonts for a U.S. installation...

Important Note: European installations will need to keep these two additional fonts: app850.fon and vga850.fon. (In US systems, the corresponding fonts are dosapp.fon and vgaoem.fon.)

cga40woa.fon
cga80woa.fon

coure.fon

dosapp.fon

ega40woa.fon
ega80woa.fon

modern.fon

roman.fon

serife.fon
sserife.fon

symbole.fon

vgafix.fon
vgaoem.fon
vgasys.fon

At the top of Search Assistant click on "Edit". Then select "Invert Selection". Now you can delete all the other 123 unnecessary Fonts all at once, because they will now be the ones highlighted, and the fonts you want to keep won't be.


Fonts with .TTF Extensions

Here is a list of the remaining *.ttf Fonts I have in C:\WINDOWS\Fonts.

Many TTF extension fonts (The blue-green "O" fonts) are hidden. Do a search for *.ttf in Search Assistant. In Search Assistant, be sure that under "More Advanced Options" you have "Search for hidden files and folders" selected.

Highlight these specific Fonts...

arial.ttf
arialbd.ttf
arialbi.ttf
ariali.ttf

framd.ttf
framdit.ttf

lucon.ttf

marlett.ttf

micross.ttf

tahoma.ttf
tahomabd.ttf

times.ttf
timesbd.ttf
timesi.ttf

trebuc.ttf
trebucbd.ttf

verdana.ttf
verdanab.ttf
verdanai.ttf
verdanaz.ttf

At the top of Search Assistant click on "Edit". Then select "Invert Selection". Now you can delete all the other unnecessary Fonts all at once, because they will now be the ones highlighted, and the fonts you want to keep won't be.

A Good Practice: If some of the Fonts you have selected will not delete from within the Search Assistant, don't delete them. There are, of course, other ways of deleting them. You could go directly into the Fonts folder and delete them. Or you could go into Safemode and delete them. That's up to you. Myself, if I can't delete a particular Font from within the Search Assistant, I don't.

After I delete all of the above fonts, I delete this file from C:\WINDOWS\system32 and reboot my system:

FNTCACHE.DAT...Font Cache.

Windows then builds a fresh FNTCACHE.DAT.

---------------------------------------

C:\WINDOWS\Help
You can delete all the individual help files in the Help folder. It just depends on how interested you are in their subject matter.

The Help folder contains the help files used by the Windows XP Help system and all its native utilities.

C:\WINDOWS\Help\nvcpl (Installed by NVIDIA Driver Update.)
I delete the nvcpl folder and its contents.

C:\WINDOWS\Help\Tours
I delete Tours folder and its contents.

Then I delete this file that belongs to it in C:\WINDOWS\system32:

tourstart.exe

C:\WINDOWS\ie7 (Installed by Internet Explorer 7.)
I delete the ie7 folder and its contents.

The ie7 folder contains the necessary files for uninstalling of Internet Explorer 7. You can uninstall IE7 through the Add/Remove Programs window, but the ie7 folder and its contents must be present in order to do so.

This folder and its contents has absolutely nothing to do with Internet Explorer 7 being in good working order. If you are certain you won't need to uninstall IE7, then by all means delete the ie7 folder and its contents.

C:\WINDOWS\ie7updates (Installed by Internet Explorer 7.)
I delete the ie7 folder and its contents.

The ie7updates folder contains the files Microsoft downloads to your system to be able to then draw upon during the IE7 installation.

C:\WINDOWS\ie8 (Installed by Internet Explorer 8.)
I delete the ie8 folder and its contents.

The ie8 folder contains the necessary files for uninstalling Internet Explorer 8. You can uninstall IE8 through the Add/Remove Programs window, but the ie8 folder and its contents must be present in order to do so.

This folder and its contents has absolutely nothing to do with Internet Explorer 8 being in good working order. If you are certain you won't need to uninstall IE8, then by all means delete the ie8 folder and its contents.

C:\WINDOWS\ime (See also PART 6 under C:\WINDOWS\system32\IME. It is also used when an IME is installed.)
I delete the ime folder and its contents.

The ime folder contains files to support Input Method Editors. An Input Method Editor (IME) allows computer users to enter complex characters and symbols (such as Japanese, Chinese, Tibetan and Korean characters), using a standard keyboard.

---------------------------------------

C:\WINDOWS\inf

The inf folder contains the .INF (system information) files used to install software components and hardware drivers.

Some people will tell you that it is okay to delete the entire contents of the inf folder. I totally disagree with this. INF files aren't just about installing software components or hardware drivers.

Just to be able to get into the Windows Component Wizard, your system will need these 36 .INF files present:

accessor.inf

certclas.inf
communic.inf
comnt5.inf

dtcnt5.inf

fp40ext.inf
fxsocm.inf

games.inf

ieaccess.inf
igames.inf
iis.inf
ims.inf

layout.inf

msmsgs.inf
msnmsn.inf
multimed.inf

netbeac.inf
netiprip.inf
netlpd.inf
netoc.inf
netsnmp.inf
nettpsmp.inf
netupnp.inf

oeaccess.inf
optional.inf

p2p.inf
pinball.inf

rootau.inf

setupqry.inf
startoc.inf
sysoc.inf

tsoc.inf

wbemoc.inf
wbemsnmp.inf
wmaccess.inf
wmpocm.inf


Here's an example using Microsoft Update.

These .INF files are needed by Microsoft Update:

drvindex.inf

machine.inf

branches.inf.....<-- When you delete the branches.inf, another is created when you download and install a Windows update.


Here's an example using the Acronis True Image program.

Acronis True Image needs these .INF files present in C:\WINDOWS\inf for you to utilize all its functions:

certclas.inf

disk.inf
drvindex.inf

layout.inf

volume.inf


And generally, updates for Windows Media Player require this file to be present:

unregmp2.exe.....Microsoft Windows Media Player Setup Utility


Here's what I do.

I delete all the .PNF files in the inf folder.

PNF files, are cache-type files that help making the opening of some applications quicker and more responsive.

These are files when deleted will re-create themselves should its corresponding .inf file by the same name be called upon.

Per Rob Elder: "It's a "pre-compiled" version of the ASCII .INF file that gets created when the Setup first processes a particular .INF file. It's done to speed up searches of the .INF files (as you've noticed there are LOTS of those on the system in Windows 2000/XP); if the dates of the .INF and .PNF files compare favorably (.PNF is later than .INF) the corresponding .PNF file will be used (if present)."

Then, after giving it some time (30 days or more), I see that no corresponding .PNF files are re-created alongside the .INF files of the same name, (That would mean my system isn't using those particular .INF files.), I will then go ahead and delete the unused .INF files.


In the meantime, however, here's a trick I picked up from NeoMayhem on our old Slimming Down Windows XP thread that we had going on at Neowin:

Do a search for mdm*.* and delete all the *.inf files that comes up.

There were 181 mdm*.* files in my inf folder.

These are all modem drivers, and it is very unlikely you will ever need them. You either have a modem already installed, or if you don't, and decide to add one later, it will come with its own set of drivers.

C:\WINDOWS\inf\IEM (Installed by Internet Explorer 7.)
I delete the IEM folder and its contents.

---------------------------------------

C:\WINDOWS\Installer

You can delete the contents on the Installer folder if you like, but keep in mind, Windows Installer uses the information within .MSI files that are provided with some applications, and installs, repairs, or removes software using this information.

One day you might click on the name of a program in Add/Remove Programs, because you want to modify it, or repair it, or uninstall it. And if it's one of those applications that uses an .MSI file, you're not going to be able to modify it, or repair it, or uninstall it.

C:\WINDOWS\java
You can delete the java folder and its contents if you want. Microsoft's (Java) Virtual Machine is no longer installed by default after SP2.

The java folder contains two empty subfolders, Classes and TrustLib.

If you choose to manually install (as I do sometimes) the old Microsoft (Java) Virtual Machine instead of Sun Java, the java folder and these subfolders will be recreated by the installation. (Along with another subfolder, Packages.)

If you choose to instead install Sun Java, the Sun Java installation will create its own folders and subfolders it will need.

C:\WINDOWS\lastgood
I delete the lastgood folder and it's contents.

The lastgood folder is a backup folder. The lastgood folder is generated after you install, uninstall or update, various drivers and programs and such. It will contain backup files in various subfolders that match the names of the folders they came from.
Usually the lastgood folder and its contents will delete on its own after rebooting, but every once in awhile it doesn't.

C:\WINDOWS\Media
Here I delete most of the sounds Windows makes.

The Media folder contains .wav files used by XP. Like the sound you hear when Windows starts up, or when you empty your Recycle bin.

C:\WINDOWS\msagent
I delete the msagent folder and its contents.

Microsoft Agent files (Microsoft Agent is a set of programmable software services that support the presentation of interactive animated characters within the Microsoft Windows interface.)

C:\WINDOWS\msapps
I delete the msapps folder and its contents.

Files that support backward compatibility in applications.

C:\WINDOWS\msdownld.tmp
I delete the msdownld.tmp folder and its contents.

C:\WINDOWS\mui
I delete the mui folder.

MUI (Multilingual-User Interface) Packs give companies flexibility in making language options available to users.

C:\WINDOWS\network diagnostic (Installed by Internet Explorer 7.)
I delete the network diagnostic folder and its contents.

The Network Diagnostics for Windows XP tool analyzes information about your network connectivity to help you troubleshoot network-related problems with your computer. Typically you will do this along with a support professional, either on the phone or over the internet.

C:\WINDOWS\nview
I delete the nview folder and its contents.

C:\WINDOWS\Offline Web Pages
I delete the Offline Web Pages folder and its contents.

Stores downloaded Webpages for offline availability.

C:\WINDOWS\OPTIONS
I delete the OPTIONS folder and its contents.

These are the cab files for my Fast Ethernet NIC Driver Setup Utility.

---------------------------------------

C:\WINDOWS\pchealth (See also Help and Support and Remote Desktop Help Session Manager in PART 2.)
I delete all the contents in the pchealth folder, but I keep the folder.

The pchealth folder contains files and subfolders to support the Microsoft Help Center Service. These files support all the Windows XP Help services, including features such as Remote Desktop Assistance.

IMPORTANT: Before you do this "move" (not copy) the msconfig.exe from inside the C:\WINDOWS\PCHEALTH\HELPCTR\Binaries folder to the System32 folder, or you will loose it.

---------------------------------------

C:\WINDOWS\PeerNet
I delete the PeerNet folder and its contents.

Per Microsoft: The optional Windows Peer-to-Peer networking component provides a framework for peer-to-peer programs to communicate directly between computers over Network Address Translation (NAT) devices and over the Internet.

C:\WINDOWS\PIF
I delete the PIF folder and its contents.

Program information files (PIFs) for MS-DOS-based programs.

---------------------------------------

C:\WINDOWS\Prefetch

Data files related to enhancing the speed at which applications start.

You can delete the Prefetch folder and its contents and turn off Prefetch despite what you may have read to the contrary. I doubt if you will notice much difference in your system's performance if you do. But read on, I'll show you something.

Should you do decide to delete the Prefetch folder and its contents, to turn off Prefetch, change the Prefetch registry setting to "0" here:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters

Dword value = EnablePrefetcher

0 = Disable
1 = App launch prefetch
2 = Boot Prefetch
3 = Both (recommended)

Here's what I discovered about Prefetch:

I keep two Windows XP backup images stored: my Slimmed Installation, and a Full Installation. The Full Installation I have stored for testing purposes and comparisons. I keep this Full Installation up-to-date the same as I do my Slimmed Installation.

Each installation is identical to the other. Each has the same programs installed. Each has the same settings and tweaks applied. Each is kept up-to-date with the latest drivers and Microsoft High-Priority Updates. Everything I install on one, I install on the other. Every change I make to one, I make to the other.

There are only two exceptions to this:

1). Services settings

2). Files removed

My Service settings on the Full Installation are setup a bit differently than those of my Slimmed Installation. Most of the Services I remove in my Slimmed Installation, are merely Disabled in my Full Installation. A few others I keep set to Automatic, if only to prevent errors from cropping up in my Event Viewer. A few more I set to Automatic because they'll just start up anyway if I leave them on Manual.

These are the only files I remove from the Full Installation:
Perfectly Safe To Remove Files and Folders

To figure out everything I have deleted on my Slimmed Installation... Well, you'd pretty much have to read the entire guide.
However, I can show you which Services I have enabled, disabled, and deleted on my Slimmed Installation:
PART 2: Disabled Services

On each installation, my reboot time is a consistent 31 seconds (given an occasional 32-second reboot on each). I have always kept a curious check on this.

I use PerfectDisk Defragmenter on both installations to manage my boot files, and I have always had Prefetch enabled (set to "3" in the registry) on both installations.

I cannot run BootVis on my Slimmed Installation, because I have COM+ disabled, and all it's associated files deleted.

I can run BootVis on my Full Installation, as COM+ is enabled, and none of its files have been deleted.

Now that we have those reference points established, let me show you the results.

With my Full Installation, (reboot time being a consistent 31 seconds), when I run BootVis, my consistent reboot time remains at 31 seconds.

If I then set my Prefetch to "0" in the registry (disabled), my reboot time gains 2 seconds; making it 33 seconds.

However, when I then keep that "0" setting, purge the Prefetch folder of all it's files, and defragment using PerfectDisk, my reboot time drops 1 second to 32 seconds.

So I gained 1 second on my reboot time on my Full Installation by doing this.

As I said, I cannot run BootVis on my Slimmed Installation.

When I disable Prefetch on my Slimmed Installation, my 31 second reboot time gains 1 second, making it 32 seconds.

However, leaving Prefetch disabled, and purging the Prefetch folder of its contents, and then defragmenting using PerfectDisk, my reboot time reverts once again to its 31 seconds.

By having the Prefetch disabled and the Prefetch folder purged of all its files on my Slimmed Installation, there is absolutely no difference in my reboot times. On the other hand, should I do the same for my Full Installation, it adds 1 second to my reboot time.

---------------------------------------

C:\WINDOWS\Profiles
I delete the Profiles folder and its contents.

Seemingly useless folder created by Adobe Reader.

C:\WINDOWS\Provisioning (See also Wireless Zero Configuration in PART 2.)
I delete the Provisioning folder and its contents.

Schemas for creating wireless profiles.

C:\WINDOWS\pss
I delete the pss folder and its contents.

C:\WINDOWS\Registration
I delete the Registration folder and its contents.

The Registration folder contains files that support COM+ applications. COM+ catalog files are .clb files and are located in the Registration folder. COM+ is designed to simplify the creation and use of software components. You manage COM+ using the Component Services in the Microsoft Management Console (MMC).

C:\WINDOWS\RegisteredPackages
I delete the RegisteredPackages folder and its contents.

The RegisteredPackages folder contains installation files. They look like Windows Media Player installation files.

C:\WINDOWS\repair
I delete the repair folder and its contents.

Registry backup files (These files are updated if you use NTBackup and choose to back up system state files.)

Per Rob Elder: "There are backup copies of the hive files in the repair directory. But if you are not running MSBackup, they are from the day that the operating system was installed. If you're using MSBackup then they are from the date of the last backup."

C:\WINDOWS\Resources
Contains files to support the user's shell interface. (Themes.)

Windows will not let you delete the C:\WINDOWS\Resources folder.

---------------------------------------

C:\WINDOWS\Resources\Themes

You can delete the Themes folder and its contents if you want, but read on first...

Once you have your system setup for using a particular "Luna Style" theme, you can actually delete most of the Themes folder contents.

Contained in the Themes folder are the Luna subfolder, the Luna.theme, and the Windows Classic.theme.

The Luna subfolder contains the Shell subfolder and the luna.msstyles.

The Shell subfolder contains these subfolders: Metallic, Homestead and NormalColor. Each of these three subfolders contains its own shellstyle.dll. Much of the internal colors and file bitmaps are contained in the shellstyle.dll. The shellstyle.dll is also used for the visual-style effects in task windows, such as in the Add or Remove Programs panel.

The luna.msstyles does not contain all the information for the Windows XP style Theme (Luna Theme). However, you do need the luna.msstyles if you want to use a Luna Theme.

Here's where it gets tricky. There is also a shellstyle.dll in the system32 folder (C:\WINDOWS\system32).

You can delete the shellstyle.dll from the system32 folder, as long as you keep the Themes folder, its Luna subfolder, and the one Shell subfolder of the particular "Luna Style" theme you are using (Metallic, Homestead or NormalColor), along with its shellstyle.dll.

Let me show you...

Let's assume you have seleted and are using Metallic (Silver Color Scheme) for your Luna Theme.

Delete these files and subfolders:

In C:\WINDOWS\Resources\Themes

Delete the Luna.theme
Delete Windows Classic.theme

In C:\WINDOWS\Resources\Themes\Luna\Shell

Delete the Homestead folder and its shellstyle.dll.
Delete the NormalColor and it shellstyle.dll.

And then you can delete the shellstyle.dll in C:\WINDOWS\system32.

To see the visual-style of the Add or Remove Programs panel, you must keep either the shellstyle.dll that is in the system32 folder, or the shellstyle.dll of the particular Luna Theme you are using. More importantly, without at least one of these shellstyle.dll presence, you will be unable to enter the Add or Remove Programs panel.

If you choose to use the Windows Classic Theme, you can fully delete the Themes folder and all its contents.

But if you choose to use the Windows Classic theme, and delete the Themes folder and its contents, you will still need the shellstyle.dll that is in the system32 folder in order to gain access to the Add or Remove Programs panel.

---------------------------------------

C:\WINDOWS\security
I delete the security folder and it's contents.

The security folder contains subfolders and files related to security. Includes log files that define the default security applied during setup and templates for assigning new security privileges.

C:\WINDOWS\setupupd
I delete the setupupd folder and its contents.

Dynamic Update storage location.

C:\WINDOWS\ShellNew
I delete the ShellNew folder.

---------------------------------------

C:\WINDOWS\SoftwareDistribution

Contains Microsoft Updates installation source files and folders downloaded by Microsoft Update.

You can delete the SoftwareDistribution folder and its entire contents if you first stop the Automatic Updates Service. Upon your next visit to the Microsoft Update Website, the Automatic Updates Service will restart itself automatically, (assuming that you merely "stopped" the Service, and not "disabled" it), and the SoftwareDistribution folder and all its contents will be rebuilt.

Over a period of time, the "DataStore" and "Download" subfolders can build up with old source files and folders from previously installed Microsoft Updates, with log files reflecting your visits to the site, and with log files created by the Automatic Update Service.

Periodically, I like to delete the contents of the "DataStore" and "Download" subfolders...with the except of these two files from the "DataStore" subfolder: the edb.chk and the edb.log. If these two files are deleted, you will need to reboot your computer before your next visit to the Microsoft Update Website...otherwise, the Microsoft Update Website will not function. In addition, these two files can be deleted only after your system settles in from after rebooting, or after a time from a visit to the Microsoft Update Website...while the Automatic Updates Service is running, that is.

---------------------------------------

C:\WINDOWS\srchasst
I delete the srchasst folder and its contents.

The srchasst folder contains files and subfolders for the Search Companion. I like the way Search Companion performs without these XP updates. (Even though the little puppy is kind of cute.)

---------------------------------------

C:\WINDOWS\system

The system folder contains 16-bit versions of protected and real mode drivers and .dll files used by applications. These files are provided for backward-compatibility with older applications. All but two of these backward-compatibility files have duplicates in the system32 folder.

You can delete the system folder and its contents. However, some older applications you install might look for some of the files in the system folder.

These files have duplicates in the system32 folder:

AVICAP.DLL......AVI Capture DLL
AVIFILE.DLL.....Microsoft AVI File support library
COMMDLG.DLL.....Common Dialogs libraries
KEYBOARD.DRV....WOW Keyboard Driver Module
LZEXPAND.DLL....Windows file expansion library
MCIAVI.DRV......MCI driver for AVI
MCISEQ.DRV......MCI driver for MIDI sequencer
MCIWAVE.DRV.....MCI driver for waveform audio
MMSYSTEM.DLL....System APIs for Multimedia
MMTASK.TSK......Multimedia background task support module
MOUSE.DRV.......WOW MOUSE Driver Module
MSVIDEO.DLL.....Microsoft Video for Windows DLL
OLECLI.DLL......Object Linking and Embedding Client Library
OLESVR.DLL......Object Linking and Embedding Server Library
SHELL.DLL.......Windows Shell library
SOUND.DRV.......WOW SOUND Driver Module
SYSTEM.DRV......Windows System Driver core component
TAPI.DLL........Microsoft® Windows™ Telephony Server1
TIMER.DRV.......Timer driver for PC compatibles
VER.DLL.........Version Checking and File Installation Libraries
VGA.DRV.........WOW Display Driver Module
WFWNET.DRV......Windows for Workgroups network driver

WINSPOOL.DRV...(Windows Spooler Driver). Important: If you choose to delete the system folder and its files, at least keep the copy of the WINSPOOL.DRV that is in the system32 folder, or you may not be able to reboot to Windows. Just be sure to keep one of them.

These two files do not have duplicates in the system32 folder:

setup.inf.......
stdole.tlb.....OLE 2.1 16/32 Interoperability Type Library

If you want, you can move "setup.inf" and "stdole.tlb" to the system32 folder, and then delete the system folder and its files. This way your system would still have copies of these backward-compatibility files.

Important Note: Should you choose to delete these files from both the system and the system32 folders, you may start receiving Application Errors similar to these when you go to restart or shutdown your computer:

Application popup: svhost.eve - Application Error: 0x7755d002 referenced memory at 0x00000004. The memory could not be read.

Application popup: <application name> - Application Error: The instruction at "<memory location>" referenced memory at "<memory location>". The memory could not be "written".

If this begins happening, try replacing the system folder and all its files.

---------------------------------------

C:\WINDOWS\Tasks
You can delete the Tasks folder and its contents, the Add Scheduled Task file (Scheduled Task Wizard), but if you have Task Scheduler Service running, the folder and its contents will be re-created upon your next reboot. I personally delete the Tasks folder and its contents because I have Task Scheduler Service disabled on my system. (See PART 2 under Task Scheduler.)

C:\WINDOWS\Temp
I delete any files I ever find in the Temp folder.

Note: It's a good idea to delete these files after a reboot. Some programs you install may use temporary installation files they place here to complete their installation upon the rebooting.

Additional Note: Windows Genuine Advantage installs the WGAErrLog.txt to the Temp folder. Should you delete this file, be sure to reboot your system, so that a new WGAErrLog.txt can be created. Otherwise, Microsoft Update may not work for you.

C:\WINDOWS\twain_32
I delete the twain_32 folder and its contents because I don't have a scanner.

The twain_32 folder contains files to support Twain technology, enabling a scanner document to be inserted into a file.

C:\WINDOWS\WBEM (Installed by Internet Explorer 7.)
I delete the WBEM folder and its contents.

C:\WINDOWS\Web
I delete the Web folder and its contents.

The Web folder contains files and subfolders to support Internet printing and document access.

---------------------------------------

C:\WINDOWS\WinSxS

The WinSxS folder stores the shared components of side-by-side applications. These can be multiple versions of the same application or the same assembly.

Microsoft keeps changing the rules with the WinSxS folder, constantly coming up with updates for it, new files, new subfolders. Programs sometimes install their own files and subfolders to it. It gets all very confusing.

Rather than go into great length and detail, suffice it to say that this is what I do with the WinSxS folder...and it has stayed this way since I first began removing files and subfolders from the WinSxS folder many years ago.

First I delete every .cat file in the Manifests subfolder, and in all the individual subfolders within the Policies subfolder.

C:\WINDOWS\WinSxS

I keep these subfolders and their contents, and delete all others:

x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03

x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.2600.2180_x-ww_522f9f82

C:\WINDOWS\WinSxS\InstallTemp

I delete the InstallTemp folder.

C:\WINDOWS\WinSxS\Manifests

I kept these files, and delete all others:

x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03.Manifest

x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.2600.2180_x-ww_522f9f82.Manifest

x86_Microsoft.Windows.Networking.Dxmrtp_6595b64144ccf1df_5.2.2.3_x-ww_468466a7.Manifest

x86_Microsoft.Windows.Networking.RtcDll_6595b64144ccf1df_5.2.2.3_x-ww_d6bd8b95.Manifest

x86_Microsoft.Windows.Networking.RtcRes_6595b64144ccf1df_5.2.2.3_en_16a24bc0.Man
fest

x86_Microsoft.Windows.SystemCompatible_6595b64144ccf1df_5.1.2600.2000_x-ww_bcc9a281.Manifest

C:\WINDOWS\WinSxS\Policies

I kept these subfolders and their contents, and delete all others:

x86_policy.1.0.Microsoft.Windows.GdiPlus_6595b64144ccf1df_x-ww_4e8510ac

x86_policy.5.1.Microsoft.Windows.SystemCompatible_6595b64144ccf1df_x-ww_a0111510

x86_policy.5.2.Microsoft.Windows.Networking.Dxmrtp_6595b64144ccf1df_x-ww_362e60dd

x86_policy.5.2.Microsoft.Windows.Networking.Rtcdll_6595b64144ccf1df_x-ww_c7b7206f

x86_policy.6.0.Microsoft.Windows.Common-Controls_6595b64144ccf1df_x-ww_5ddad775


NOTE: Nero 8 needs these:

C:\WINDOWS\WinSxS

x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700.manifest

x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_3bf8fa05.manifest

C:\WINDOWS\WinSxS\Manifests

x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700.manifest

x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_3bf8fa05.manifest


Nero 8 will send errors to the Event Viewer without these. However, Nero 8 will function without them.

C:\WINDOWS\WinSxS\Manifests

x86_Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_91481303.manifest

C:\WINDOWS\WinSxS\Policies

x86_policy.8.0.Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_x-ww_caeee150


--------------------

Slimming Down Windows XP: The Complete Guide is my gift to those who always wanted to know which files they can delete from Windows XP, but couldn't find their answers. I have always offered my guide freely, and never asked anything in return.

Those of you who wish to make a donation, showing your support and appreciation for Slimming Down Windows XP: The Complete Guide, My Batch Files Are Available Here