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

ما هى ال FSMO Roles

  بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master و هى عباره عن 5 Roles فى ال Active Directory و هما بينقسموا لقسمين A - Forest Roles 1- Schema Master Role و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role واحد فى ال Forest بيكون موجود على Domain Controller و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd regsvr32 schmmgmt.dll 2-Domin Naming Master و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain ليهم نفس الاسم فى ال Forest و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts B- Domain Roles 1-PDC Emulator و هى ال Role اللى بتتحكم فى ال Password change فى ال domain و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين و بيتم التحكم فيها من خلال ال Active directory Users & Computers عن طريق عمل كليك يمين على اسم الدومين و نختار operations master فى تاب ال PDC Emu

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output

Unlock the VMware VM vmdk file

  Unlock the VMware VM vmdk file Kill -9 PID Sometimes a file or set of files in a VMFS become locked and any attempts to edit them or delete will give a device or resource busy error, even though the vm associated with the files is not running. If the vm is running then you would need to stop the vm to manipulate the files. If you know that the vm is stopped then you need to find the ESX server that has the files locked and then stop the process that is locking the file(s). 1. Logon to the ESX host where the VM was last known to be running. 2.  vmkfstools -D /vmfs/volumes/path/to/file  to dump information on the file into /var/log/vmkernel 3.  less /var/log/vmkernel  and scroll to the bottom, you will see output like below: a. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)FS3: 130: <START vmware-16.log> b. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)Lock [type 10c00001 offset 30439424 v 21, hb offset 4154368 c. Nov 29 15:49:17 vm22 vmkernel: gen 664