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.
Source: Microsoft.


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

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.

Recreating a VMFS-3 or VMFS-5 partition table in ESXi 5.x

For this kind of issues you need to engage VMware support on this, following any part of this article could lead to more complex situation if not ran by an expert.   Symptoms Datastore does not mount because of a lost or overwritten partition table.   Purpose When a VMFS partition is created in ESX 3.x or ESX 4.x, it has a Master Boot Record (MBR) partition map. The MBR is written to the first 512 B block (LBA0) and contains the information where the (VMFS) partition starts and ends. ESXi 5.0 introduced VMFS-5, which uses a GUID partition table (GPT) for new datastores. When a VMFS-3 partition is created in ESXi 5.x and is later updated to VMFS-5, the original partition map (MBR) is maintained. If the partition information of a VMFS datastore is deleted or overwritten (for example, by a Windows system with direct access to the same disks), it is impossible to determine if the partition map was GPT or MBR. The only time you can be sure that a GPT partition map was used is if th...

How to deploy an OVA in Cloud Director

  How to deploy an OVA in Cloud Director Yesterday I was in a call with a customer and we discussed uploading OVA’s into Cloud Director. I said sure that is no problem at all. Well then I started thinking how are you supposed to deploy an OVA in Cloud Director because I do not even remember how this is done. So I opened up Cloud Director and tried it for myself. I decided to make this blog post along the way to show you how to deploy an OVA in Cloud Director. As an added bonus I will also show you how to upload an OVA to the catalog. This way I can deploy the OVA over and over again. Environment information Cloud director 10.3 OVA How to deploy an OVA in Cloud Director In Cloud director I opened up the Applications section and selected “NEW” I am deploying an OVA so I selected “Add vApp From OVF”. In the screenshot below you can see all the steps involved with (in my case) deploying and customising the Usagemeter. Options to customise are for instance: Network settings, vApp naming...