Replies: 2 comments 2 replies
-
The user's OS seemingly had some suspicious changes, either by modding too much, or viruses, or somesuch. Basic operations were failing with the above style errors. The fixes were to find the folders that it was complaining about and give the user "full control". There were several paths it complained about, and each needed to be given full control permission While this fixed the issue, my recommendation was to also look into reinstalling the OS to get a fresh start at some point |
Beta Was this translation helpful? Give feedback.
-
If user has installed a Wabbajack modlist, settings from the modlist author's Synthesis may have carried over and the issue could be due to incompatibility between the Wabbajack installed Synthesis settings and user PC. To resolve, uninstall the Wabbajack Synthesis in {modlist name}/tools and reinstall Synthesis from GitHub to same location. MO2 should be able to run Synthesis again without any issue. Trade-off is that any installed patchers in the Wabbajack Synthesis would also be deleted, so make a list to reinstall if those are important. |
Beta Was this translation helpful? Give feedback.
-
Synthesis either:
Beta Was this translation helpful? Give feedback.
All reactions