Mod Deployment issue, "Mod Staging folder missing" Error

[DasDestomicthenoob]

So about a month and a half ago, I got a new Hard Drive (New Drive :K) to replace my old Hard Drive that lacked the space to hold my mods (Drive :I).

 

After my PC finished transferring all data recorded from the old Drive onto the new one... And I attempted to load up Vortex, it gave me a number of errors, ranging from the colors blue, orange, and red.

 

<- Image of all errors incurred.

 

Part 1: Staging Errors/Directory Issues

 

"Failed to move directories"

 

I uninstalled Vortex, and then reinstalled it in my :K Drive as it gave me the error saying there was a "Staging Error" which I assume translates to, "Hey, you took the :I Drive out, where da hell you gonna put your mods now?"

 

So after doing so, I attempted to alternate the Mod Staging Folder for Fallout New Vegas from something along the lines of,

"I:\Vortex Mods\Something\Something\Fallout New Vegas"

to

"K:\Vortex Mods\Fallout New Vegas"

 

After which I clicked the orange "Apply Button" to it after selecting it's pathway, then got the subsequent errors saying, Vortex tried to access "I:\Games\Vortex\Fallout New Vegas" but it doesn't exist.

As I clicked the "Show Details" button below it, all it gave me was an enormous wall of things I didn't recognize:

ENOENT: no such file or directory, stat 'I:\Games\Vortex\Fallout New Vegas'

Error

at Object.chmodAsync [as statAsync] (K:\Program Files\Vortex\resources\app.asar\webpack:\src\util\fs.ts:227:3)

at isOnSameVolume (K:\Program Files\Vortex\resources\app.asar\webpack:\src\util\transferPath.ts:50:10)

at Object.testPathTransfer (K:\Program Files\Vortex\resources\app.asar\webpack:\src\util\transferPath.ts:52:44)

at ensureDirAsync (K:\Program Files\Vortex\resources\app.asar\webpack:\src\extensions\mod_management\views\Settings.tsx:259:22)

at Object.da (K:\Program Files\Vortex\resources\app.asar\node_modules\react-dom\cjs\react-dom.production.min.js:14:428)

at ka (K:\Program Files\Vortex\resources\app.asar\node_modules\react-dom\cjs\react-dom.production.min.js:15:118)

at la (K:\Program Files\Vortex\resources\app.asar\node_modules\react-dom\cjs\react-dom.production.min.js:15:172)

at ya (K:\Program Files\Vortex\resources\app.asar\node_modules\react-dom\cjs\react-dom.production.min.js:17:210)

at Ca (K:\Program Files\Vortex\resources\app.asar\node_modules\react-dom\cjs\react-dom.production.min.js:18:248)

at Aa (K:\Program Files\Vortex\resources\app.asar\node_modules\react-dom\cjs\react-dom.production.min.js:18:57)

at Fa (K:\Program Files\Vortex\resources\app.asar\node_modules\react-dom\cjs\react-dom.production.min.js:21:69)

at Gd (K:\Program Files\Vortex\resources\app.asar\node_modules\react-dom\cjs\react-dom.production.min.js:84:409)

at Pi (K:\Program Files\Vortex\resources\app.asar\node_modules\react-dom\cjs\react-dom.production.min.js:249:259)

at Nb (K:\Program Files\Vortex\resources\app.asar\node_modules\react-dom\cjs\react-dom.production.min.js:39:140)

at Jd (K:\Program Files\Vortex\resources\app.asar\node_modules\react-dom\cjs\react-dom.production.min.js:86:249)

at Ri (K:\Program Files\Vortex\resources\app.asar\node_modules\react-dom\cjs\react-dom.production.min.js:250:103)

Part 2: Access Issues/Mod Read Errors

"Failed to refresh mods"

 

One of the other issues I ran into was the constant read errors that struck me, which said, "Vortex tried to access "I:\" but it doesn't exist" Which would crop up after the Directory Issues happened, and of course gave me yet another wall of errors saying,

ENOENT: no such file or directory, mkdir 'I:\'

Error

at Object.resolve [as ensureDirAsync] (K:\Program Files\Vortex\resources\app.asar\webpack:\src\util\fs.ts:267:26)

at Object.filtered [as default] (K:\Program Files\Vortex\resources\app.asar\webpack:\src\extensions\mod_management\util\refreshMods.ts:19:13)

at modNames (K:\Program Files\Vortex\resources\app.asar\webpack:\src\extensions\mod_management\eventHandlers.ts:148:9)

at tryCatcher (K:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23)

at Promise._settlePromiseFromHandler (K:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:512:31)

at Promise._settlePromise (K:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:569:18)

at Promise._settlePromise0 (K:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:614:10)

at Promise._settlePromises (K:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:693:18)

at Promise._fulfill (K:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:638:18)

at Promise._resolveCallback (K:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:432:57)

at Promise._settlePromiseFromHandler (K:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:524:17)

at Promise._settlePromise (K:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:569:18)

at Promise._settlePromise0 (K:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:614:10)

at Promise._settlePromises (K:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:693:18)

at Promise._fulfill (K:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:638:18)

at Promise._resolveCallback (K:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:432:57)

 

and has left me clueless on how to fix this.

 

Part 3: Deployment Errors

 

"Mods can't be deployed."

 

What is most likely the 2nd Worst issue I've ran into with this application is the deployment errors, which are in no way helpful or inciteful. Before anyone asks, yes I've attempted to search the forums for as long as I could before getting frustrated with other threads that never helped, and I've been trying to do this for the past month and a half.

This Error has a button next to it with the word, "Fix"... Although when clicked on provides me a thing saying that Vortex supports a variety of different deployment methods, but only offers them amongst certain platforms... [in this case, I am using Fallout New Vegas, which IS supported, but Vortex is aids and gives me these errors]

 

But after clicking the "Next" button to reveal any sort of information, I am granted with by far what I have seen as the biggest middle finger Nexus Mods has ever given me:

 

 

It offers no guidance whatsoever, and overall has left me stumped awaiting someone to reply to my post.

 

 

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

Once again; I've been stuck with this problem coming back to it almost every single day for the past month and a half, so whoever manages to fix this problem...

(believe me, I'll do whatever it takes to fix this damn problem even if it means wiping something [dunno what] entirely and putting it back in, I don't even care about my progress anymore)

...Will have my most sincerest respect and gratitude.

[HadToRegister]

So about a month and a half ago, I got a new Hard Drive (New Drive :K) to replace my old Hard Drive that lacked the space to hold my mods (Drive :I).

 

After my PC finished transferring all data recorded from the old Drive onto the new one... And I attempted to load up Vortex, it gave me a number of errors, ranging from the colors blue, orange, and red.

 

Once again; I've been stuck with this problem coming back to it almost every single day for the past month and a half, so whoever manages to fix this problem...

(believe me, I'll do whatever it takes to fix this damn problem even if it means wiping something [dunno what] entirely and putting it back in, I don't even care about my progress anymore)

...Will have my most sincerest respect and gratitude.

 

 

The easiest solution to this would've been to change your Drive letter K to drive Letter I, then Vortex and the rest of your system would've continued on as if nothing had changed.

I do it all the time, I put in the new drive, copy everything from the OLD drive to the NEW drive.

Change the drive letter of the old drive to something different, change the new drive letter to what the old drive letter was.

Shut down the computer, remove the old drive, then boot up, and my system doesn't know that anything has changed other than the drive is bigger, all my paths are the same, because the new drive is using the old drive Letter.

 

How to change a drive letter

[BigBizkit]

 

Part 3: Deployment Errors

 

"Mods can't be deployed."

 

What is most likely the 2nd Worst issue I've ran into with this application is the deployment errors, which are in no way helpful or inciteful. Before anyone asks, yes I've attempted to search the forums for as long as I could before getting frustrated with other threads that never helped, and I've been trying to do this for the past month and a half.

This Error has a button next to it with the word, "Fix"... Although when clicked on provides me a thing saying that Vortex supports a variety of different deployment methods, but only offers them amongst certain platforms... [in this case, I am using Fallout New Vegas, which IS supported, but Vortex is aids and gives me these errors]

 

But after clicking the "Next" button to reveal any sort of information, I am granted with by far what I have seen as the biggest middle finger Nexus Mods has ever given me:

Screenshot (259).jpg

 

It offers no guidance whatsoever, and overall has left me stumped awaiting someone to reply to my post.

 

 

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

Once again; I've been stuck with this problem coming back to it almost every single day for the past month and a half, so whoever manages to fix this problem...

(believe me, I'll do whatever it takes to fix this damn problem even if it means wiping something [dunno what] entirely and putting it back in, I don't even care about my progress anymore)

...Will have my most sincerest respect and gratitude.

 

 

I agree that the text for "Solution" on that one could be better. But the text outlining the problem is accurate. Symlink deployment is not compatible with Fallout: New Vegas nor any other Bethesda game - due to how modding for these games works. You have to go with either move deployment, which is experimental and thus not recommended, or hardlink deployment (the default, which is recommended).

 

 

 

That being said, your issues seem to stem from the fact that you reinstalled Vortex while also moving your mod staging folder to a non-default location. The solution outlined by HadToRegister seems fairly sensible, though you might be better off starting from scratch in your case.

[DasDestomicthenoob]

 

So about a month and a half ago, I got a new Hard Drive (New Drive :K) to replace my old Hard Drive that lacked the space to hold my mods (Drive :I).

 

After my PC finished transferring all data recorded from the old Drive onto the new one... And I attempted to load up Vortex, it gave me a number of errors, ranging from the colors blue, orange, and red.

 

Once again; I've been stuck with this problem coming back to it almost every single day for the past month and a half, so whoever manages to fix this problem...

(believe me, I'll do whatever it takes to fix this damn problem even if it means wiping something [dunno what] entirely and putting it back in, I don't even care about my progress anymore)

...Will have my most sincerest respect and gratitude.

 

 

The easiest solution to this would've been to change your Drive letter K to drive Letter I, then Vortex and the rest of your system would've continued on as if nothing had changed.

I do it all the time, I put in the new drive, copy everything from the OLD drive to the NEW drive.

Change the drive letter of the old drive to something different, change the new drive letter to what the old drive letter was.

Shut down the computer, remove the old drive, then boot up, and my system doesn't know that anything has changed other than the drive is bigger, all my paths are the same, because the new drive is using the old drive Letter.

 

How to change a drive letter

 

Yeah here's the problem; I have attempted to change the Drive Letter and have taken my PC to Technical Support before and the underlying issue was that I physically cannot change the Drive Letter from K to I. We have no idea why this is.

I don't remember if I'm able to actually change it to anything else aside from Letter K, but from what I've seen, changing the driver letter to I is simply impossible.

[DasDestomicthenoob]

 

 

Part 3: Deployment Errors

 

"Mods can't be deployed."

 

What is most likely the 2nd Worst issue I've ran into with this application is the deployment errors, which are in no way helpful or inciteful. Before anyone asks, yes I've attempted to search the forums for as long as I could before getting frustrated with other threads that never helped, and I've been trying to do this for the past month and a half.

This Error has a button next to it with the word, "Fix"... Although when clicked on provides me a thing saying that Vortex supports a variety of different deployment methods, but only offers them amongst certain platforms... [in this case, I am using Fallout New Vegas, which IS supported, but Vortex is aids and gives me these errors]

 

But after clicking the "Next" button to reveal any sort of information, I am granted with by far what I have seen as the biggest middle finger Nexus Mods has ever given me:

Screenshot (259).jpg

 

It offers no guidance whatsoever, and overall has left me stumped awaiting someone to reply to my post.

 

 

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

Once again; I've been stuck with this problem coming back to it almost every single day for the past month and a half, so whoever manages to fix this problem...

(believe me, I'll do whatever it takes to fix this damn problem even if it means wiping something [dunno what] entirely and putting it back in, I don't even care about my progress anymore)

...Will have my most sincerest respect and gratitude.

 

 

I agree that the text for "Solution" on that one could be better. But the text outlining the problem is accurate. Symlink deployment is not compatible with Fallout: New Vegas nor any other Bethesda game - due to how modding for these games works. You have to go with either move deployment, which is experimental and thus not recommended, or hardlink deployment (the default, which is recommended).

 

 

 

That being said, your issues seem to stem from the fact that you reinstalled Vortex while also moving your mod staging folder to a non-default location. The solution outlined by HadToRegister seems fairly sensible, though you might be better off starting from scratch in your case.

 

 

So what should I do? I can't change the Drive Letter whatsoever, but how can I just wipe the slate clean and re-do everything, or is there an even easier option?

[HadToRegister]

 

 

That being said, your issues seem to stem from the fact that you reinstalled Vortex while also moving your mod staging folder to a non-default location. The solution outlined by HadToRegister seems fairly sensible, though you might be better off starting from scratch in your case.

 

 

So what should I do? I can't change the Drive Letter whatsoever, but how can I just wipe the slate clean and re-do everything, or is there an even easier option?

 

 

I told you the easiest option.

 

The thing is, when you moved everything from the I drive to the K drive, Windows wrote all of the new paths into the registry, there was no way that was going to work.

 

The only thing that can stop you from changing your Drive from K to I, is either you already have another drive that took the letter I, or because you moved everything, then took out the I drive and left the new drive as K, and the Hardlinks are convincing the system that Drive I still exists in your system

Try hitting Windows Key + X and picking Disk Management

 

Now, the list should show you whether you have a Drive with the Letter I

 

If it doesn't, you should be able to right click on Drive K and pick "Change Drive Letters and Paths" and pick I: from the drop down.