Hello Krita Community, i come from Discord Krita server i got advice to ask here for help. So i never had problems with Krita, until i got my new PC and re downloaded Krita. The version of Krita im using is 4.4.0 newest one, i used to use a older version on old PC. Anyway, after 2 - 3 hours, i can not save my projects anymore, instead i get a message reading out this:
“Could not save C:/Users/Admin/Desktop/Programs/RVGL/cars/xm250/cartheforce.bmp
Reason: Cannot open file for writing. Reason: The file could not be copied.”
I have been trying to find help on numerous Discord servers, including the Krita Discord one, and nothing helped. The only thing i found out is when i delete the file, (Not the Krita file, the exported file) and then try to save it, it works and it gets saved. Until 2 - 3 hours pass when the glitch suddenly comes back and does not let me save my project again.
Also, saving on other locations (example: Desktop), it works. It has to be in the folder which is written up there because it’s a texture for a model. Giving me suggestions of saving it to a other location instead of the folder where the mode is will not help, because i can not look at the model i am working on. The two must be in the same folder.
This has never happened on old Krita and my old PC. Please help. Im looking forward for advice and support. Thank you i hope you are doing well during these hard times.
Hello. Yes i tried to run Krita with Admin, it did not work. When i had old Krita on my old PC i had no problems like this, and then suddenly this new version on my new PC makes this “Glitch”. I have Admin rights on my new computer, im really confused why is this happening in the first place.
I have experienced this bug several time abefore however I can’t replicate it to make a report of it.
What I usually do is save with another name on the same location or on another top most directory in the drive I’m working on. Reopen Krita with the new file and then save over the correct file location.
This bug never happened beforehand. Listen when i do what you said another name, and same location. It works until 2- 3 hours pass and then the glitch occurs again. I already mentioned that i think, that the problem is not solved that way. And this has been only happening when i got the newest Krita, as i said before, i never had this with old Krita version.
But it has happen to me before hand, what do you want me to say? Welcome to the club?
Just changing name does not work you need to restart Krita with after the save and loading the fresh save. When the session is cursed of course it will happen again. But my suggestion is a directory closer to your working OS. External drives are a no go.
It’s on Local Disk C. I’m really not sure what are you implementing? Im pretty sure ive done that, that i have saved with a different name, and then leave and re-enter, if that is what are you saying.
Then just export everything into a exr or something and then make a new session and import everything in and delete everything you have with the old name. You will loose layer styles and blending modes but at least you will be able to save again.
Check whether https://docs.krita.org/en/KritaFAQ.html#windows-krita-cannot-save is relevant. Without access to your system, it’s impossible to be sure what’s wrong, but this is not a bug in Krita (i.e, something that can be fixed by changing Krita’s code), it’s a setup issue on your system.
I can not enter Controlled folder access. “Your Administrator has limited Access to some areas of this app, and the item you tried accessing is not available”.
When you’re trying to Export the .bmp to that folder location, are you running the RVGL application at the same time? If so, try not doing that to see if things work properly again.
Just so everyone know, i have reinstalled my PC. I have reinstalled Krita and everything. As of now is working good! If anything (Hopefully NOT), gets bad, i’ll inform you guys here. Thank you everyone here and on Discord who talked to me to fix this issue. I hope you people have a wonderful day/night. Bless you.
Next time it happens may be we can diagnose it more properly