Steam crashes when adding existing SteamLibrary

[Cheezymon]

I had an issue after a Steam update where it wouldn't launch.

I fixed this by completely uninstalling Steam.

Adding the library on my F: drive works fine, as soon as I add the library on my D: drive Steam crashes and then refuses to launch.

Renaming the library so that Steam doesn't try to load it anymore will get Steam working again, the library is 830GB so it would be nice if anyone knew what might be making it crash steam!

[joebobschwabe]

Hey, this JUST happened to me. Same sort of issue. I woke my computer from sleep, and it wouldn't fully wake (I think it something with Windows 10 and Nvidia, I use surround on 3 monitors), so I do what I always do, hard restart. When it came back up a couple seconds later, Steam wouldn't launch. It would be "running" when I look in the task manager, but it wasn't showing as an active window nor a background program in the task bar. I uninstalled and re-installed, and it came back up fine. I added my H: drive, and it recognized the 360 games on it. Cool, I added my F: drive, and it froze the whole program up. White overlay, spinning blue loading mouse icon, then finally, Windows dialog box asking if I want to wait for it to respond or shut it down. S.M.A.R.T test is good on all my drives. Just running chkdsk on my F: drive right now, but so far, zero bad sectors.