Save failed because you do not have permission to create a file in that location.

[T-roy]

FIXED!

AVAST anti-virus had blocked Affinity Photo.exe - screenshots @ end of thread

==========================================================

FAILED TO SAVE DOCUMENT

Save failed because you do not have permission to create a file in that location.

I searched this forum & google & see that several have had the same issue but no solution.

I am using version 1.10.6.1665 on Win 10 PRO 64 & have not added fonts to my PC

This happened after the most recent update.

Even if I use EXPORT, it fails

If I EXPORT + change the file name, it finally will work, but this is a huge pain in my workflow vs CTRL S

Please advise...

Edited December 23, 2022 by T-roy

[T-roy]

NOTES:

image 1 = CTRL S ~ or menu item ~ File > SAVE

image 2 = menu item ~ File > EXPORT (pop-up: file already exists - do you want to replace it) > YES > image 2 error

[walt.farrell]

Welcome to the Serif Affinity forums.

I would start by checking your Windows settings, e.g. for Controlled Folder Access. Or your anti-virus and anti-malware settings you may have set up.

[T-roy]

Thanks for the reply. 

Nothing in my "workflow" changed - except the last Affinity Update before v2

I didn't jack w/ any Windows settings or Controlled Folder Access & doubt Win10 auto-updates jacked this up.

I use Avast AV (which seem to get updated daily) so I'll try to turn off any protection on E:\ drive pics folder.

I am shocked that there has been no direct support from this company.

I hope "official support" chimes in here (do they ever?) and resolves this.
- there are lots of searches for the same exact issue - none were resolved that I've seen.

[walt.farrell]

6 minutes ago, T-roy said:

there are lots of searches for the same exact issue - none were resolved that I've seen

At least one, and I think more than that, were resolved as Controlled Folder Access or other anti-malware settings, if I remember correctly. 

And one doesn't have to have recently changed settings. The way these controls work, one could have previously white-listed an app, and then updated the app. And the update could automatically revoke the white-listing. That's why it's relevant to consider that scenario.

11 minutes ago, T-roy said:

I am shocked that there has been no direct support from this company.

 

14 minutes ago, T-roy said:

 I hope "official support" chimes in here (do they ever?) and resolves this.

I can't say whether anyone from Serif has participated in any of the threads about this, or not. But yes, they often respond. 

Right now, for your thread, the timing is unfortunate. Someone from Serif may respond, but some are already on holiday, and as you can read in the notice about the holiday closing (red bar, above) they'll be very short-staffed from tomorrow until Jan. 3.

[Ron P.]

19 minutes ago, T-roy said:

& doubt Win10 auto-updates jacked this up.

Do you know why there's the current APV1 version of 1.10.6.1665? It's due to one of MS updates jacking up AP, AD, font selection, and who knows what else it messed with. It wasn't Affinity programs that done that.

22 minutes ago, T-roy said:

use Avast AV (which seem to get updated daily) s

I've used Avast and it's freebie version AVG free. I finally seen just how they can mess up programs. I removed AVG from my system, and haven't had any of the issues I was having with Affinity programs.

23 minutes ago, T-roy said:

I hope "official support" chimes in here (do they ever?) and resolves this.

Official Support does frequent the forums. The do not always "chime in", but do reply a lot more than the some other big name software developers. There's numerous other users, like me, that are constantly on the forums. We have a good understanding of what's going on with them, and know what Serif has been recommending to either fix or work around the issues. Think of the Serif Staff like this. There's about let's say 50 of them, in a community of over 500,000. They have to go door-to-door to fix issues. How often are you going to see them, and how soon do you think they will get to your issue? Maybe your issue has already been reported and addressed? You might need to do a little researching to find it.

[T-roy]

Thanks - walt.farrell - for setting me on this path after already doinking around with admin / permissions / users, etc.

I temporarily disabled my AVAST AV & my pics saved normally!

Unfortunately, after adding my E:\ drive "pics folder" as an exception in AVAST - I still get the same error & can't save.

I tried adding an exception for the Affinity app folder & it already exists.

I also searched for "access controlled folders" but MS webpage is out of date - the options on the MS site do not exist for me.

https://support.microsoft.com/en-us/windows/allow-an-app-to-access-controlled-folders-b5b6627a-b008-2ca2-7931-7e51e912b034

I hope others will benefit from this thread as I have posted the exact error text & pop-up images.

It's not fixed yet...

[walt.farrell]

3 minutes ago, T-roy said:

It's not fixed yet...

But if disabling Avast fixed it, you know the issue is with Avast. And that's gives you another support option to investigate.

[T-roy]

4 minutes ago, Ron P. said:

Maybe your issue has already been reported and addressed? You might need to do a little researching to find it.

Thanks for the reply...

I searched & this issue has been reported repeatedly w/ no cure (noted in a previous post, but I understand - it's easy to miss.)

RE: Do you know why there's the current APV1 version of 1.10.6.1665? 

No, I guess that is why I am here... looking for solutions! 

What does APV1 stand for? I guess I don't care if it fixes this issue - the app is useless to me now.

Where can I find - APV1 version of 1.10.6.1665? 

[T-roy]

 

1 minute ago, walt.farrell said:

But if disabling Avast fixed it, you know the issue is with Avast. And that's gives you another support option to investigate.

I'd say the issue is with Photo.exe being flagged as a virus.

*That just set off my BRAIN alarm (not AVAST alarm)!

I remember a virus years ago called Photo.exe... let's look...

https://duckduckgo.com/?q=photo.exe+virus&ia=web

^^^Yeah, with that history it's no wonder AVAST flags it, but I should be able to override that.

I'll keep poking - thanks to both of you for your interest & help so far!

*Please note: my short, direct sentences are not intended to be terse, judgmental or otherwise, and I am not trying to "rain on" SERIF, but I've heard it before that I sound "mean" or (pick a word). I'm just trying to "get 'er done!"

I sincerely appreciate your input & feedback!

[T-roy]

Tightened up my search term & this seems to be a known problem (AVAST & photo.exe), but never a final follow-up from the users or support...

I'll look into it after this weekend, and will report back if I get to the bottom of this!

 

 

Edited December 23, 2022 by T-roy

[T-roy]

FIXED!

Thanks for the help guys - I needed a sounding board to get this worked out!

Ultimately - for ME & this specific error - AVAST had previously blocked Photo.exe (green highlight)

Even though I added an exception later, the BLOCK had to be removed (I think that's what was going on - note red highlight)

I wish I had used red & green in reverse, but WOOT! 

This issue is FIXED & I have work to do!

Have a great weekend & it's close enough to say - Happy New Year!

Edited December 23, 2022 by T-roy

[Ron P.]

11 hours ago, T-roy said:

What does APV1 stand for

My apologies, that's an abbreviation for Affinity Photo version 1. Version 1.10.6.1665 is the fix for MS update. I was just showing that OS (MS specifically) do break software that was otherwise working great. 

Happy to hear you got it going.

Merry Christmas & a Very Happy New Year to you too!!

[Lee Weisenburger]

I use Avast One and after disabling the app permissions within Avast relating to Affinity Photo I was able to once again save and export work to my desired file folder without an issue.

Edited September 27, 2023 by Lee Weisenburger