Archive check was bundled few years back to avoid users attempting to load BSA intended for different games. Disabling won't do much for deployment process.
I've been installing Vortex outside Program Files default path for a while, try targeting (C:)/<new folder>/* next time you reinstall. For now, that's all I got.
Essentially combines or "merges" mod folders. Select "mods" to combine, target parent mod to merge into and if any load after rules, etc. it'll overwrite.
Also, can't combine different mod types.
This matches my local copy but is only band-aid solution as Vortex should verify integrity/regenerate new
GitHub - loot/skyrimse at v0.21 - https://github.com/loot/skyrimse/archive/refs/heads/v0.21.zip
Let me know if this copy suppresses sort/deployment error notif once added to masterlist folder.
That connection failure is obv the underlying issue here bc it should be an automatic thing that doesn't require any user interaction other than being "online".
Try looking for masterlist referenced in LOOT forum response. It failing on sort/deployment makes sense since its version doesn't match what Vortex expect.
I can't upload my copy bc is too big for non-premium I guess...
Only advice I'd have is do full uninstall via uninstall vortex.exe and clean up/delete all directories before trying new tests to keep troubleshooting core error.
Maybe avoid making your users name a single letter too. Doesn't seem like a common thing to do.
Is that your mods Staging folder?
Also, your masterlist.yaml isn't the same as mine. Did you try grabbing it from LOOT's github or is that what Vortex automatically generates?
Post a full pic of this folder directory, as well as attach copy of your existing(?) > C:\\Users\\a\\AppData\\Roaming\\Vortex\\skyrimse\\masterlist\\masterlist.yaml
Nevermind, file sizes are too big for here.