"Processing cannot run because it could not create a folder to store your settings" on Windows 10

[benfry]

Having sorted out the JNA issues in #3800, we now need to get a settings folder that's safe to use on a clean install of Windows 10.

[benfry]

@B3040 can you try this version?
http://download.processing.org/processing-150920b-windows64.zip

It should provide a better error message about what's going on, including the path that it's trying to write to, which should tell us why it's failing.

[B3040]

here is the path:

[benfry]

Ok, so that looks entirely correct. What happens if you go to that folder (AppData > Roaming) and try to create a folder named "Processing"?

[benfry]

Nevermind that, posting an alternate version. One second...

[benfry]

Here we go: http://download.processing.org/processing-150920c-windows64.zip

And if this doesn't work, please check the path that's seen in that dialog box (Users > herbe > AppData > Roaming). The AppData folder is hidden, so you may have to type it in at the top of the Windows Explorer window.

[B3040]

I created that folder,

and the result is:

[benfry]

Are you running Processing as a different user? This is really odd... Or is the "Roaming" folder owned by another user than you?

[B3040]

no, there are 2 accounts on this machine: my microsoft account and my local account, and for both I have administor rights. Currently I am using the microsoft account.
Does this info help you?

[benfry]

Yeah, so for some reason, you don't have write (or full control) access to your own "Roaming" folder. For instance, this is what it looks like on my Windows 10 installation:

[benfry]

I've seen one report that installing Acrobat might cause this, but I'm not finding much definitive.

[B3040]

Now I have changed the setting for Roaming as such:

Looks that OK? Do you need additional info?
Nevertheless, processing-150920c-windows64 delivers:

Yes, I installed Adobe Acrobat X Pro and Distiller X.

[benfry]

Ok, I've added more code for this to appear in 3.0 beta 7 that'll try to find an alternate workaround and give a better error message about permissions, but that's as far as we can go to fix this issue.

[B3040]

OK, let's hope the best for 3.0 beta 7.
And meanwhile many thanks again for the great work you have done so far.

[benfry]

Fingers crossed! Appreciate your help in tracking this down.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.