VoidsShadow

Anyway, this turned out to be a user error.

I hadn't touched the mods folders in months, so it wasn't even on my mind. I've previously considered using third-party software to make periodic backups, but my mod collection was nearing 30GB. If I were to use LZMA2 compression with high compression ratio parameters (e.g. 768MB Dictionary Size), the backups would add up in size more slowly, but it would take hours for each backup to compress. The compression would be pretty demanding on CPU resources if I were to use the aforementioned high-compression settings.

It's mostly my fault for not keeping myself informed of Vortex's development. :/

That's exactly what the issue was. I originally had a symbolic link from the ProgramData location to my J partition. At the time, I wanted everything that wasn't Windows off of my C partition and Vortex was proving to be a pain. So, Vortex's executable would be at "J:/Vortex/Vortex.exe" alongside the downloads folder and the staging folders. It was nice to have Vortex all in one place while it lasted. Okay, I think I had actually lost those files somewhere between December and late January.

Note: my mod staging folder and downloads folder were under the install directory at "J:/Vortex/". I was trying to keep all of my Vortex-related files in one place so I could keep track of it better. Luckily, that drive is 3TB and isn't written to very often. Recuva has its work cut out for it. P.S. My mistake. I may have lost those files longer ago than I thought.

On the bright side, it did warn me that it would not be backwards compatible with previous versions of Vortex. Anyway. There goes over 2,000 mods collected over the past 6 years. TL;DR User error/ignorance

In response to post #55255198. "Not long now!"

I apparently needed this file to install OverUnity: https://github.com/myanaloglife/office-2013-vl/blob/master/OfficeProPlus/x86/proplus.ww/proplusww.msi

http://i.imgur.com/NY5OPT1.gif