Things will get interesting for the system. Come back when you've found something that might take up a dollar of disk space. You're better using the actual supported tool for removing uninstall info rather than yanking it out from underneath the system. Sometimes an update needs to be rolled back before another can be installed. Guess how that happens? Setup files for Windows Update. Since they don't take up any space worth mentioning and WU removes ones it's done with, I wouldn't bother.
There's a few more kilobytes of temp files you could go for without trying to destroy IE. Honestly, what's the fascination with miniscule amounts of disk?
I guess it's just the Java Runtime installation kit and can be deleted If you never intend to update or remove it, sure.
If you never intend to update or remove it. Which one is that tool? I understand the whole point in not deleting the files as disk space is really cheap this days. However, before making a clone of the partition with clonezilla, norton ghost, etc it can be good to delete the unnecessary things.
Instead of a 6 GB image file you can get a 3 GB one. Shouldn't be running is a bit strong language to use, don't you think. I mean until the OS is supported by MS etc There is another reason a person might want to clean those files up: people who have working computers with no need to replace them, except they're running a little short on space. Why not clean up the extra stuff if it won't hurt anything? Drive space is cheap, but not buying more drive space is even cheaper. These files are used to provide a reference in case you're offline and want to uninstall an update.
They're also, more well known, used to store downloaded updates to if you have AU set to "download but then ask". I'm not sure what that margin is in something as old as XP. They are "safe" to delete, but you're moving into unsupported territory by doing so.
Linwood wrote: There is another reason a person might want to clean those files up: people who have working computers with no need to replace them, except they're running a little short on space. Clearing out user crap will give more space than clearing out a few hundred megabytes. Compress parts of the disk, NTFS compression is so fast that it can cause an increase in performance.
Hat Monster wrote: Setup files for Windows Update. WU is absolutely failtastic about removing these when it's done. Those folders are probably the only ones I delete, though, and only because they truly are useless, and offend my OCD sensibilities sitting in the root of whichever of my drives happens to have the most free space. You know what helps keeps an older system running longer and better? A newer hard drive that isn't crammed to the brim with crap.
And that's retail price. And that's being generous It just blows my mind that Windows thinks its okay to write anything , even temporary files not that they get around to deleting it to something other than my own Temp folder, let alone to another disk they don't know anything about or have permission to write to. Maybe I'm working on it and I'm about to format it or delete the partition.
Do your mess there. Quote: It just blows my mind that Windows thinks its okay to write anything, even temporary files not that they get around to deleting it to something other than my own Temp folder, let alone to another disk they don't know anything about or have permission to write to. WU has permission to write wherever it damn well pleases. Jim Z wrote: updates are a privileged operation, no?
I'm not talking about security here, just common sense. Windows doesn't own my computer and everything connected to it - it just thinks it does. I should have kept reading until I got to Brodie. The point stands, this is ri-cock-u-lous and a waste of energy and time. Linwood wrote:. Not having a computer is even cheaper still. Stepping over dollars to pick up nickels and dimes does not make sense. Just how much is time and aggravation worth? It's cheaper not to have a car.
DavlinLotze wrote: It just blows my mind that Windows thinks its okay to write anything, even temporary files not that they get around to deleting it to something other than my own Temp folder, let alone to another disk they don't know anything about or have permission to write to.
I've also seen behavior where updates will repeatedly fail to install because the download got corrupted and Windows Update refuses to redownload. I don't know how that space is managed but if I had to use one word to describe it, "badly" comes to mind.
Hat Monster wrote: Then you don't pay much attention to Windows Update. How often does this happen in practice, with hotfixes delivered through Automatic Update?
The only example I can think of off the top of my head is having to remove Windows Desktop Search version 3 before installing version 4. I generally go for zipping the hotfix uninstall folders up and moving them somewhere else if space is at a premium on the system drive, or someone's got some OCD about hidden files and wasted space.
For most hotfixes, a newer one will completely supercede a previous one. Hat Monster wrote: Clearing out user crap will give more space than clearing out a few hundred megabytes. No disagreement there. Use Task Scheduler to run on system startup before anyone logs in. Slipstreaming SP3 onto your XP disc would have prevented that space from being used. If you're doing a fresh installation, there no reason to be installing SP3 after the fact.
That's the crux of the whole "storage space is ridiculously cheap" argument. If a few hundred MB of extra crap is causing problems, then the hard drive is probably too small, too old, or both. Too little free space and and old drive can both negatively affect performance, and can both be remedied by getting a newer, bigger drive. It also probably only has 2 MB of cache. With storage so cheap, it's just silly to not upgrade if you're running low on space, even if and maybe especially if you have an older system.
Unfortunately, this directory can take up a lot of space. Greg Shultz explains how to free it up safely. If you've installed Windows XP Service Pack 2 on top of an existing Windows XP installation and are satisfied with the way your system is behaving, you may want to consider removing the SP2 Uninstall files—especially if you want to keep your hard disk free from unnecessary clutter. In fact, while you're at it you might also want to think about clearing out the Uninstall files for all the Hotfixes you installed before you installed SP2.
The SP2 installation procedure leaves the prior Hotfix Uninstall files in place in case you want to uninstall SP2 and then uninstall a particular Hotfix. You can also remove any Hotfix Uninstall files for Hotfixes that you've installed after SP2 if you're satisfied with the way they work.
This article is from TechProGuild , TechRepublic's premium online brand dedicated to providing network administrators and support professionals with proven, real-world solutions to today's toughest IT problems. TechProGuild members have access to this and other solutions-oriented original technical content, as well as over IT-related books, monthly PDF newsletters, and free featured downloads from the TechRepublic Catalog.
Discover additional articles like this and more by becoming a TechProGuild member. Sign up for a 7-day free trial and join TechProGuild today! Even though the goal here is to remove the Uninstall files because you no longer feel that you need them and would prefer to have the extra hard disk space available for data and applications, you should make backup copies of the SP2 and other Hotfix Uninstall files. That way, should you ever decide to uninstall the files, you can restore the Uninstall files and then uninstall them.
In this article I'll walk you through the entire procedure for backing up and removing SP2 and other Hotfix Uninstall files. Several folks with whom I've discussed this technique with mistakenly assumed that if you removed the SP2 Uninstall files, you would run into problems with Windows File Protection, which would no longer be able to do its job.
However, that's not the case. This folder is then used by Windows File Protection in the event that a crucial system file needs to be replaced. As such you'll need to be sure that you've enabled the Show Hidden Files and Folders option on the View tab of the Folder Options dialog box.
At this point, you can investigate the folders and determine which ones you want to backup and then remove. You can use command-line options to specify that Cleanmgr. You can then schedule the task to run at a specific time by using the Scheduled Tasks tool. To start the Disk Cleanup tool, either run the Cleanmgr. Disk Cleanup supports the following command-line options:.
The n value, which is stored in the registry, allows you to specify tasks for Disk Cleanup to run. The n value can be any integer value from 0 to All drives on the computer are enumerated and the selected profile runs against each drive. Temporary Setup Files - These are files that were created by a Setup program that is no longer running. Downloaded Program Files - Downloaded program files are ActiveX controls and Java programs that are downloaded automatically from the Internet when you view certain pages.
These files are temporarily stored in the Downloaded Program Files folder on the hard disk. This option includes a View Files button so that you can see the files before Disk Cleanup removes them. Disk Cleanup removes these page but leaves your personalized settings for Web pages intact.
IE5 folder. Old Chkdsk Files - When Chkdsk checks a disk for errors, Chkdsk might save lost file fragments as files in the root folder on the disk. These files are unnecessary. Recycle Bin - The Recycle Bin contains files that you have deleted from the computer. These files are not permanently removed until you empty the Recycle Bin. This option includes a View Files button that opens the Recycle Bin.
Temporary Files - Programs sometimes store temporary information in a Temp folder. Before a program quits, the program usually deletes this information.
0コメント