Jump to content

Error: Failed to initialize LOOT


JonySnowball

Recommended Posts

Same for me with the real user name "û"

Error: Given game local path "C:\Users\û\AppData\Local\Fallout4" does not resolve to a valid directory.
at c.handleResponse (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\webpack:\gamebryo-plugin-management\node_modules\loot\index.js:167:1)
at Socket.handleResponse (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\webpack:\gamebryo-plugin-management\node_modules\loot\index.js:80:1)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)
at Socket.Readable.push (_stream_readable.js:208:10)
at Pipe.onread (net.js:594:20)

 

Wait for the fix.

ty.

Link to comment
Share on other sites

  • Replies 77
  • Created
  • Last Reply

Mine doesnt initialise loot since the update as well. mine comes up with

 

Error: symlink_status: The parameter is incorrect.
: "D:\Games\Steam\steamapps\common\Fallout 4\"
at c.handleResponse (D:\Games\Vortex install location\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\webpack:\gamebryo-plugin-management\node_modules\loot\index.js:167:1)
at Socket.handleResponse (D:\Games\Vortex install location\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\webpack:\gamebryo-plugin-management\node_modules\loot\index.js:80:1)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)
at Socket.Readable.push (_stream_readable.js:208:10)
at Pipe.onread (net.js:594:20)

 

It does this for skyrim as well. even uninstalled and reinstalled vortex too. I don't think mine has the same problem as everyone else :L

Link to comment
Share on other sites

Mine doesnt initialise loot since the update as well. mine comes up with

 

Error: symlink_status: The parameter is incorrect.

: "D:\Games\Steam\steamapps\common\Fallout 4\"

at c.handleResponse (D:\Games\Vortex install location\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\webpack:\gamebryo-plugin-management\node_modules\loot\index.js:167:1)

at Socket.handleResponse (D:\Games\Vortex install location\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\webpack:\gamebryo-plugin-management\node_modules\loot\index.js:80:1)

at emitOne (events.js:116:13)

at Socket.emit (events.js:211:7)

at addChunk (_stream_readable.js:263:12)

at readableAddChunk (_stream_readable.js:250:11)

at Socket.Readable.push (_stream_readable.js:208:10)

at Pipe.onread (net.js:594:20)

 

It does this for skyrim as well. even uninstalled and reinstalled vortex too. I don't think mine has the same problem as everyone else :L

 

 

Curious as to why it's saying "SYMLINK STATUS".

 

Do you have your Mod Staging Folder on the same drive as your games?

Link to comment
Share on other sites

Same issue here. Was working fine until yesterday (I guess?), now won't initialize LOOT. I'm assuming it has to do with the different drives shown here; but am not sure why it would have been working before? Was going to try too just copy paste into F: but I'm new to this program (and really know only enough to be really dangerous lol) so wanted to ask here first.

 

Error: symlink_status: The parameter is incorrect.
: "F:\SteamLibrary\steamapps\common\Skyrim Special Edition\"
at c.handleResponse (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\webpack:\gamebryo-plugin-management\node_modules\loot\index.js:167:1)
at Socket.handleResponse (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\webpack:\gamebryo-plugin-management\node_modules\loot\index.js:80:1)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)
at Socket.Readable.push (_stream_readable.js:208:10)
at Pipe.onread (net.js:594:20)
Link to comment
Share on other sites

 

Same issue here. Was working fine until yesterday (I guess?), now won't initialize LOOT. I'm assuming it has to do with the different drives shown here; but am not sure why it would have been working before? Was going to try too just copy paste into F: but I'm new to this program (and really know only enough to be really dangerous lol) so wanted to ask here first.

 

Error: symlink_status: The parameter is incorrect.
: "F:\SteamLibrary\steamapps\common\Skyrim Special Edition\"
at c.handleResponse (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\webpack:\gamebryo-plugin-management\node_modules\loot\index.js:167:1)
at Socket.handleResponse (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\webpack:\gamebryo-plugin-management\node_modules\loot\index.js:80:1)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)
at Socket.Readable.push (_stream_readable.js:208:10)
at Pipe.onread (net.js:594:20)

 

 

 

Since nobody answered...

 

do YOU have your Mod Staging Folder on the same drive as your games?

Link to comment
Share on other sites

HI, thanks for the quick response. Yes, I do. I actually have games on both C and F; but have Steam, Vortex and Vortex mods files on F. As I said it was working just fine at first. (I just started using it a few days ago, I only ever used FOMM before). I can provide a screenshot of the file paths once I figure out how to do that here lol.

Link to comment
Share on other sites

HI, thanks for the quick response. Yes, I do. I actually have games on both C and F; but have Steam, Vortex and Vortex mods files on F. As I said it was working just fine at first. (I just started using it a few days ago, I only ever used FOMM before). I can provide a screenshot of the file paths once I figure out how to do that here lol.

 

 

OK, so do you get this error no matter if you're using a game on the C and F drive, or does the error only pop up for the games that are on the C drive?

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...