Tried symlink/mklink - now riddled with "Access is denied" - solved

destrekor

Lifer
Nov 18, 2005
28,799
359
126
So... this has been yet another fun lesson in the "You aren't as gifted in Windows as you think you are" series.

[quick background: my only user account is an admin-level account]

What got me here:

move the "steamapps" folder off my C drive (SSD), and onto my D drive (HDD).
create symlink using "mklink /j "c:\program files (x86)\steam\steamapps" "d:\steamapps"
(original steamapps directory in the steam folder was no longer there at that point)
When I tried that, I got "access is denied" - but the "folder" was created in the original steam directory
Figuring this was failed, I tried deleting the directory. "Access is denied" ... Well shoot.

After some digging around, I've done a few things:
entered an elevated command prompt, tried removing directory - still same error
For the hell of it, tried running the mklink command again - no go, still denied
I also went into the security policies and specifically named my user account (though it should be grouped under Administrators) to have the permission/ability to create symbolic links. I logged off and back on, and repeated these steps. Nothing.

I go into the steam folder, and look into the Permissions. Well, the steamapps folder in particular shows me "Unable to display current owner" - and I've tried everything I know to take ownership. I cannot even display any page to change specific permissions until I take ownership, apparently, but I cannot do it. I cannot change the entire "Steam" folder's permissions and force child-inherit, at least, it spits an error stating something about steamapps (I clicked off quickly, as I was expecting that anyhow).

Suggestions?

At any rate, I'm also curious if what I am intending will even work in the end. I have and want to keep Steam itself installed on my SSD, but want to have the entire steamapps folder (all game data) on my HDD (must be done through symlinks - steam itself is retarded). But after I accomplish that, I do want to move a few specific games back onto my SSD.
I'm assuming I can't just put them back into the steamapps directory on the SSD (since that's a symlink); now that I'm thinking about it, this should work: I just move those specific folders into a new directory on the SSD, then create symlinks in the steamapps directory that's located on the HDD.

Of course, that's assuming I can get this little issue fixed - it's quite troublesome.
 
Last edited:

Rhonda the Sly

Senior member
Nov 22, 2007
818
4
76
I don't have time to go through you problem with deleting the link but I do that with mklink /d.

Hope it helps once everything is fixed up.
 

destrekor

Lifer
Nov 18, 2005
28,799
359
126
It seams for this instance, at least according to everyone doing this for steam, a directory junction (/j) is what must be created.

edit:

I thought I tried last night after also rebooting, but turns out I had not - or had typed something wrong.

(keep in mind, I updated my security policies)

I just opened an elevated command prompt, tried rmdir for that steamapps folder, but oddly enough, said director did not exist. I checked in explorer - yep, no such directory. It mysteriously vanished. Oh well, works for me.

So then I tried mklink /j all over again, and this time got "Junction created for ..."
awesome

Not sure if these ownership issues still exist, I don't even want to look. So far things look good, going to load up steam to see if everything appears intact.

Just shed about 150gb from my SSD. Definitely happy. I will be moving some of the games back, so I won't end up gaining all that space, but definitely happy to finally get this done. Been thinking about it forever, and seeing only 10gb left on my 256gb SSD definitely bothered me. Even with TRIM and stuff, that's just asking for some trouble in the future. Next up - I really should think about moving my Users directory to my HDD (two HDDs in Intel RAID array - one volume Raid0 for application storage space, one volume Raid1 for documents and downloads). It's not massive, but with temp files and documents not really needing SSD speed, all that folder is doing is eating up read/write cycles (up until this point, on a nearly full SSD).


In the end, I guess this issue is resolved - by magic*, no less. :D

*potentially simply a reboot or two. or magic.
 
Last edited: