zetim

To clarify: Technically the location of the game is only indirectly relevant, what matters is the application directory of Vortex itself and .NET and then the staging folder (settings->mods). If you're modding bethesda games or a few others you will definitively have set the staging folder to be on the same drive as the games though. If you can successfully install mods for games with the staging folder on not-C then that rules out the application directories and it's indeed the staging folder that is the problem. The necessary access rights for the Vortex app directory are given by its installer, the access rights for .NET are given by default on windows (unless user "mis"configured the system, see pinned message), the access rights for the staging folder are given by Vortex at runtime. That requires your windows account to own the staging folder but that will usually be the case because Vortex creates that folder for your account. So the only way I can see that the pinned fixes wouldn't work but only on one drive but not the others is if the staging folder there isn't actually owned by your account. So either you have a second windows account (could also be something like a dedicated admin account) that created that folder or you moved that folder from a different windows install and didn't update the owner. I think I'm in a similar boat. I upgraded from windows 7. I have vortex installed on my C: drive, but steam and most of my games are on a separate drive. I am definitely the owner of all the drives, unless the Windows 10 upgrade utility did some wonk. This setup was a little wonky on windows 7 with permissions, but I got it working. I updated to windows 10 and hadn't used vortex in a while. Tried to use it this week and started getting the .net error. Went through most of these fixes, but couldn't actually edit permissions in my C:/program files folder where vortex is installed, becuase it's greyed out (I'm assuming from inheretence? I'm not 100% on how windows 10 does stuff tbh), and it's also already there. I tried adding the ALL APPLICATION PACKAGES to the steam folder where my games are installed, and to the folder where the mods are stored on the same drive. None of this has worked. I still get the same error in Vortex. I haven't tried reinstalling Vortex, or disabling sandbox, yet. I would rather reinstall Vortex, but I'm worried about losing the mod configuration on the reinstall. I assume it won't tear out mods from games on its way out, but I am worried that it won't know what mods are installed already and how to handle them for modification going forwards. I didn't see anything in a QA or FAQ about how Vortex handles mod configurations, whether it's tied into the program locally or stored in some sort of app data folder that will be retained even when uninstalled or something akin to that. I'm assuming most of this mess was caused by the windows 10 upgrade shuffling things around in a way that vortex was not designed to handle (and honestly that it still works at all after an OS change is something of a miracle), and a reinstall would potentially fix that. I've included my error and dotnet info here: Asking OP/devs in general, can I safely uninstall and reinstall Vortex? Or will that break everything?