Skip to main content

Reducing the winsxs folder - why it won't happen until Microsoft change Windows Updates

Recently I, along with thousands of other system administrators, have been swearing more than usual. If you're one of these people, you know why - the winsxs folder starts to use huge amounts of space on your hard disk. If you've gone by Microsoft recommended practice and created a 50GB C drive, then you also know how quickly this screws you.

Is there a way to reduce this folder? If you apply a Service Pack and go through the mechanism to apply it without chance of uninstalling it then you'll grab a little space back, but as you apply more updates, patches and new drivers the winsxs (or Windows side by side folder) will continue to grow. Theoretically it allows you to roll back if something goes wrong with some component of the operating system. In real life though, this isn't really done - we can just reinstall the busted component or whatever.

The system that controls the winsxs folder is tied to Windows Updates - and as we all know in Windows Vista, 7, 8, Server 2008, 2008R2 and 2012 Windows Updates can be hit and miss. Updates failing to apply, updates taking forever to apply or the ever annoying "Shutdown and install updates" that drags on forever. Vastly different to Windows XP of course.

Most often the fix is to replace the disk, or expand your hard disk size but this is frustrating and annoying. It's also expensive for our clients. Unfortunately it seems to be the best way to solve this issue - there is no short term fix or even any hint from Microsoft this will be solved.

I recommend that for new servers, a 100GB C drive is configured to give you breathing time until Microsoft finally manage to solve this issue. If you know better - hit the comments.

Comments

Popular posts from this blog

Windows 10 Enterprise Eval - gotchas

After an annoying turn of events where my Windows 10 Enterprise USB drive failed, attempts to install Win10 onto a computer failed miserably. I turned to the net and managed to get my hands on Microsoft's Windows 10 Enterprise Evaluation. I have an enterprise key so I thought - cool! Here's the opportunity to get it going and to then upgrade the license later. Full install, patched etc and all is swell. Except when I try to upgrade. I straight up tried changing the licence key only to get a variety of errors, most of which are pertaining to the activation system being unavailable. The I try this: https://winaero.com/blog/upgrade-windows-10-evaluation-to-full-version-easily/ but it doesn't work either. Next I'll try this: h ttp://www.edugeek.net/forums/windows-10/174594-upgrading-windows-10-enterprise-90-evaluation-full.html And if all else fails, in goes the bootable USB I've now created. If only I'd had this in the first instance I would not be writing t

Fixing a black screen after doing a Kali Linux update

Kali Linux is a rolling Linux distribution designed for security and penetration work. You can find details on it here: www.kali.org . We run this excellent product for a range of different security work and it's been great. I built the image in VMplayer, then shared it to the team and we've all been at it since. A recent update broke it though - black screen, no network and completely unresponsive. There are lots of posts about similar things - mostly to do with graphics adaptors, however, we found that executing the following at a root prompt fixed it. But how to get to the root prompt from a blank screen? Linux has a number of terminals available to the user - most of us use the graphical one to do our day to day, but you can access a command line prompt without much trouble. Simply hold CTRL-ALT and then F2 or F3 down at the same time and it drops you to a command line login. BOOM. Time to fix it up. For me, and for the other fellas in the team, all it too was to

Plone - the open source Content Management System - a review

One of my clients, a non-profit, has a lot of files on it's clients. They need a way to digitally store these files, securely and with availability for certain people. They also need these files to expire and be deleted after a given length of time - usually about 7 years. These were the parameters I was given to search for a Document Management System (DMS) or more commonly a Content Management System (CMS). There are quite a lot of them, but most are designed for front facing information delivery - that is, to write something, put it up for review, have it reviewed and then published. We do not want this data published ever - and some CMS's make that a bit tricky to manage. So at the end of the day, I looked into several CMS systems that looked like they could be useful. The first one to be reviewed was OpenKM ( www.openkm.com ). It looked OK, was open source which is preferable and seemed to have solid security and publishing options. Backing up the database and upgradin