Rani Sofya Posted October 19, 2019 Share Posted October 19, 2019 So I pretty much tried reinstalling affinity, clearing, reinstalling windows, updating windows, everything... Affinity photos and designer both give me this error when I try to save or export something. I'm on windows 10, 16G RAM, 500G SSD (33G free space), Intel 17-8550U CPU, and a GeForce graphics card Quote Link to comment Share on other sites More sharing options...
HVDB Photography Posted October 19, 2019 Share Posted October 19, 2019 This may help ... ! Quote Affinity Photo 2.3.1 Laptop MSI Prestige PS42 Windows 11 Home 23H2 (Build 22631.3007) - Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz 2.00 GHz - RAM 16,0 GB Link to comment Share on other sites More sharing options...
Rani Sofya Posted October 19, 2019 Author Share Posted October 19, 2019 Hey HVDB, I looked at that post and I uninstalled a few things, now I have 73GB free on my SSD and it still won't work, I don't use an external driver. Quote Link to comment Share on other sites More sharing options...
dutchshader Posted October 19, 2019 Share Posted October 19, 2019 Can you save the file to desktop? Quote intel core i5, 16GB 128Gb ssd win10 Pro Huion new 1060plus. philips 272p 2560x1440px on intel HD2500 onboard graphics Razer Tartarus Chroma Link to comment Share on other sites More sharing options...
walt.farrell Posted October 19, 2019 Share Posted October 19, 2019 That error message is often a symptom of having Controlled Folder Access enabled in Windows when you have not told Windows to allow the Affinity applications to save to those output folders. See this thread for more some more information. Rani Sofya 1 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
Rani Sofya Posted October 20, 2019 Author Share Posted October 20, 2019 Thanks, Walt! That worked perfectly! for those who can't find it, you can just search up "Controlled Folder Access" on windows and turn it off or give access to affinity, I just turned mine off. Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted October 20, 2019 Share Posted October 20, 2019 Glad to hear it worked, Rani. Thanks for letting us know. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
Pšenda Posted October 20, 2019 Share Posted October 20, 2019 2 hours ago, Rani Sofya said: "Controlled Folder Access" However, Windows must have told you, that they have not written to the protected folder! Quote Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301 Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130. Link to comment Share on other sites More sharing options...
walt.farrell Posted October 20, 2019 Share Posted October 20, 2019 12 minutes ago, Pšenda said: However, Windows must have told you, that they have not written to the protected folder! You would think so, but evidently if that's happening it's subtle enough that several users have missed it. I would also think that some action taken by the Affinity application failed (perhaps something to create an empty file in the output folder) but the developers assumed it could not fail and didn't check the return code. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.