Deleted180062886User

thanks for the reply. Much as it sounds an easy fix, and much as I might sound pArANoId, for selfishly pragmatic reasons (security) I'll have to forgo that until Nexus officially responds and explains, since no other application or website is reporting any such issues. in any case, a figurative thumbs up, and fwiw, if they come back with the same advise, then you get the "Marked Solved" creds. Thanks lol, I completely understand, hopefully the next update solves this without users having to try as many things as I did

I had the same problem this week, spoke about it in a couple of the other threads. Idk what happened with the update, but I was able to fix the issue by power cycling my wi-fi router. I hope this works for you, too

I apparently have fixed the problem by power cycling my router, hope this works for you, too

I apparently have fixed the problem by power cycling my router, hope this works for you, too

That was the first thing I tried, it just searches for the file and fails twice, then you get the same original message like OP says. Happens every time I open Vortex.

For me it has been doing this the past 4 days, I have tried making vortex exceptions in my firewall, updating windows, switching to beta branch, uninstalling, reinstalling, installing previous versions of vortex which then updated to the current one, resetting my wi-fi adapter, installing the LOOT program, manually updating the masterlist and prelude, nothing has worked.

I have this same problem, I think it's a bug with the latest version as I never had the issue until a few days ago.

Didn't work for me sadly, appreciate you trying to help. I think my setup hates the last vortex update for whatever reason, I guess I'll just wait for confirmation on whether I can still play my modded game with this error.

The thing is, it was and has been working perfectly for a long while now, it's only a few days ago that these errors popped up, and as far as i'm aware my network hasn't changed since then. I made a new inbound and outbound rule in the windows firewall for github.com to allow the connection on github's addresses just now but that didn't change anything. I'm at a loss for what to do to get it working again. I have this same problem with the masterlist not updating for Fallout 4, glad to see it's not just me. Started 2 days ago and adding exceptions through my firewall did not help. Does anyone know if the game is playable with this error or am I forced to wait this out? Afraid to try myself.