Vortex Spontaneously deciding Skyrim Special Edition isn't installed.

[Kirosamasan]

So quick breakdown. I'm playing Skyrim Special Edition modded using Vortex, and everything is fine. I get off and go to sleep. The next day I went to play again, and it's saying Skyrim is uninstalled!? I double check to make sure, and yep Skyrim didn't uninstall itself magically overnight. Check the error again and it gives me.

SetupError: Missing: c:\program files (x86)\steam\steamapps\common\Skyrim Special Edition\Data
    at C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:2980:145
    at tryCatcher (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:547:31)
    at Promise._settlePromise (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:604:18)
    at Promise._settlePromise0 (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:649:10)
    at Promise._settlePromises (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:725:18)
    at _drainQueueStep (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:93:12)
    at _drainQueue (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:86:9)
    at Async._drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:102:5)
    at Async.drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:15:14)

So I decide to check where it's looking for the game and it's the right place, manually set it again just to try, and it tells me that it can't find SkyrimSE.exe, well no surprise there considering it's SkyrimSELauncher.exe that's used to launch the game. Anyways, this is in fact the second time this issue has come up, and the only fix I've found is REINSTALLING Skyrim SE. This is because changing the name of Skyrim SE's launcher breaks the game (no surprise).  I know this must come off as rude, but please Vortex team fix whatever wacky line/s of code is causing this issue.