Skip to main content

Clean up failed update or WinSxS Directory in Windows Server 2008 R2 with new Update

 Clearing Windows Update Cache Upon Update Failure




  1. Open Command Prompt by Start -> Run and type “cmd
  2. On the Command Prompt, type “net stop wuauserv“. This is done so that you will terminate the windows automatic update service to allow us to delete the cache files
  3. Still on the Command Prompt, type “cd /d %windir%” or “cd\windows
  4. Type “rd /s SoftwareDistribution
  5. Thats it, the cache has been purged. Now we need to restart the windows automatic update service again. To do that, type “net start wuauserv
  6. Or go to this link: http://support.microsoft.com/Default.aspx?kbid=971058



Clean up WinSxS Directory in Windows Server 2008 R2 with new Update


The WinSxS folder seems to be one stop solution for storing files added to your OS via Windows Update. The Winsxs folder, stores multiple copies of dll‘s in order to let multiple applications run in Windows without any compatibility problem. Microsoft releases dozens of updates every month to keep at bay the problems pertaining to certain incompatible applications, newly discovered bugs and security related issues. To ensure the updates don’t cause compatibility trouble, duplicate files by default gets stored in the WinSxS folder. Furthermore, some Windows updates are designed such that they can be uninstalled readily, should any instance of incompatibility be found. This may help in reverting back a computer to its previous state.
Thus, the WinSxS folder can grow large to take up substantial amount of hard disk space. The problem gets compounded when it starts storing files of updates that are no longer required, but still take up the hard disk space. Here the role of the Windows Update Cleanup feature come into play. The tool is designed to help you regain valuable hard disk space by removing bits of old Windows updates that are no longer seem valid.Windows 8 and Windows Server 2012 R2 offers a numbers of ways to cleanup of the WinSxS folder which includes the Windows Component Store. In Windows 8 and Windows 8.1, the OS will automatically reduce the size of the WinSxS. These methods include internal processes, such as uninstalling and deleting packages with components that have been replaced by other newer components. Previous versions are then kept for a period of time, after which they are automatically removed. Windows 8.1 introduced a new command line option for DISM.exe, /AnalyzeComponentStore. Running this command, will analyze the WinSxS folder and tell you whether a Component Store Cleanup is recommended or not. In October last year, Microsoft released an Update that added the Windows Update Cleanup option to Disk Cleanup tool in Windows 7.Disk Cleanup wizard add-on for WinSxS in Windows Server 2008 R2

Just last week, Microsoft released an update that added the ability to clean up the WinSxS directory and component store on Windows Server 2008 R2. The tool however, in order to function, requires Desktop Experience feature to be installed.You will have to install the update and install the Desktop Experience feature.

Select the button to Add Required Features and click Next and then Install.



To complete the installation process a reboot is required. When presented with the installation Results screen, click close and reboot as advised.


With that done, the process of configuring Windows features starts up. It may take a while to configure the changes so, do not turn of your computer while the changes are being made to your system.When done, your machine will reboot and start. Open the Disk Cleanup tool > Start > All Programs > Accessories > System Tools.



Upon launching the tool, it will prompt for the drive you would want to clean up. Select the desired drive and hit the OK button.



Instantly, the command triggers the scanning action. The tool will calculate the amount of free space you intend to keep. Accordingly, the process may take from few seconds to minutes to complete the process. At this juncture, several options will be offered to you forcleanup, including a new option for Windows Update Cleanup.



Now, upon completion of the process of creating some free space, reboot your machine and notice if the WinSxS directory has been reduced to the required size. It should.The update is available on Windows Update. It can also be manually downloaded from the Microsoft Update Catalog. You can also download the Disk Cleanup Wizard add-on installed with the Desktop Experience feature from KB2852386.
SourceMicrosoft.


Also some other methods.
WinSxS is a Windows folder which is having Windows Component Store files. WinSxS Folder cannot be deleted but you can reduce it's size by doing any of the method above,

Method 1:
Using Start Component Cleanup.

Method 2:
Using command prompt
command used:
Dism.exe /online /Cleanup-Image /StartComponentCleanup

Comments

Popular posts from this blog

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the ...