There are three solutions.. So to delete folder1. This works fine. As the title implies, this is another solution… but the more folders you have, the slower it gets. Next are the steps:. You now have permission on all the folders in the folder on which you clicked to view properties. But if you have many folders, it will take a long time… if so check solution 3. This solution is very fast but is a bit technical as well… cause you need to use the command prompt cmd to use this solution.
When a Windows Vista update. MSU is installed, the components get updated, each and every one, instead of the files and the worst part is it still maintains the older superseded previous versions of components in WinSxS so the user would be able to uninstall updates. Microsoft does say that some sort of "scavenging" or deleting older copies of components takes place but is scarce on the details.
The scavenging seems to take place automatically at certain intervals in Windows 7 but not in Windows Vista. In Windows Vista, you have to add or remove any Windows component for the scavenging to take place. And Microsoft says the scavenging will free up some disk space but in practice, on my system, I see my free disk space only decreasing on Vista as I remove or add any component.
As as you install more and more updates on your system, they will take more and more disk space. This is one of the primary reasons Windows Vista and Windows 7 are so bloated. Another reason for them being so bloated is the DriverStore that these OSes store.
But let's not go there for now. Now, an important thing to note is that the size of the WinSxS folder is not what Explorer or the dir command report, it is far less but is misreported by Explorer because it counts the hard links more than once when calculating size. Microsoft's ingenious recommendation to this problem of ever growing disk consumption is to install fewer updates to keep the size of the servicing store under control.
Of course, users cannot deny installing security updates and leave their system open to security holes. What they can do is install less optional updates, the ones that Microsoft releases on the fourth Tuesday of every month and also install less of the hotfixes that are available by request from a Knowledge Base article.
In short, you have to trade the number of bugs fixed in the OS by installing hotfixes at the cost of enormous amounts of disk space. The whole servicing stack is a total downgrade to Windows XP's update. Many systems are unable to boot because of failed updates. Another disadvantage of the "new" servicing stack and the redesigned Setup mechanism of Windows Vista is the inability to do a true slipstream of service packs and hotfixes.
The time it takes to actually install these hotfixes online compared to Windows XP is also completely unacceptable. When you start installing an MSU update, it spends a lot of time determining whether the update applies to your system.
Then, the update itself takes much longer to install compared to Windows XP's Update. Finally, that post-installation process "Configuring updates Do not turn off your computer" takes several minutes before shut down followed by a second post-installation process configuration upon restart before logon that also takes also several minutes and thrashes the disk. I can install the entire SP3 for Windows XP in about 10 minutes after downloading the full installer.
In contrast, Windows Vista or Windows 7 do install relatively quickly in just about minutes on a modern PC but installing the service packs and updates takes more time than anything on XP did. Not only can service packs not be slipstreamed, but Vista Service Packs are not even cumulative, which means if you clean install Windows Vista today, you have to install SP1 first which takes about 90 minutes, then SP2 which takes less time, then all the post-SP2 updates which do take hours to install.
If you really HAVE to use Windows 7 or Windows Vista, you are stuck with this slow update non-sense as Microsoft does not even acknowledge that there is any slowdown or loss of functionality in the new servicing mechanism. Is is worth wasting your time on an OS whose servicing mechanism Microsoft completely screwed up? Microsoft's Windows Vista and Windows 7 products are not engineered with disk space in mind. It causes a problem, especially for SSDs which are still low capacity and very expensive.
The only hope is that Microsoft again completely redesigns this servicing mechanism in a future Windows release so it would not cause this growing disk space consumption issue, speed up installation of updates by an order of magnitude, not slow down logon and logoff, not prevent systems becoming unusable because of failed updates being stuck at a particular stage and allow true slipstreaming.
Microsoft's response to this is vague - they simply state "Windows 7's servicing is more reliable than Windows XP" but they cannot acknowledge it is a million times slower and still unreliable Of course they know all this too but can't admit it since it makes their latest OSes look poor. Take a look at servicing-related complaints in Microsoft's own forums: 1.
Very slow install of updates to Windows 7 2. Windows 7 - Updates are very slow 3. Windows 7 Ultimate, it takes long time configuring updates 4. Very slow update install at shutdown Windows 7 Home Premium 6. Why does my computer run so slow when installing updates? Every time the computer is shut down, it always says installing update do not turn off your computer 8. Computer is working slow and wants to do windows updates all the time 9.
Windows 7 Update install time taking a very long time Windows wants to install 6 updates every time I log off or put the computer in sleep mode Computer really slow after latest updates Windows hangs up in "configuring updates" Why can't windows 7 install updates? Every time computer is shut down, receive Installing updates, do not shut off How long does it take for the Windows 7 Home Premium updates take? Windows 7 "Installing Update 2 of 2" for 12 hours now Updates causes endless reboots Updates stuck installing for over 24 hrs.
Computer does not boot Cannot load Windows 7 after installing 2 critical updates. A proper solution to this problem would be to completely re-engineer and rewrite the servicing mechanism so it operates with the speed, reliability and pain-free operation of the XP servicing mechanism.
I don't see this situation improving in Windows 8 either. Good luck with your Windows tablet taking hours to install service packs and updates. Now, do iPads take that long to install updates? System requirements at install time may be 15 GB of free disk space but over time, this number increases to alarming levels as you install more service packs and post SP-updates. You can find out the real size of the WinSxS folder using a tool like cttruesize ctts.
The most helpful command EVER found on reducing the whooping bloat size of winsxs 2 years of operation on a Windows 7 x64 system blew it up to 21 GB!!! Running the command reduced the size of WinsXs to 7. Everything else proposed is worthless compared to this. This folder size has nearly stalled me from using my fast SSD to install programs on it because i always had to worry about future reserve space. MS shouldnt divert from the design flaw of the OS bloating itself to unnatural sizes by quoting low storage capacity prices useless point for a folder you cannot relocate to a cheap storage HD instead approach a easy to use and safe solution to users who are not tech savy to reduce the size of this folder without jeopardizing.
Because the only remaining safe solution would be a complete reinstall of the Operating system After long readings without any real answer I've decided to take a different approach.
Let's post files found in the WinSxS directory that are safe to delete. Here's a list of files to start with: for example, Sleep Away.
Solution: take ownership and delete the bastards. Hard Link or not, you can't argue with actual results. I know 16Mb is not anything to brag about, but it's the first real bite from WinSxS other than the SP1 cleanup command.
It is my hope that with enough responses to this, we'll have something that can make an actual difference. I hope others will identify more files, or better yet folders, that are full of fluff like this that can be safely deleted. MS fixed it in Windows 8. Office Office Exchange Server. Not an IT pro?
Windows Client. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Windows 7 Miscellaneous. Use this forum to discuss miscellaneous issues that cannot be covered in any other Windows 7 forum.
Sign in to vote. Of course, what happened was that the old Windows files were transferred to Windows. However, the WinSxS folder of the original installation remained, and lives on at eight gigabytes. I can rename the folder, but not delete it.
I have tried to use MoveFile to delete it on bootup, and I'm this close to installing a tiny Linux distributable just to try and delete the folder. How do I delete this useless, space-eating folder? Friday, May 29, PM. Friday, March 25, PM. Unfortunately, I now get a prompt that says I need permission from myself.
Flatterland, As an alternative to a Linux live CD - many of which will not let you around the file permissions of Windows Vista and Windows 7, I'd recommend VistaPE - but only on the grounds that you know exactly what you're doing! Never mind, I solved the problem. Just had to check the boxes for child permissions in inherited permissions. Looks like the settings weren't going deep into all the files. I'mma take a look into it.
Thanks again :D. Is it contained in the Windows. Let us know. The Windows. Weird why Microsoft put the bulk, if not all, of the entire operating system in the WinSxS folder. That must make all of the other directories only shortcut folders, more or less. I spent a considerable amount of time, last year, researching this subject. There are hundreds of websites that attempt to explain the WinSxS folder and what it does, unfortunately most of those articles are full of misinformation, misunderstandings, and plain speculation.
To understand the WinSxS folder, what it is, how it works, and how you can be fooled by it's perceived size, you need to understand several different concepts. Hard Links, Componentization, and Servicing. Here are 3 links to fairly short articles, written by the people who designed and maintain that component. No FUD, just facts. Saturday, May 30, AM. Oh, I understand now! That's why I gained barely a gigabyte when I finally deleted the purportedly eight-gigabyte SxS folder; in reality, it's just a comparatively small number of files with a lot of hard links spread out across the system.
Hard links have been around since XP, though. I wonder why the technet blog link says that they were "long-awaited" andjust "introduced in Win Vista. Hi I think the blog article was referring to the fact that Windows Vista is where Hard Links were first used extensively throughout the system.
Many developers had been pushing Microsoft to make better use of hard links for years. One thing is for sure. But, when it gets to the WinSxS folder at approx. And that the other directories, including the Windows Parent directory of WinSxS is more or less just short cuts, or Hard-links, or whatever they're called. Sunday, May 31, PM. Hi David Correct! Now you have a good understanding about how it works. Can I have a cookie?
Monday, June 1, AM. So, in other words No, in that case, you're deleting the actual files. By marking a post as Answered, or Helpful you help others find the answer faster. I'm talkin' bout all the files that Microsoft stuck in them during the installation.
There must be close to a gig's worth of. I got's all the one's that I don't want or need OUT. Wasn't too concered with the bit version of Windows 7. I was with the bit version. Hi David Actually Chris is correct. Monday, June 1, PM. If this is so, why was this feature not incorporated into explorer directly instead of having it behave incorrectly?
That I have "minus 4 Gb" of space left? It really sounds ridiculous, and excuse me but it's evidently a real sloppy work from MS people I mean, we're not talking about some third party app not showing what you really have, but the OS's own stuff not working correctly Tuesday, June 9, PM.
The question raven poses is the one I have had for a long time. I'm assuming that most installers are going to use the same API's that windows is using and tell me I don't have enough free space. Currently windows explorer in the VM shows I will keep an eye on this over time to see how much it grows. The Ask the Core Team article linked above seems to be the most honest explanation I've read so far. That's were I'm running into the biggest problem.
We are running into serious issues with reguards to how much space the WinSxS folder takes up, with no added value to our business. I'm considering using something like VistaLite, which I've used to shrink down Win7 to fit on my netbook in our production environment with the added risk just to save some space.
In summary, please consider the following: 1. Fix the windows APIs, and Windows Explorer in regards to calculating disk space to take into account hard links 2. Since everything is componentized, give us an advanced install option to not install stuff we don't need. I don't need the same experiance on my servers that the average user needs on thier deskop PC. I know how to install a driver!
Continue to offer the service pack cleanup tools, and consider extending this option to allow us to "commit" changes as we see fit. For example if I roll out patches in month 1, and everything goes OK, i'd like to commit those patches in Month 2 before I roll out patches for Month 2. Thursday, June 25, PM. Can someone please follow up on this question? You can say that hard links don't take up any space all you want, but all the OS tools think that the hard links really are taking up space.
So while they may not be taking up 1s and 0s on the magnetic plates of the hard drive, they are still taking up free space from my system. They prevent me from installing apps which are using the same OS tools to calculate free space. You may as well have physically copied each file, in the end there is no difference to me. Sunday, August 2, AM. Wednesday, September 23, AM. Hi ymhing The compcln. It's designed to immediately remove all of the old files in the WinSxS folder that are replaced by the SP2 update.
It does not exist and cannot be used on a Windows 7 system. Also, the link to the maintenance troubleshooters that you posted are for Windows Vista. Windows 7 has all of these tools built-in. Do not select "Restart" at this point, but choose "Exit Without Restart" instead. BIN Boot folder Boot. On restart, place a check in the System dialogue box that pops up.
Note: This method, while easy to use and effective, has its shortcomings. It does not carry out a full cleanup of your system and leaves traces of the Windows Vista installation on your Windows XP system drive. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question 2. Report abuse. Details required :. Cancel Submit. Irfan H.
0コメント