Most Active Hubs Microsoft Teams. Security, Compliance and Identity. Microsoft Edge Insider. Azure Databases. Autonomous Systems. Education Sector. Microsoft Localization. Microsoft PnP. Healthcare and Life Sciences. Internet of Things IoT. Enabling Remote Work. Small and Medium Business. Humans of IT. Green Tech. MVP Award Program. Video Hub Azure. Microsoft Business. Microsoft Enterprise. Browse All Community Hubs. Turn on suggestions.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Show only Search instead for. Did you mean:. We can delete the files in the folder, But, they will be needed when trying to uninstall some programs which installed with Windows Installer.
So after delete these files, we will need to reinstall or repair a related program if they cannot be uninstalled with error "requires the previous installation to be uninstalled". However, instead of deleting the Windows Installer folder, I'd have you delete them by using disk cleanup.
Also, reduce the space for System Restore. Refer: How much disk space does System Restore require? Warning: If you decrease the disk space to be smaller than the space that is currently being used by system protection, older restore points, including previous versions of files, will be deleted.
How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. The same links for Vista apply to Windows 7. MS didn't change the usage! Not a very helpful answer. Some of us prefer to buy SSD drives which in case you haven't heard offer a massive performance increase over traditional platter based storage. In this case, trimming the winsxs folder would be great way to optimize space.
I would also welcome info on how to trim up the winsxs folder. That is completely absurd. On my system WIN7 X64 this folder consumes 7. No extra languages or so. Winsxs doesn't really take up space. It's just hard links to other files. But windows can't tell you the right amount of space it takes up.
I take this back. I'm using cygwin ls and find. I wouldn't delete anything though. I am preparing to move my installation to an ssd and find windows reports 22gb of space used after moving my documents etc to a traditional sata drive.
You can't tell the size of winsxs, but the free space on c: is reported correctly. For example if you have a big crash dump and make a hard link to it, the reported free space on c: remains the same. I ran that tool that the 'answer' provided. The majority of the files in the winsxs folder resides in 'backup', as the name implies i'm suspecting this is for meant for backing up old versions of files, e. So, is there anyone out there that has a working solution?
I'd just remove the backup folder, but i don't want to spend time unnecessarily in linux live distros to fix it again, aside for the fact that many less tech-savy users wouldn't know how to do that at all. I'd be surprised if you'd get windows 7 working on an AT-based device in the first place.
If no real answer is provided in a few days from here, i'm just gonna try re move the backup folder, if that doesn't crash my system i'll report my findings here. After finding this folder and how much it contains, then finding this information. I'm offended that I no longer have the capacity to prune back things that the clepto OS keeps.
Without that control, I no longer have a system that I will be able to use and this puts those of us that support it in a very bad spot. I have another longer list of things I don't really like about how the OS has progressed, maybe it's lack of understanding, but I file it under "that's a sneaky maneuver. This is not a good design method. I did however find a post that explains what is going on and I don't like the answer.
After reading the article all I can say is wow, really. There has to be a better way, hope you find it. I still think that the HW reqs should plainly state that the size requirement will expand exponentially over time. Unless the shell can understand that Winsxs is truly on mb. The actual amount of storage consumed varies, but on a typical system it is about MB. While that is not small, we think the robustness provided for servicing is a reasonable tradeoff.
Since the only solution to this problem is to buy a bigger harddrive, well, I can't run windows anymore. I thought I would miss it, but I don't. I'll just run xp VM if i need windows for something, i guess. I feel like a total chump for buying ultimate, and I can't believe the infuriating responses from the representatives. I'm not going to cancel my xboxlive subscription but I'll never buy another windows OS again.
I really wanted it to work out for us, microsoft, but it's not me, it's you. Had to find it via Google, as MS doesn't seem to promote this way. Dunno why This only appears to work if you upgraded to Windows 7 SP1. A clean install of Windows 7 SP1 in my case Enterprise bit you get the following,. Microsoft Windows [Version 6. All rights reserved. Deployment Image Servicing and Management tool Version: 6. The operation completed successfully.
Thank you zeroFX!!!! I have Windows 7 Ult. After running that command, it saved me almost 4gb on my OCZ 60gb ssd and 3. I've done this on a couple of SP1 machines that have worked fine for months and regained some 4Gb of space each time. My daughter's laptop started life on XP and has been running Vista since it first came out and has all the updates applied. Her C drive 39GB is now showing 2.
The machine is still usable with difficulty, fortunately all the data was on a separate partition and has been removed. I am now left with the WinSxS showing I have read everything I can find on this subject and am seriously considering deleting this blobs.
My daughter has already bought a new machine so if I kill this old one it really doesn't matter too much as I will wipe everything and install Linux for use as a web browser. This is truly sad, i myself have had the same problems on my ssd, but now I am having an issue at work.
I was recently tasked with deploying windows 7 in the workplace. I went to reading all of the various tools they offer and built my first image. It was Windows 7 Pro. After running imagex on it my wim file was around 3. Well after talking we decided to use enterprise since we have license to it and it offers more features. Did the same exact setup on it, installed the same applications. Now running imagex results in a 16GB wim file.
This just doesn't work Many thanks to ZeroFX and all other. Just ran the mism command following instructions in the link below. I really feel left out in the cold by Microsoft and am seriously considering to start using a different OS. No matter how much space in reality is left on my C:-drive, if the OS does not see it, what effing good does it do?
The WinSXS folder may contain hard links, but what a hard link means is that when the file it's linked to no longer exists, WinSXS is using up that space, because a file is not removed from disk until all hard links to it are removed too! So the real question is: How do we clean out hard links to old versions of files that no longer exist, that are no longer needed by any installed applications?
Download the Disk Usage tool from the sysinternals site? Updates installed in very little time. If you wanted to further reduce update times on Windows XP, you could just temporarily stop the System Restore service and updates would install at crazy speeds. Note that this is not recommended for novice users who don't know advanced recovery methods, as some updates can sometimes cause your system to stop booting so you cannot even uninstall them.
For files that were in use, a restart copied them from dllcache to the system32 folder. This is simple file-based servicing. The hotfix installer Update. Again, this is not recommended for novice users as some updates can screw your system even after the comprehensive testing Microsoft does before releasing them.
But if you won't be uninstalling any updates usually one only requires uninstalling updates if they cause problems , you could save a ton of disk space by not backing up the files it patched. When Microsoft was developing Windows Vista, they realized that components had gotten too many interdepencies on each other and to service each file reliably without breaking another component that relied on it, Microsoft introduced what they called as Component Based Servicing CBS.
You can read all about it in a much more technical way at The Servicing Guy's blog. This has the benefit of not having to insert the OS disc to add or remove any components, and some other advantages as well like offline servicing of a Windows Vista or Windows 7 image.
But the design introduces a major disadvantage of taking up a lot of hard disk space. Now, Windows keeps multiple copies of the same file but with different version in WinSxS if it is used by more than one Windows component. 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.
0コメント