We build and test our software based on the existence of specific files and directories. You can find out by clicking Help. Let me know if you have any other questions. It's free and also has the ability to cleanup windows update uninstall files along with other crap. That's 14 hours to get updates done. If these are updates, that have been applied or need to be referred to, why is it this folder has more information in it than everything else on my system drive!!! I can't seem to get it to do anything.
If you don't trust the app to do the right thing, use the move feature to put them somewhere safe in case you need them back in the future. Good and bad work could be determined at a glance. Slow, uses too much space in this folder and often causes failures. I am currently following part of this article. I suppose the only field i've missed in the above list is something for subordinate updates for want of a better term. So the general idea is to advise on what the minimum set of recommended updates are to have installed before making a master image, or installing any apps, or connecting to Windows Update for the first time, or adding to a production environment.
Is there some tools that would clean up that folder a little? Drive Z is on a different partition. I appreciate all the suggestions and will probably utilize most of them. If the file to be applied is greater, thats all that matters. Otherwise installers would not be able to access the directory and report an error 1632. If newer software could be run with win 98 I would go back to it. Don't be so modest, you ran a marathon! If you're going to ask a question the least you can do is figure out how to figure out what version of Windows you're running.
If an application asks where to install, it should be confined in that directory only! But that is probably to ignore what you said about ignoring dates and only going on version numbers. I spent a few hours tonight searching on Google with not a lot of luck but with suggestions to use msiinv. Microsoft recommends not touching this WinSxS folder for the purpose of gaining more disk space. Have you gone to the other links I provided, and done some simple cleanup of the system, such as. Check Desktop Experience from the list, click Add Required Features if another window pops up, go to Next, and Install.
Nikolai Hi, I have a situation with the Windows Installer file. Running msizap from here was like magic. Or you did critical changes in W8 that were necessary to implement this functionality? I see a lot of people have had success with this program. My Installer folder is now982 Mb instead of 72 Gb!!!!!! And then check which folder has been updated. Try picking one let's call it xxyyzz. Removing items from here could cause you to have application crashes, or worse, require the reinstallation and patching of the application. Anyone still having this problem should do a search for the msizap tool.
Hey Tim, Glad you found my post. Still have a very large windows folder : I've been in similar situations. When running this, the installer and patch packages are enumerated and unreferenced packages are considered to be safe to delete and are thereby also deleted. It's a space hog, however, taking up several gigabytes of space and growing with each Windows Update you perform. Make a note so that it can be deleted.
Regardless, if version numbers are what should be referred to in determining update applicability, that might be making the case for including something like the filever command, inbox. The downside to this is that you will need to reboot your server after installing this and it installs other components you do not need on a server. Unfortunately, I don't know a ton about the Installer directory as its not part of the overall servicing architecture ie. If you remove files from this directory and have issues, you may need to reinstall the application to get back to a good state. You could install entire service packs in 10-15 minutes and dozens of chained updates in less than 5 minutes. Windows update with reboots also ran successfully after making the above changes. All of you reading this didn't have this issue so what was different? Those files need to be there in order for your system to work as intended.
I may have worded it ambiguously. It isn't just Windows Server Enterprise Edition. Additionally, many of the core files, such as kernel, do have multiple updates to them so it wouldn't surprise me that you have 15 versions of a file with the name ntoskrnl. I have quite a few other servers with the same size root drive and do much heavier lifting than this server with plenty of space available still. Or it checks every time the whole WinSxS and if something doesn't match — it stops? I knew there had to be a way to deal with this, and indeed there was. The 'ver' command is not outputting anything that a single envar couldn't.
So there may be situations where the administrator has to delete files manually. It's going to take a while because of the 36. The appropriate executable should be renamed MsiZap. When it comes to backup, I believe you can never have too many, nor keep them in too many places. I generally clean up any folders older than a month, the logic being that if the patch has been installed for a month with no issues, there's pretty much no chance I'll be needing to uninstall it, which is the only reason you would need these files. Thanks again to one and all. Nuking and reinstalling isn't always practical and is way, way too drastic to be the go-to response to a Windows folder growing out of control.