What is wrong with my junction.exe command?

Question

I am trying to create a junction point on windows 8 so that files will be written on my HDD (D:) instead of my SSD (C:).

A few of the commands I've tried

D:\Downloads\Junction\junction.exe D:\Temp\Glasswire\service C:\ProgramData\GlassWire\service
D:\Downloads\Junction\junction.exe D:\Temp\Chrome\LocalStorage "C:\Users\Garvin\AppData\Local\Google\Chrome\User Data\Default\Local Storage"

The end result is that files are written to both the junction point directory and the destination directory. My understanding of junction points was that new files would only be written to the junction point directory, but are junction points actually just backup directories or am I doing something wrong here?

(Also I am using Windows 8)

EDIT: From what I see in task manager/Performance only my SSD shoots up in activity when dragging files to C:\Users\Garvin\AppData\Local\Google\Chrome\User Data\Default\Local Storage while the HDD stays at 0%. (I am dragging a 550mb video and 700mb exe from a USB)

I was attempting to reduce the number of writes the SSD performs to increase its lifespan but junction points do not seem to be the way to go, contrary to what is written here http://lifehacker.com/5802838/how-to-maximize-the-life-of-your-ssd

Answer 1

I've always used the built-in mklink /j command to create directory junctions in Windows. It seems to work fine -- just like a soft link in Linux.

Hese's some info from TechNet here: http://technet.microsoft.com/en-us/library/cc753194.aspx