locked
WINSXS

    Question

  • Hello,

    My Winsxs firectory has grown to 7GB large and is sucking up the available space I have allocated to my C:\ drive.  Is there anyway to delete the files out of this directory?

    Tommy

    Tommy Rotunno
    Thursday, April 23, 2009 1:56 PM

Answers

  • hi tommy,

    many users have posted earlier about the increase in size of winsxs folder and below is the explanation


    From David Shen

     

    Based on the research, all the necessary files for specific additions, roles, applications will be contained in the %windir%\Winsxs directory. The %windir%\winsxs folder (also referred to as the component store) is used to store all the installation source files that is needed for Windows Server 2008 to service itself and its optional components, which takes the place of the traditional flat from media.

     

    All the shared and private assemblies, manifests, backed up system files, etc, are critical to the operation system of Windows Server 2008 and all of the installed programs. If any of these shared assemblies are removed and you install a program that requires that assembly, the program will simply refuse to run.
     

    Here is a blog which describe it in detailed.

    What is the WINSXS directory in Windows 2008 and Windows Vista and why is it so large?http://blogs.technet.com/askcore/archive/2008/09/17/what-is-the-winsxs-directory-in-windows-2008-and-windows-vista-and-why-is-it-so-large.aspx

    If you want to decrease the space that the Winsxs folder takes, you may consider the way which is described in the following Blog.

    What's winsxs\manifestcache\(something)_blobs.bin?
    http://blogs.msdn.com/jonwis/archive/2009/01/13/what-s-winsxs-manifestcache-lt-something-gt-blobs-bin.aspx

    =======================================================


    Additional info

    hi there,

    many users have reported the issue of winsxs folder getting increased in size, this folder is basically a OS folder which you should not modifiy / play around with. OS stores dll refernce files in windows sxs ( side by side ) folder which is very much needed for OS to refer to particular version of dll

    below is the excellent post explaining the same ( they have explained for windows vista ) but windows sxs folder does same job on all flavour OS .

    http://social.technet.microsoft.com/forums/en-US/itprovistaannouncements/thread/9411dbaa-69ac-43a1-8915-749670cec8c3/


    sainath Windows Driver Development
    Thursday, April 23, 2009 2:45 PM
    Moderator
  • Hello Tommy,
    The thing to remember is this is really your OS.  Most of the files in the various Windows folders are really just hard links to the same files you are seeing when looking at winsxs.  The files really  don't  take up space in the winsxs and one of the other folders, it only lives once on the drive.  But if you look at the folders individually the numbers appear larger than the total disk space consumed
    Thanks, Darrell Gorter[MSFT] This posting is provided "AS IS" with no warranties, and confers no rights
    Thursday, April 23, 2009 8:48 PM
  • Hi,

    Sainath and Darrell have provided correct information for you. Generally speaking, we don’t need to worry about the size of WinSxS folder. But if you would like to reduce its size, you can try the following tools:

    The WinSxS folder in Vista and Windows Server 208 has the same function, so you can use the VSP1CLN file to remove some files in WinSxS folder.

    http://technet.microsoft.com/en-us/library/cc709655.aspx


    However, correct knowledge of WinSxS folder is important before you take any action.

    From the "WinSxS directory" section of the following article:
    http://blogs.msdn.com/e7/archive/2008/11/19/disk-space.aspx

    We can find:

    "Nearly every file in the WinSxS directory is a “hard link” to the physical files elsewhere on the system—meaning that the files are not actually in this directory. For instance in the WinSxS there might be a file called advapi32.dll that takes up >700K however what’s being reported is a hard link to the actual file that lives in the Windows\System32, and it will be counted twice (or more) when simply looking at the individual directories from Windows Explorer."

    "In reality it doesn’t actually consume as much disk space as it appears when using the built-in tools (DIR and Explorer) to measure disk space used"

    Please also refer to the "Where does the disk space go?" section to get more information.

    Thanks.

    This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, April 24, 2009 10:07 AM
    Moderator

All replies

  • hi tommy,

    many users have posted earlier about the increase in size of winsxs folder and below is the explanation


    From David Shen

     

    Based on the research, all the necessary files for specific additions, roles, applications will be contained in the %windir%\Winsxs directory. The %windir%\winsxs folder (also referred to as the component store) is used to store all the installation source files that is needed for Windows Server 2008 to service itself and its optional components, which takes the place of the traditional flat from media.

     

    All the shared and private assemblies, manifests, backed up system files, etc, are critical to the operation system of Windows Server 2008 and all of the installed programs. If any of these shared assemblies are removed and you install a program that requires that assembly, the program will simply refuse to run.
     

    Here is a blog which describe it in detailed.

    What is the WINSXS directory in Windows 2008 and Windows Vista and why is it so large?http://blogs.technet.com/askcore/archive/2008/09/17/what-is-the-winsxs-directory-in-windows-2008-and-windows-vista-and-why-is-it-so-large.aspx

    If you want to decrease the space that the Winsxs folder takes, you may consider the way which is described in the following Blog.

    What's winsxs\manifestcache\(something)_blobs.bin?
    http://blogs.msdn.com/jonwis/archive/2009/01/13/what-s-winsxs-manifestcache-lt-something-gt-blobs-bin.aspx

    =======================================================


    Additional info

    hi there,

    many users have reported the issue of winsxs folder getting increased in size, this folder is basically a OS folder which you should not modifiy / play around with. OS stores dll refernce files in windows sxs ( side by side ) folder which is very much needed for OS to refer to particular version of dll

    below is the excellent post explaining the same ( they have explained for windows vista ) but windows sxs folder does same job on all flavour OS .

    http://social.technet.microsoft.com/forums/en-US/itprovistaannouncements/thread/9411dbaa-69ac-43a1-8915-749670cec8c3/


    sainath Windows Driver Development
    Thursday, April 23, 2009 2:45 PM
    Moderator
  • Thanks for the info.  It looks like there is no way to shrink that directory which is crazy.  Microsoft really dropped the ball here, I have 7GB being taken up by that folder.



    Tommy Rotunno
    Thursday, April 23, 2009 3:22 PM
  • Hi Tommy,


    • Vista Service Pack 1 contains a binary called VSP1CLN.EXE, a tool that will make the Service Pack package permanent (not removable) on your system,  and remove the RTM versions of all superseded components.

    http://sreekarun.livejournal.com/8015.html

    Sree


    SomeOne
    Thursday, April 23, 2009 3:32 PM
  • But I am running Windows Server 2008 64bit not Vista.
    Tommy Rotunno
    Thursday, April 23, 2009 3:34 PM
  • hi tommy,

    did you had a chance to go through my eariler post in which there is detailed info about winsxs and link to reduce the size of winsxs folder


    sainath Windows Driver Development
    Thursday, April 23, 2009 5:18 PM
    Moderator
  • Hello Tommy,
    The thing to remember is this is really your OS.  Most of the files in the various Windows folders are really just hard links to the same files you are seeing when looking at winsxs.  The files really  don't  take up space in the winsxs and one of the other folders, it only lives once on the drive.  But if you look at the folders individually the numbers appear larger than the total disk space consumed
    Thanks, Darrell Gorter[MSFT] This posting is provided "AS IS" with no warranties, and confers no rights
    Thursday, April 23, 2009 8:48 PM
  • Hi,

    Sainath and Darrell have provided correct information for you. Generally speaking, we don’t need to worry about the size of WinSxS folder. But if you would like to reduce its size, you can try the following tools:

    The WinSxS folder in Vista and Windows Server 208 has the same function, so you can use the VSP1CLN file to remove some files in WinSxS folder.

    http://technet.microsoft.com/en-us/library/cc709655.aspx


    However, correct knowledge of WinSxS folder is important before you take any action.

    From the "WinSxS directory" section of the following article:
    http://blogs.msdn.com/e7/archive/2008/11/19/disk-space.aspx

    We can find:

    "Nearly every file in the WinSxS directory is a “hard link” to the physical files elsewhere on the system—meaning that the files are not actually in this directory. For instance in the WinSxS there might be a file called advapi32.dll that takes up >700K however what’s being reported is a hard link to the actual file that lives in the Windows\System32, and it will be counted twice (or more) when simply looking at the individual directories from Windows Explorer."

    "In reality it doesn’t actually consume as much disk space as it appears when using the built-in tools (DIR and Explorer) to measure disk space used"

    Please also refer to the "Where does the disk space go?" section to get more information.

    Thanks.

    This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, April 24, 2009 10:07 AM
    Moderator
  • Hi Darrel,

    Explorer shows that my winsxs directory takes up 7GB of space.  If most of that was not real due to hardlinks, then I would expect that the total used space for C: reported by Explorer would be larger than that reported by chkdsk, because it is counting gigabytes of phantom used space in winsxs.  However, the numbers match with chkdsk, which leads me to believe that the 7GB number is correct, unless chkdsk itself is being fooled by hardlinks, in which case is there any way to know how much free space is left on my drive?  Also, when I subtract the total used space reported by explorer from the size of my partition, it matches the free space reported by Windows on the partition.  So, is the 7GB real or not?
    Thanks.
    Monday, May 11, 2009 8:41 PM
  • After much research, I understand that winsxs IS the operating system.  However I would like to know whether all the amd* directories can be manually deleted since I have an x86 machine?  It seems ridiculous to require us to just live with the system bloat for a processor we don't even have.  SSDs are very expensive and would be nice to have for the boot drive, but having this directory constantly growing is just not right.  Is there any way we can move it to a secondary drive and have the OS refer to it there?
    Tuesday, August 02, 2011 4:37 PM
  • Hello,

    I have gone through so many post regarding this. I found only one solution, that is: install service pack 1 or 2, and run the "compcln.exe" or what so ever! Now, I should say the only one solution i found is not the "solution".

    My winsxs folder is 3.89GB, and I want to reduce it, so I install services pack that require more than 5GB space!! after installation it can take 5+3.89=8.89GB, lets say I run the cmd.. will it reduced into 2GB? where as the pck itself need 5GB!! who knows how much it can reduce?? I better not install the pck 1 or 2...!! what is the use of installing the pck in this case? wasting time!

    I think, Microsoft engineers  need to comes up with some tool that can reduce it!!

    Thank you

     

    Thursday, November 10, 2011 7:17 AM
  • Hello,

    What OS are referring to and what is the size of your volume that the OS is installed to?

    What are you using to determine the size of folder and is it Hard-link aware?

    Can you try the Disk Usage tool from the sysinternals site?
    http://technet.microsoft.com/en-us/sysinternals/bb545046.aspx

    drop into a \tools folder

    C:\Tools>du /v /u c:\Windows >Win_Folders.txt 

     


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en
    Sunday, November 13, 2011 7:54 PM
  • I have Windows 2008 Server SP2. Other than the operating system, I have 3 or four application installed that are less than 7 GB.  The total space allocated to the C drive is 65GB.  Now I only have 1.6 GB free and I am running into space problems.  the WINSXS file is about 20 GB and growing.  This cannot be right.  How do I stop losing space?

    Wednesday, November 30, 2011 6:10 AM
  • Hello,

    Can you try the Disk Usage tool from the sysinternals site?
    http://technet.microsoft.com/en-us/sysinternals/bb545046.aspx

    drop into a \tools folder

    C:\Tools>du /v /u c:\Windows >Win_Folders.txt

    Make this available so we can look at what is consuming space


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en
    Wednesday, November 30, 2011 7:20 PM
  • I believe people are saying over and over what's big, and MS engineers should really take it seriously.

    WINSXS folders are taking large amount of space - way more than OS itself!

    I cannot believe what sort of engineers won't take this seriously, especialy ones who work on something which is supposed to be an "Enterprise Software". Is this the reason why MS OS is loosing the market share, and people are being more and more frustrated by Windows team?

    Installing windows takes ~4GB. Works perfectly fine initially. Than it start srawling, until it becomes useless.

    WinSXS folder now 7GB, entire Windows 11GB. Any reason for this? Any reason not to reduce the size, or optimize its usage?

    Imagine this when you multpiple it by 10, 20, 100 Servers? How much storage would you waist? How big your Windows OS disk needs to be to accomodate for an enteprize applicatino over few years of its production life-cycle?

    C'mon MS guys, I believe you're good engineers, I still believe in you and you can do it better - fix this thing, and don't just tell us by more storage, or faster machines. It won't work.

     

    Thursday, December 01, 2011 1:14 AM
  • Same problem at our company. I don't see any difference in using treesize program or DU tool like suggeted above.


    TreeSize Professional Report, 21/02/2012  11:51
      Drive: c$ on 'server' (Y:)
    Drive: Y:\     Size: 15.351,1 MB     Used: 12.275,9 MB     Free: 3.075,2 MB        4096 Bytes per Cluster (NTFS)

    Full Path       Size            Allocated       Files           Folders         % of Parent     Last Change     Last Access   
    Y:\ 12.993,4 MB 13.145,7 MB 84.978  15.747  100,0 % 21/02/2012 21/02/2012
    Y:\Windows 11.526,7 MB 11.657,1 MB 68.106  11.640  88,7 % 21/02/2012 21/02/2012
    Y:\Windows\winsxs 5.892,5 MB 5.958,1 MB 34.151  8.762  51,1 % 15/02/2012 21/10/2011
    Y:\Windows\System32 3.847,1 MB 3.900,5 MB 26.742  1.525  33,5 % 21/02/2012 21/02/2012

    output du /v /u c:\Windows below

                 ...  

                 21  c:\windows\winsxs\x86_xrxscan.inf.resources_31bf3856ad364e35_6.0.6001.18000_en-us_ef6ff684af922a40
       6.033.955  c:\windows\winsxs
      11.803.350  c:\windows

    Totals:
    Files:        68106
    Directories:  11639
    Size:         12.086.630.774 bytes
    Size on disk: 12.332.617.728 bytes

    Winsxs is 6GB large and I don't see any readon why ! It couldn't be that hard to make a good OS without draging all the file history with us from the installbase !?

    du /v /u c:\Windows
    Tuesday, February 21, 2012 10:55 AM
  • Microsoft needs to address this officially - not in forums. Is there a Microsoft document that addresses this? I have a lot of servers that are virtualized, taking up space on the SAN. All of these virtual servers are wasting disk. Either the reporting tools in the operating system are wrong, or the disk space is really tied up, but my monitoring systems think the disks are getting full, and as far as copying files, or installing patches go, the disk is seen as being full. I don't want to allocate a bunch of space on the SAN for this retarded misuse of disk. I generally create my Windows 2008 r2 virtual servers with a 25GB system volume, and that should be plenty. How it's filled up varies greatly among my servers, depending on what's installed. This is a bad one. It's an application server in a Sharepoint 2010 farm.

    Here's the DU output, first on c:\windows, then on c:\. Is Microsoft telling me that I don't need to worry about this drive reporting that it only has 300M free now because these are duplicate files?

    11,989,370  c:\windows\winsxs
    22,389,288  c:\windows

    Totals:
    Files:        88149
    Directories:  21478
    Size:         22,926,631,423 bytes
    Size on disk: 23,216,680,960 bytes

    11,989,370  c:\Windows\winsxs
    22,392,247  c:\Windows
    24,460,789  c:\

    Totals:
    Files:        104420
    Directories:  24074
    Size:         25,047,848,628 bytes
    Size on disk: 25,271,861,312 bytes

    Tommy

    Tuesday, February 21, 2012 9:37 PM
  •  I also stumbled over this winsxs and disk space problem. MS states in their system requirements for W8K that minimum disk space is 10GB. I think they should update their document because this is only for installing W8K not running it and keeping it updated. If you want to keep your system up-to-date then the 10GB isn't minimum but its 20-30-40 GB? We have internal CA running on W8K and ignorant as I was I installed it on 15GB partition because there wasn't any other application planned on this server. And now after a couple years I have some 700MB free and I must start planning for disk expansion(luckily its virual machine and we have partiton management tool for that). And MS really don't mention that W8K installation is supposed to grow that much and you should plan according your server installation according to this because there is no way to delete old updates and reduce the size of windows installation.
    Monday, March 05, 2012 10:11 AM
  • du /v /u c:\Windows >Win_Folders.txt

    The value in Win_Folders.txt for C:\Windows\Winsx is only for the files that are directly in that folder.  It does not include files in the subfolders.  To get the total of all of the files in C:\Windows\Winsxs you need to use:

    du /v /u c:\Windows\Winsxs
    Which will provide you with a sum of all of the space used as the last line of output.


    http://www.saberman.com


    • Edited by saberman Saturday, March 24, 2012 3:36 AM cutoff
    Saturday, March 24, 2012 3:35 AM
  • Time does not stop, and I am still looking for a solution about this issue.

    We have 30+ Windows 2008 R2 servers. We have 50GB disks for System drive and winsxs is using at least 20% of it!!! I read a lot about winsxs and no one knows for sure how to eliminate it or at least make it smaller. Come on Microsoft, give us a solution for this. SAN disks are too expensive to be wasted for something we dont really need!


    Diego de Azevedo IT Analyst - MCSE, MCITP

    Wednesday, May 02, 2012 1:55 PM
  • Time does not stop, and I am still looking for a solution about this issue.

    We have 30+ Windows 2008 R2 servers. We have 50GB disks for System drive and winsxs is using at least 20% of it!!! I read a lot about winsxs and no one knows for sure how to eliminate it or at least make it smaller. Come on Microsoft, give us a solution for this. SAN disks are too expensive to be wasted for something we dont really need!


    Diego de Azevedo IT Analyst - MCSE, MCITP

    If Service Pack is installed on 2008 R2 Servers, you can use following command to free up some space

    dism /online /cleanup-image /spsuperseded [use elevated cmd (run as Administrator)]

    Also, please refer following discussion

    Dism command in windows 2008 SP2 

    http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/75b7edb0-4bb2-4337-af23-85e3ff179d92


    A UNIVERSE without WINDOWS is CHAOS !

    This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

    About Me ?

    • Proposed as answer by Mandrew2000 Monday, February 25, 2013 8:13 PM
    Wednesday, May 02, 2012 2:51 PM
    Moderator
  • let's face it, this is an administrators nightmare.  

    I don't really care if "nearly every file in the WinSxS directory is a “hard link” to the physical files elsewhere on the system", in fact I'm tired of seeing this posted when people are experiencing real difficulties with HDD space - this is like telling a dying man "Cancer is a terrible thing and can attack any part of any person".... we KNOW all this but strangely, regurgitating it until it becomes hackneyed and tired is NOT a technical solution and doesn't clear any space on a servers struggling disks.

    I tried explaining to a furious Service Manager that the reason the critical system, accessed by around 3500 users nationwide, was unavailable in the middle of the night was because the server had received a set of updates which together with the 'hard links' had pushed the box over the edge.  How surprised was I when instead of 'Oh I see, so it could be a misrepresentation in the amount of diskspace used due to a potential doubling up of the file usage reported by the O/S -  thats OK' I received a less 'understanding' reply 

    I know I have the option to run dism /online /cleanup-image /spsuperseded and believe me, I have tried it - failed with different errors on different servers (the most ironic being ' Service Pack Cleanup can't proceed: No service pack backup files were found. The operation completed successfully.) why were no service pack backup files found... the $ServicePackUninstall folder was removed by an engineer awoken at 3:00am by Operational Support to resolve an unavailable service, and if dism doesn't reference this folder, then it has failed epically and NOT completed successfully as reported by the O/S

    Here's a question I cannot find an answer to - if the space usage is doubled up, does the O/S recognise this and allow data to be written to the diskspace 'used' by the phantom files?  ie am I to expecting to see:  Total DiskSize 60Gb           Used 65Gb  if not, then the 'hard link' thing really IS the worlds most useless piece of IT information - we know what the problem is, we know what causes it, we know that it's affecting millions of devices around the world....but there is nothing that can be done :(

    What I would like to see is a solution that works properly and allows my O/S to function as happily, a year down the line, as it did when first installed when it used around 9Gb instead of 24Gb .... any takers??

    Friday, August 03, 2012 9:42 AM
  • Hello,

    The real question is what is occupying the space on the machine.  yes something is occupying the space but it's likely not the winsxs that is causing the issue, the growth is likely in a lot of different folders different for different people.

    Can you try the Disk Usage tool from the sysinternals site?
    http://technet.microsoft.com/en-us/sysinternals/bb545046.aspx

    drop into a \tools folder then run

    C:\Tools>du /v /u c:\ >Files.txt

    Make the output available.

    This will help target what folders are really occupying space on the system


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

    Friday, August 03, 2012 10:02 PM
  • Windows 7 Ultimate x64 With All Important Patches built from an ISO with SP1 in it.

    9,329,116  c:\Windows\winsxs

    That is a significant amount of space to give up in a VM.

    Edit:

    This is from du /v /u.

    • Edited by saberman Sunday, August 05, 2012 10:46 PM
    Friday, August 03, 2012 11:30 PM
  • Did anyone ever create a case in Microsoft Connect?

    Yes, this is a problem.  Yes, hard-links explanation is an ignorant response from MS support.  Yes, server ARE being affected b/c what is reported is what is used by the OS to determine if it can write to a disk.

    I have 200+ Hyper-V VM's... many of which are 2008 R1.  I have winsxs directories ranging from 5GB to 20GB.  The VHD's for the VM's are dynamic disks.  I had a server run out of disk space b/c of the WINSXS folder growth.  I looked at the VHD.  It had expanded to 101% of the allocated space.  This means hard-links is fruitless and actual space is being used. 

    Is the solution to reinstall?  No.   But this is probably a conspiracy to force upgrades to R2 to flush out the winsxs growth.  Afterall, they have a space recovery tool for R2 :) 

    Saturday, August 04, 2012 3:07 AM
  • Hello,

    Do you have the data I requested from the images or installations with the issue?

    Can you try the Disk Usage tool from the sysinternals site?
    http://technet.microsoft.com/en-us/sysinternals/bb545046.aspx

    drop into a \tools folder then run

    C:\Tools>du /v /u c:\ >Files.txt

    Make the output available.

    This will help target what folders are occupying space on the system


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

    Sunday, August 05, 2012 10:23 PM
  • If you can provide a location to drop off the file, I have one ready for you.   I cannot post here, too large.

    A snippet here.

      13,009,429  c:\Windows\winsxs
      24,100,664  c:\Windows
      29,386,214  c:\

    Totals:
    Files:        102068
    Directories:  23892
    Size:         30,091,483,580 bytes
    Size on disk: 30,146,105,440 bytes

     

    Monday, August 06, 2012 4:10 AM
  • Hello,

    Do you have a skydrive account or could you get one and post it there?

    Can you zip the file up and then email it to me?

    First Name and Last Name initial at Microsoft.com


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

    Tuesday, August 07, 2012 4:30 PM
  • I have forwarded you the details @microsoft.com
    Thursday, August 09, 2012 4:36 AM
  • win8 - and what they fixed: nothing, same damn big folder, and without start menu ;/
    Thursday, August 09, 2012 7:08 AM
  • Hello Millertime78,

    Hmm I have not seen it yet. 

    How big was the file? 

    darrellg [delete this] @microsoft.com


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

    • Proposed as answer by Mandrew2000 Monday, February 25, 2013 8:12 PM
    • Unproposed as answer by Mandrew2000 Monday, February 25, 2013 8:12 PM
    Thursday, August 09, 2012 6:03 PM
  • This has worked great for my 2008 R2 Standard SP1 virtual, the WinSxS size has gone down from 11275.3 MB to 7237.4MB

    with the following message:


    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385

    Image Version: 6.1.7600.16385

    Removing backup files created during service pack installation.
    Removing package Microsoft-Windows-ServerEnterpriseEdition~31bf3856ad364e35~amd64~~6.1.7600.16385
    [==========================100.0%==========================]
    Service Pack Cleanup operation completed.
    The operation completed successfully.

    Also found the same solution here: http://www.happysysadm.com/2011/06/clean-up-winsxs-on-windows-2008-r2.html

    The procedure is the following:
      • Install Windows Service Pack 1 then ...
      • Start and elevated command prompt (run 'CMD' as administrator) and ...
      • Run the DISM command, which replaces the old VSP1CLN and COMPCLN we used on previous Windows versions: DISM.exe /online /Cleanup-Image /spsuperseded
      • Wait 10 minutes before the task completes ( it ends with “Service Pack Cleanup operation completed. The operation completed successfully”)
      Normally you should have been able to reduce the Winsxs folder size by 1 or maybe 2 GBs, sometimes more. Saved space may vary a lot.
      Just know that after using DISM you will not be able to uninstall the Service Pack 1 anymore.
      Let's have a look at the used switches for DISM.exe:
      • The /online switch tells DISM to work on the running OS installation
      • The /spsuperseded option removes the backup  files created during installation.
    Optionally you could use the /hidesp option which will remove SP1 (KB976932) from the “Installed Updates” section of Programs and Features, to ensure that users do not try to uninstall the Service Pack.

    I hope this helps. Please let me know how much disk space you were able to free up using the given command.

    • Edited by Mandrew2000 Monday, February 25, 2013 8:18 PM
    Monday, February 25, 2013 8:15 PM
  • Just curious if there was any resolution for the reported issue?
    Monday, February 25, 2013 11:45 PM
  • Here are a couple of files with the du command output for C: and for C:\windows\winsxs

    http://sdrv.ms/16Gawif

    http://sdrv.ms/16GaBCD

    For winsxs Totals:

    Files:        53403
    Directories:  12316
    Size:         12,681,452,461 bytes
    Size on disk: 12,859,752,448 bytes
    Sunday, April 07, 2013 3:35 PM
  • Just curious if there was any resolution for the reported issue?
    me too, trying to gain some space on a Vista laptop with 60 GB hard drive.
    Sunday, April 07, 2013 3:37 PM
  • OK, so what we supposedly know is that:

    A) WinSXS folder are hard links to other files and doesn't actually take up any space.

    B) Windows Explorer and all other file tools and Windows components report that WinSXS folder IS taking up space.

    And what I know...

    C) I can defrag the WinSXS folder, which is weird since there are no real files in there...{using defraggler, grrr}

    Conclusion: It doesn't matter if those links are actually taking up space because everything that is reporting back to the OS says it IS taking up space.  If the WinSXS folder states that it is taking up 10GB, than it IS taking up 10GB because I don't have access to that space.  When was the last time you saw a hard drive that had the details of "37GB of 30GB used?"  If this hard-link theory is correct, than that (37 of 30) should be something we see all the time, but I have yet to see a screen shot or report of said information.  I am not God of course, so there may be something out there that I haven't seen.

    I have a hosted VM and am only allocated 30GB primary drive (C:) period. Expanding the drive isn't an option, not part of the services offered.  I already have all that I can moved over to the secondary hosted drive (D:).

    Those green boxes should be unmarked as answers, because there is something wrong still with Win8 and Server2012 and the WinSXS folder.  The idea is sound, the administrative portion of it is not sound.

    Tuesday, June 18, 2013 4:49 PM