Access to the path '...' is denied

[Noggog]

Synthesis either:

• Shows the "Nuget Config Issue", and in the logs says "Access to the path '...toolpath.sentinel' is denied"
• Blocking errors, with verbage like "access to path ... is denied"

[Noggog]

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

[Wabbajack-appreciator]

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.

[Noggog]

You can avoid losing your list of patchers if you hang on to the PipelineSettings.json and GuiSettings.json files next to the exe

[Noggog]

Of note, the setting that seems to cause issues that WJ authors often have set is DotNetPathOverride. You should be able to remove this setting from the PipelineSettings.json.

[Noggog]

Another situation I've seen this error come up is when people have been upgrading to Synthesis 0.33. I've seen a few reports of Access Denied errors. But most people say that reinstalling synthesis helped them. So I'm not sure if they aren't copying all the files in properly from the new release or what. But one thing to try is nuking all the files (except your GuiSettings.json, PipelineSettings.json and /Data folder that have all your settings) and then applying the fresh release into the cleaned folder.

[agusmor]

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

[Noggog]

Alright, I'm putting some chatter out into the Mo2 space to see if they've got any insight into the %temp% directory. I'd -like- to keep it there if we can.. so just doing some research first

[agusmor]

Yeah way less messy keeping it on %temp%. If you need any more testing just hit me up

[Noggog]

I've done some testing myself. On current 0.33, I see the access is denied errors as you've been seeing. It does seem the CEF disabling in 0.34.0-pre-release2 seems to do the trick for me. Even building into %temp% /w a DotNet9 patcher (I've just been using StringLocalizationTester) doesn't trigger any access denied errors for me yet.

I'm going to push the CEF update for now. But we can continue doing further experiments

[Noggog]

Let me know if you're still having issues. I might clean this discussion up, as it devolved into an issue report of sorts, and won't be useful for newcomers using the latest versions of the UI

[FelesNoctis]

I can confirm that I was still experiencing this issue with the most recent update and dotnet9. Installing dotnet8 and adding the appropriate global.json to the Synthesis folder appears to have resolved the problem.

[TwistedModding]

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

[Noggog]

Are you certain you need to replace the entire synthesis zip? I would think restarting mo2 would be enough?

[agusmor]

Try running it with dotnet8.
You can add a file called global.json in the same folder as Synthesis.exe with the following:

{
  "sdk": {
    "version": "8.0.300",
    "rollForward": "latestFeature"
  }
}

This will force the program to run on dotnet8 (which you would also need to install). This fixed it for me
You could also uninstall dotnet9 and install dotnet8

[sysdmp]

my testing also confirms that it works perfectly on net.sdk8 but starts showing "access denied" behavior on 9.
thing is, I need 9 for spiggit (otherwise it does not install libraries properly, known)
so I guess manually pinning to 8 is one way to solve it.
could this be related to this? #521

[agusmor]

Check the thread above and the pre releases. The pre-release2 forces #521 fix on every patcher (or so I understood) and pre-release3 moves the working dir outside of %temp%, which actually fixed it for me!
You could also check if the latest full release works for you when changing the %temp% user dir, which is effectively the same I think

[walkswithwolf]

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.

1. the error occurs when synthesis is trying to check/update the patcher github files, errors out right away, or
2. the error occurs when synthesis tries to compile the patcher (checking runability I believe), patcher will have the grey dot and then turnred with the error. Also notice that this instance also leaves a Loading folder in the working temp folder.

I'll keep trying things, and will report if I find anything new.

[sysdmp]

same observation (0.34.0)
errors still happen, but less often (both SDKs 8 and 9 installed).
however I do not use global.json yet.

[Noggog]

@walkswithwolf while running 0.34.0-pre-release3 (which is special, as it's a test release that moves the workspace location entirely)
What is the exact path being denied access in your logs?