I'm planning on installing an SSD/HDD combination with the SSD as my boot (Windows 7 x64) drive, and a spinning HDD as a storage drive.

  • Are there any log files in particular best suited to a mklink to the SSD?
  • Is it worthwhile to move/link the main user profile to the SSD?
  • How much space should I try to leave open on the SSD for best wear leveling?
  • What other directories/files would you consider mapping to the HDD?

I know that temporary directories, even the main profile may be good options here, I'm just wanting to know any obvious choices for space, or many-write situations.

  • I know I will relocate the music/videos directories as they get really big, but may do the user profile altogether for space considerations here.
    – Tracker1
    Jan 14, 2010 at 16:45
  • 3
    We've written a post about this on the Super User Blog, see Maximizing the lifetime of your SSD. May 12, 2011 at 16:38

4 Answers 4


In addition to Wil's answer, I put all BitTorrent downloads and most games onto an HDD, rather than an SSD. Although there is the potential for better performance with games on an SSD (such as reduced loading times), they tend to take up a lot of space. Also, if you don't need to use hibernation, you may wish to disable it to save space on the SSD.

Note that keeping some free space on the SSD is more to help the drive maintain performance over time, rather than to directly assist the wear levelling.

  • Yeah, I wound up installing gametap and steam to the HDD, then symlinking them to the HDD... did this for a few things... media files are on my NAS for the most part.
    – Tracker1
    Nov 22, 2010 at 17:31

I use an SSD alongside a HDD and install quite a bit more software than the SSD has space for. I'm answering anecdotally as I've been unable to find authoritative information for managing an ever growing Windows installation split between an SSD and a HHD

I manually manage a great deal of my installation and data. Every program that prompts for an installation path gets assigned to D:\Program Files or D:\Program Files (x86). Note that simply installing here without taking extra steps may create a security risk by bypassing the restrictions that Microsoft places on the C:\Program Files folders. I have not fully researched the implications of simply changing the installation path. I've also created a D:\Users\Chris\ folder and I take advantage of the Windows 7 Libraries feature to make manually setting save paths easier.

I use WinDirStat to find large files and folders on the SSD for selective junction creation to the HDD. Anything related to the Windows installation I research online, as I've seen suggestions that wholesale linking folders such as the Program Files directory or the \Windows\winsxs to a HDD will cause problems and instability.

Some of my junctioned folders are:

  • Large chunks of data in the \ProgramData\ folder
  • Adobe files (Common Files?)
  • \Windows\Installer\ files

Windows seems to manage log files well and I haven't seen any that balloon up into significant sizes.

I strongly suggest making backups before moving and linking folders.


It really depends on your usage.

If you do not have a lot of stuff, I would simply use the SSD and only the SSD.

I personally would not move your entire profile or junction it as there are settings that are written all the time, user registry and various items that you would want to keep on the SSD.

I would just create a few folders on your hard drive and keep movies, videos, archive, backup and music files on there. When you are using a hard drive just for data storage and nothing else, they are quite fast.

As for leaving space, Just never let it get full - I personally would want to keep at least 5GB free at any point (but that is just me)

As for log files, they will be created (usually) within the Windows directory so they will be on the SSD.


On my data HDD, i created a directory called JUNCTIONS. Here are the folders i junctioned.

  (Add Everyone full access or similar permission for windows updates to work)

I used this tool that made creating destination Junctions easy. Hard Link Shell Extension

If you are junction-ing users, do not create the destination users folder, just "create junction" from within the JUNCTIONS folder.

I also left Windows Indexing turned on as it writes to ProgramData

  • 4
    Please note that winsxs contains the biggest part of your OS, it shouldn't be junctioned if you want your OS to run stable and load quickly; C:\Windows\explorer.exe for example is just a hardlink to C:\Windows\WinSxS\amd64_microsoft-windows-explorer_31bf3856ad364e35_6.2.8102.0_none_3563787fbec6da7a\explorer.exe on my 64-bit Windows 8 system, but this works similar in Windows Vista and Windows 7 for both 32-bit and 64-bit versions. Oct 24, 2011 at 3:09

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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