I am having problem with using an alternate resource folder on Windows 11.
On Windows 10 it is working fine but on Windows 11 it looks like krita is writing files in the correct folder when creating new Template or installing plugin but it dosn’t find the folder when trying to use the Template and even if the plugin is correctly installed and activated it is not found. I am using version 5.2.9
Because it works with Krita on a Windows 10 machine, I am so bold as to claim that this action fails for you on a Windows 11 machine “because Windows 11 is trying to be artificially intelligent”. Or in other words, here Microsoft is once again trying to be smarter than its customers, it is not acceptable (i.e. not for Microsoft) that the customer tells Windows what to do and how to do it! Since you are using the same Krita twice, so nothing has changed on Krita, the problem must lie elsewhere. And what has changed on your side? Windows!
Of course, I have no proof that it is as I claim. But I’m nearly sure that I’m right.
But there is a simple way for a clean separation of more than one Krita version using Windows: Create a second, third, fourth user account for every additional Krita installation you want to use. That is the way I’m using since the beginning of time (or something like that) and it works like a charm, you are even able to run these versions simultaneously without any issues, here you can see 7 different versions of Krita running simultaneously on my machine:
and this is the posting where I initially presented this:
Michelist
Or did I misunderstand you, and you are using only one version of Krita with two different resource folders?
Michelist
Add: You didn’t forget to restart Krita after switching to the other resource folder and before installing new resources like this plugin, did you?
I have this setting on windows 10 working perfectly fine where I am using Krita 4.8 using the default folder “krita” and the newer Krita 5.+ using an alternative folder “krita5” to keep both version separate.
Here on windows 11 it working partialy only for the template and the plugin.
I remember at the begining of version 5 there was similar issue (see)
1 Like