Helping people with computers... one answer at a time.

ServicePackFiles contains the files updated by the Service Packs issues since your install. It can be deleted if you have the files elsewhere.

I just installed service pack 2 for my Windows XP Home Edition. Can I remove the service pack files folder in my windows folder?

Yes, but you probably don't really want to.

Let me explain why.

The short answer is that if you remove it, you may at some future date be asked to insert the Windows installation CD if Windows believes it needs to install or repair an operating system file. The problem is that your CD probably only has SP1 on it, if that. Windows will insist on your inserting the SP2 disk - which you likely don't have.

If you leave the folder, usually C:\WINDOWS\ServicePackFiles, and its contents in place, then Windows can simply pick up what it needs, when it needs it from there without ever bothering you.

It's very much like the I386 folder that I've discussed before. In fact, on my machine at least, there's an I386 folder within C:\WINDOWS\ServicePackFiles that actually contains all the files updated by service pack 2. So the best way to think of that ServicePackFiles is as an SP2 update to the I386 folder that may be elsewhere on your machine.

"You can delete it, just be prepared to need to insert your original installation CD if Windows ever needs it, as well as an SP2 CD if you have one."

In a sense the I386 folder (and the ServicePackFiles\I386 folder) are conveniences. They're really just there because the disk space to hold them is small these days compare to drive sizes, and they allow Windows to silently and quickly grab files it needs. The best example is when you install a new device. Normally Windows would ask you for the installation CD in order to get the drivers needed for that device. With the I386 folders already on your machine, Windows can simply get what it needs from there. Presumably it first checks the ServicePackFiles\I386 folder for updated files and if none are found it looks in the original I386 folder.

You can delete it, just be prepared to need to insert your original installation CD if Windows ever needs it, as well as an SP2 CD if you have one.

The good news is that like the I386 folder, you can move your ServicePackFiles instead of deleting it. You just need to change a registry setting to do so.

Using Registry Editor, locate the key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\SourcePath. Here's mine right now:

SourcePath registry setting

Here you can see that I've altered the SourcePath setting to control where my I386 folder lives (I've placed it on a server named "freenas" on my network in a shared "notenmax", and in a folder "\machine_specific\leo\i386" - note that the i386 portion isn't specified in the registry).

We can make a similar change for the ServicePackFiles by changing the ServicePackCachePath and ServicePackSourcePath entries. Here's mine after making that change:

ServicePack registry settings

Here you can see that I've told Windows to find the service pack files out on that other server on my network. After copying the contents of the folder to that location on that server, I can now safely delete ServicePackFiles on my machine.

Article C3192 - October 25, 2007

Leo Leo A. Notenboom has been playing with computers since he was required to take a programming class in 1976. An 18 year career as a programmer at Microsoft soon followed. After "retiring" in 2001, Leo started Ask Leo! in 2003 as a place for answers to common computer and technical questions. More about Leo.

Not what you needed?

Recent Comments
15 Comments

Its always preferable to compress the folder servicepackfiles\I386 rather than deleting.

Posted by: shiva at February 17, 2009 4:30 AM

Just FYI, If you make this registry change, you may need to point the location in all the Windows Side-By-Side Assemblies to the same location. Once an assembly is installed, it retains the full path to the old service pack files folder. Notice about 80 entries of the following under codebases... so be preparred to actually edit each assembly's location in the registry, because you still may wind up with the insert cd issue otherwise.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Installations\x86_Microsoft.Tools.VisualCPlusPlus.Runtime-Libraries_6595b64144ccf1df_6.0.9792.0_x-ww_08A6620A\Codebases\U_KB924667]
"Prompt"="Windows Server 2003 KB924667 Source Files"
"URL"="D:\\Support\\ServicePackFiles\\i386/vcrtl.man"

Posted by: Jason Raymond at January 28, 2010 8:32 AM

To Leo & Jason Raymond

Thankyou both very much for this tip, you've just allowed me to resurrect my EeePC which was struggling badly with 10MB of free disk.

BTW I've also relocated the contents of "C:\WINDOWS\SoftwareDistribution\Download" (some 750MB) and am looking into the Fonts issue.

Q: What about "C:\WINDOWS\Installer" (700MB) any ideas on moving that beastie??

Cheers, Ian.

Posted by: Ian Timms at February 21, 2010 1:01 AM

Trying to create a recovery/install CD for Windows XP Pro w/SP3. I cannot locate i386 folder in c:\ or c:\windows but there is an i386 folder at c:\windows\spervicepackfiles\i386. Is this what I need to make my CD? I've tried several methods and keep getting error messages like, cannot find NTLDR,and others even though said file(s) exist in the directory I am trying to burn to CD.

Posted by: Ken Browne at February 12, 2011 12:46 PM

Wonderful clue, solved my disk space problem - I have a small partition for system. Thanks a lot!

Posted by: Rogerio Dias at January 28, 2012 2:10 PM
Post a comment on "Can I remove the "ServicePackFiles" folder from my Windows folder?":





Remember Me?

(You may use HTML tags for style)

Before commenting, please...

  • READ THE ARTICLE. A comment that shows you didn't will be deleted and ignored.

  • Comment only on the article. Use the search box at the top of the page if you have a question about something else.

  • NO PERSONAL INFORMATION in the comment. No email addresses. No phone numbers. No physical addresses.

  • Anything that looks the least bit like spam will be deleted. Links to unrelated sites or links that appear to be primarily promotional will be deleted, or the comment will be deleted.

  • Don't ask me to recover lost passwords or hacked accounts. I can't. Those comments will be deleted.

  • I can't respond to every comment. And I can't vouch for the accuracy of others who do.

Please wait. Your comment is being processed ...