Can't Use Old Steam Library On Previous Primary Drive?

[Niknokinater]

Just got an SSD and slapped Windows on it. I'd like Steam to run from it as well. I am permitted to add folders from other drives, but only if they are empty.

Why can't I simply add my filled games folder? This is silly really.

[Tev]

The lack of context makes it harder.

If it's the main Steam installation, just move it onto your new SSD? You can't make the main folder (with the libraryfolders.vdf) a secondary installation location.

If you need to keep Steam on that disk, then I'd just make a folder (empty one) from [Steam > Settings > Downloads > Steam Library Folders], exit Steam, and place the steamapps\ -folder and the appmanifest files on that.

[Niknokinater]

Originally posted by Teutep:

The lack of context makes it harder.

If it's the main Steam installation, just move it onto your new SSD? You can't make the main folder (with the libraryfolders.vdf) a secondary installation location.

I installed new Steam on new SSD.
I need to have games remain and function from old HDD from new Steam on new SSD. Steam appears to support this, but only if the new library folder is empty upon adding. I'd really rather not drag 228Gb one folder over.

[Tev]

Then I'd transform that ex-primary location into a secondary location.

I edited the above while you were responding.

[Niknokinater]

Originally posted by Teutep:

Then I'd transform that ex-primary location into a secondary location.

I edited the above while you were responding.

Ah yeah, I tried that. Assuming that you effectively mean rename Steam Steam0 and create new empty Steam folder, add empty Steam folder (so that the generated steamapps lines up imaginably), close Steam, paste any new files in HDD Steam0 directory, delete empty Steam folder, and rename Steam0 back to Steam... That just gives the 'Library destination must be writable' error because it's in Program Files (x86) and Read-Only cannot be disabled :(

[Tev]

So don't put it under Program Files (x86).

Although altering libraryfolders.vdf manually probably overrides that restriction anyway. I also wouldn't move EVERYTHING from the old folder. Just the steamapps\ -folder (which includes the appmanifest files).

[Niknokinater]

I'm about a year too late unfortunately

Originally posted by Teutep:

Although altering libraryfolders.vdf manually probably overrides that restriction anyway.

Mmmm

[Tev]

Originally posted by Niknokinater:

I'm about a year too late unfortunately

What?

You know you can just make an empty folder practically anywhere on the disk under [Steam > Settings > Downloads > Steam Library Folders], exit Steam and move the steamapps\ -folder within the new folder.

Just don't place the new folder under Program Files (x86).

Even right now I just use Steam under

C:\	C:\Games\Steam
D:\	D:\Games\SteamLibrary
E:\	E:\Games\SteamLibrary

[Niknokinater]

Originally posted by Teutep:

Originally posted by Niknokinater:

I'm about a year too late unfortunately

What?

You know you can just make an empty folder practically anywhere on the disk under [Steam > Settings > Downloads > Steam Library Folders], exit Steam and move the steamapps\ -folder within the new folder.

Just don't place the new folder under Program Files (x86).

The goal is to avoid copying/cutting 228Gb of games. That steamapps folder is a BRICK xD

Originally posted by Teutep:

Even right now I just use Steam under

C:\	C:\Games\Steam
D:\	D:\Games\SteamLibrary
E:\	E:\Games\SteamLibrary

Ah niiice. Wish I'd have thought of that a bit earlier lel

[Tev]

Personally I'd just make a new folder outside Program Files (x86) and move it there. Suck it up with the moving, it's only 200 GB.

Well, alternatively, you can try to go to your new Steam location, go under steamapps\. Open up libraryfolders.vdf with WordPad. Edit in the path like I have (not word to word, as your paths aren't the same as mine).

"LibraryFolders"
{
	"TimeNextStatsReport"		"UNIX timestamp"
	"ContentStatsID"		"ContentStatsID"
	"1"		"E:\\Games\\SteamLibrary"
	"2"		"D:\\Games\\SteamLibrary"
}

No promises that'll work with a folder that's under Program Files (x86). I'd also remove (or rename) the libraryfolders.vdf from within that ex-location; NOT PRIMARY, while I'd imagine it'll be ignored.

As another alternative,

1. [Steam > Settings > Downloads > Steam Library Folders]
   
2. Place a folder on your ex-primary. Let's pretend its path is D:\Games\Steam.
   
3. Exit Steam (Top left: [Steam > Exit])
   
4. Open up cmd.exe as an administrator (still assuming your ex-primary is D:\)
   

   mklink /d "D:\Games\Steam\steamapps" "D:\Program Files (x86)\Steam\steamapps"

5. Press Enter and you should get a folder called steamapps within D:\Games\Steam that redirects to your previous games folder.
   
6. Consider removing (or renaming) libraryfolders.vdf (from that previous location), while it's probable it'll be ignored anyway.

[Niknokinater]

Ah I just went and wiped the drive anyway. I'll get around to downloading the games again over time. Didn't really need anything else that was on there.

Thanks for responding lad ^^ Still think that Steam should support adding previously filled libraries though. That'd be pretty solid.