New Steam Library Folder On Same Drive?

[Dyantier]

I can't seem to make another steam library folder on my same drive. I want to make a library folder in C:/SteamLibrarySSD. However, I keep receiving this message every time I try to designate that as a steam library folder,

"Selected drive already has a Steam library folder. Steam will manage multiple game installs in a single folder for you."

Any help would be greatly appreciated. :)

[Elder]

Автор сообщения: QC_General_QC

The latest suggested solution did not work for me for some reason. I instead used this tool

https://github.com/LostDragonist/steam-library-setup-tool/wiki/Usage-Guide

Worked like a charm in less than a minute!

OMG that did it! Thank you and the author of the program

[Klorgor]

Автор сообщения: magnapinna

The new workaround 100% worked for me. I will say though that it was incredibly aggravating.

It was just one thing in that I kept missing. After a good hour or so of bashing my head into the keyboard, wondering why steam kept overriding the location I entered, I realised that every single backslash needs to be a double backslash meaning you can't just copy & paste from windows explorer address bar

The full formatting looks like this, in case anyone is struggling in the future

"libraryfolders"
{
"contentstatsid" "numbers"
"0"
{
"path" "C:\\Program Files (x86)\\Steam"
.
.
.
.
.
.
{
}
}
"1"
{
"path" "C:\\Users\\me\\Documents\\Games\\Steam"
//You can leave this part blank and it'll auto-fill when you launch Steam//
}
}


Regardless, I still have no idea why Steam can't just let you do this in the app. I'm sure that there's a valid reason, but it would be good to know why we have to resort to bizarre workarounds for what seems like a common and simple issue.

Hi I edited the libraryfolders.vdf in C:\Program Files (x86)\Steam\config like this:

"libraryfolders"
{
"contentstatsid" "numbers"
"0"
{
"path" "C:\\Program Files (x86)\\Steam"
"label" ""
"contentid" "numbers"
"totalsize" "0"
"update_clean_bytes_tally" "0"
"time_last_update_corruption" "0"
"apps"
{
}
}
"1"
{
"path" "C:\\Games\\Steam"
"label" ""
"contentid" "numbers"
"totalsize" "0"
"update_clean_bytes_tally" "0"
"time_last_update_corruption" "0"
"apps"
{
}
}
}

And still Steam does not recognize it as a new install path. Any solutions?

[Klorgor]

Автор сообщения: Klorgor

Автор сообщения: magnapinna

The new workaround 100% worked for me. I will say though that it was incredibly aggravating.

It was just one thing in that I kept missing. After a good hour or so of bashing my head into the keyboard, wondering why steam kept overriding the location I entered, I realised that every single backslash needs to be a double backslash meaning you can't just copy & paste from windows explorer address bar

The full formatting looks like this, in case anyone is struggling in the future

"libraryfolders"
{
"contentstatsid" "numbers"
"0"
{
"path" "C:\\Program Files (x86)\\Steam"
.
.
.
.
.
.
{
}
}
"1"
{
"path" "C:\\Users\\me\\Documents\\Games\\Steam"
//You can leave this part blank and it'll auto-fill when you launch Steam//
}
}


Regardless, I still have no idea why Steam can't just let you do this in the app. I'm sure that there's a valid reason, but it would be good to know why we have to resort to bizarre workarounds for what seems like a common and simple issue.

Hi I edited the libraryfolders.vdf in C:\Program Files (x86)\Steam\config like this:

"libraryfolders"
{
"contentstatsid" "numbers"
"0"
{
"path" "C:\\Program Files (x86)\\Steam"
"label" ""
"contentid" "numbers"
"totalsize" "0"
"update_clean_bytes_tally" "0"
"time_last_update_corruption" "0"
"apps"
{
}
}
"1"
{
"path" "C:\\Games\\Steam"
"label" ""
"contentid" "numbers"
"totalsize" "0"
"update_clean_bytes_tally" "0"
"time_last_update_corruption" "0"
"apps"
{
}
}
}

And still Steam does not recognize it as a new install path. Any solutions?

EDIT: NVM, fix it with this: https://github.com/LostDragonist/steam-library-setup-tool/wiki/Usage-Guide

Now it is working.

[Vampe777]

Автор сообщения: TopTuk

Автор сообщения: khobay

This does not work. Everytime Steam opens it simply overwrites the libraryfolders.vdf file.

Nope, edit C:\Program Files (x86)\Steam\config\libraryfolders.vdf

That worked ! Finally ! Thank you very much, I was trying to do that for ~hour! And now it turns out that I just need to scroll this topic to its end to see the solution ^-^
P.S. Also I created "steamapps" in this folder before it worked, just in case someone will have same problem again

[MayTi]

Just did it on a new system and found it even easier than before.
adding folder C:\Games
3 easy steps;

1-modify C:\Program Files (x86)\Steam\config\libraryfolders.vdf:
exactly before last brackets pasted this

"1"
{
"path" "C:\\Games"
}

2-Created the folder "Games" in C:\ , then created the folder "steamapps" in Games folder

3-Copied "steam.dll" from C:\Program Files (x86)\Steam into C:\Games

Thats all. Started steam and installed the games.

[forabora]

Автор сообщения: Klorgor

EDIT: NVM, fix it with this: https://github.com/LostDragonist/steam-library-setup-tool/wiki/Usage-Guide

Now it is working.

THANK YOU THANK YOU THANK YOU!
No manual editing libraryfolders.vdf worked for me.
But this tool did it. Thank you again.

[anonecki]

Автор сообщения: darkliquid

I couldn't get any of the mentioned methods to work with the latest steam update, so I decided to simply make my folders have a custom drive letter, like so by executing the following command:

subst X: C:\Games\SteamLibrary

And then adding that folder from the new X: drive to the steam libraries list.

This worked perfectly, now I can finally play System Shock 2

[DrakEmono]

Hi! I would like some help as I tested everything from the last page, and nothing works (manual edition, software, ect...)
Can anyone help? Thanks!

[Klorgor]

Автор сообщения: DrakEmono

Hi! I would like some help as I tested everything from the last page, and nothing works (manual edition, software, ect...)
Can anyone help? Thanks!

Here: https://github.com/LostDragonist/steam-library-setup-tool/wiki/Usage-Guide

[Blake]

This thread was quite old before the recent post, so we're locking it to prevent confusion.