Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an SSD as my C:\ drive, and it's only 128 Gig.

I'm noticing that the C:\Windows subfolders "winsxs" and "Installer"--both of which I've read numerous places that one should never delete unless they want a nightmare--are taking the biggest chunk of space.

So, can I create a Junction using the mklink command after moving the data to one of my spindle drives with more space? Thanks, --Jim

share|improve this question
I keep reading that this can't be done because those are "already" symlinks. – cloneman Mar 20 '13 at 4:25
up vote 1 down vote accepted

You can do this for Installer. You can use this tool:

enter image description here

JunctionMaster is a small and simple shell extension that will allow you to MOVE and LINK a folder in one easy step. It focuses on MOVING the folder, then replacing the original folder with a hard link (junction) to the new location. Windows (and the user) can reference the files at the same location as before, but the actual storage of them is on the other drive. It is handy for new hard drives, and also in the case of SSDs where you may wish to redirect some folders with lots of RW activity to a conventional HDD.

For instance, if you bought a new hard drive you might wish to move some large folders without having to change their paths? For instance, having it store the stuff in c:\movies, but not having the path of c:\movies change. This is what JunctionMaster will do. It would move the files to f:\movies, but c:\movies still accesses them just the same (with no perceptible difference at all in the shell until Windows 7, where it now shows a link overlay on the folder icon). You must be CAREFUL though as deleting the files from either location will delete them in both (since only one real copy exists).

share|improve this answer
Thanks very much. I didn't use that particular tool, but I used the native mklink and did it to the Installer folder. I haven't tried winsxs yet, but from what I understand winsxs probably would benefit my system more from being on the SSD drive, so I'll keep it there. I freed up more space by moving a bunch of larger program's help files and some other huge but rarely-used files. I now have 40 Gig free and no longer feel the need to get a 256 Gig ssd, so it saved me some cash. – James Mar 20 '13 at 23:54
@James could you please tell the exact command you used for the symlink ? (put it into the edit of your question if you like). – Boppity Bop Oct 29 '14 at 16:19
Take a look at this question:… – JBE Feb 12 '15 at 19:23

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.