How to clean up all of those $NtUninstallKB folders. (OT)
in [Freeware]
|
From: John Corliss on 30 Mar 2007 10:16 Fuzzy Logic wrote: > Adam Piggott wrote: >> John Corliss wrote: >> <snip> >>> >>> This backs up what you're saying. I will leave the $hf_mig$ folder >>> alone. >> >> I always compress $hf_mig$ (via Properties->Advanced). This does no harm >> and frees up disk space. Whilst you're at it do the same for "Installer" >> (super hidden), "ie7", "SoftwareDistribution", "ServicePackFiles" and >> "repair" in WINDOWS. >> >> I also delete the contents of SoftwareDistribution\Download. If you're >> really hurting for space, compressing Microsoft.NET can save a few tens >> of MB. >> >> Back on the original topic, I move the $Nt* files onto a backup volume >> and zip them up. If the machine doesn't have zip then I use NTFS >> compression. >> >> Once I had to uninstall a patch after quite a long time until an update >> to it came along, so /never/ delete them. > > My strategy is that if I need to uninstall I can reinstall and then uninstall. Might be a good idea to download and archive the update installation files to disc though. You never know when Microsoft will pull the rug out from under a version. These are all good considerations when trying to decide whether or not to use freeware to clean up this update clutter, but aren't really discussion of such freeware itself. Thus, I have marked this post OT. -- John Corliss BS206. I don't reply to trolls like Andy Mabbett and proteanthread, and am using nfilter to block out all Google Groups posts. No ad, cd, commercial, cripple, demo, nag, share, spy, time-limited, trial or web wares or warez for me, please. |