Hello @XhoXho_art777, and welcome to the forum!
Can you please try these 2 things:
- Please save the file to your desktop,
- and remove the dot at the beginning of the file name.
The issue I see is that you are working on a file that once back in time crashed, and you missed saving the crash-restore file to a standard user folder.
If this does not work, then please report back and tell us briefly what you did so far. And please tell us the version of Krita you use and from where you have downloaded it. Additionally, tell us which version of Windows you use.
Michelist
Add/Edit: Please also try to save the file with a different name, maybe âXhoXho_art777âs picture.kraâ or something else.
Welcome to the forum, @XhoXho_art777.
I agree with @Michelist. You should not be saving to that location and your file name should not include âautosave.â
Did you start Krita as Administrator at some point? Because it looks like Krita doesnât have the permission to do its autosave anymore. If youâre afraid of loosing your file you can try using the âsave asâ or âexportâ options from the file menu to save another copy in kra format then open that copy but donât start Krita as Administrator again, it will mess up file permissions.
The filename and location shown in the error message is the standard file name pattern and location for autosaving when a document has not previously been saved as a named .kra file.
i.e. make a new image and do painting in it. After the autosave interval, the autosave file will be saved there and after a crash then krita will offer to recover it from there.
It should be possible for krita to write the autosave file to that location. Mine does.
It may be a permissions confusion situation as noted by @Takiro, above.
Only when working as admin, that was the reason for me to hint:
When working using a standard user, Krita saves in that usersâ realm, not into an admin account, that is not reachable for a standard user.
Michelist
Are we talking about running in an account that has Administrator status (usually the first user created) versus running in an account for an âordinaryâ other user?
Or is this about right-click â Run as Administrator?
Krita had admin rights while it crashed, if started via RunAs or in an admin account should make no difference.
Michelist
âRun as Administratorâ form the context menu will elevate the account for that application only. It will still use the user directory but the permissions will be of an administrator. At least on windows 8 or newer.
Being actually logged in as Administrator will use the directories of that user which doesnât happen here as the path doesnât contain the admin users home directory.
I need to create another account on my Windows 11 machine to try this.
It would be useful to wait for @XhoXho_art777 to tell us exactly what they were doing.
I figured it out! My windows needed to be updated and then it went back to functioning correctly
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
