Nexus-Mods / Vortex

Vortex Development
GNU General Public License v3.0
900 stars 131 forks source link

Game Extension not loaded (Skyrim Special Edition) / Invalid game extension: should have required property 'requiredFiles' #14399

Closed Enesore closed 1 year ago

Enesore commented 1 year ago

Happens on every Vortex 1.8.5 launch. I do not have Skyrim SE installed.

vortex.log

kelerena commented 1 year ago

I have a similar problem The only way I could achieve it was by making Steam my primary instead of SKSE. Could this cause the problem? Also, I reinstalled the vortex, but it's still not good.

vortex_log.txt

/Facepalm/ Problem solved, I deleted the folder C:\Users\xxxx\AppData\Roaming\Vortex\plugins\Vortex Extension Update - Skyrim_ Special Edition v1.0.4

Kherosen commented 1 year ago

Same issue at your same time. I was installing some collections for skyrim AE and everything was fine, then all of a sudden it collapsed lmao. I tried to solve it by repairing skyrim trough steam, but didn't work... then i tried to reinstall Vortex, run it both normally and as admin, but dodn't work. i also tried to delete the extensions in vortex regarding skyrim, but didn't work either... not sure why it happened and not sure how to solve it... still trying tho, if i manage to solve it i'll post here.

/EDIT/1

Not sure why now it worked, but after deleting the extension a few times and restarting vortex a few times, now it's working

/EDIT/2

I think it was a problem with the vortex server, because those issues happened to us at the same time and got solved in the same time, but i'm not sure... anyway, it started to work again after deleting the skyrim extension a few times

/EDIT/3

Another thought about this... before this happened, i wasn't able to download mods from nexus... i was clicking on download, waiting those 5 secs because i'm a poor non premium dog lmao, but the vortex manager wasn't responding

Str1spectre commented 1 year ago

Problem resolved

Enesore commented 1 year ago

This appears to be resolved now.

Kherosen commented 1 year ago

This appears to be resolved now.

What did you do to solve the issue on your side?