Replies: 6 comments 28 replies
-
|
NOTE: This is not the solution for most people. Keeping of obscure reference if the rest of the discussions aren't helping This probably isn't the cause for most people, but one specific user had a very atypical situation that caused this. 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.
-
|
Another situation I've seen this error come up is when people have been upgrading to Synthesis |
Beta Was this translation helpful? Give feedback.
-
|
I was experiencing this problem using dotnet9.0 with MO2, I had to remove the temp folder and the whole synthesis installation to make it work again. Based on #521 I tried to switch to dotnet8 by the global.json method (and installing it of course) and the problems seems to have gone away |
Beta Was this translation helpful? Give feedback.
-
|
I get this pretty much every time i launch synthesis, fixing it just requires me to paste in (and replace) the synthesis zip over my current synthesis install then restart mo2 |
Beta Was this translation helpful? Give feedback.
-
|
I have tried using version 0.34.0-pre-release3, and while it does not get rid of the access denied errors, they do occur less often. Adding the global.conf file to use dotnet 8 instead of 9, and it seems that the issue occurs less often still., However, I noticed that there are two different access denied issues.
I'll keep trying things, and will report if I find anything new. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Synthesis either:
Beta Was this translation helpful? Give feedback.
All reactions