Leigh

We've had numerous reports of this issue and it's currently logged with our developers.

Avez-vous toujours des problèmes pour réinstaller la V2 ? Si oui, veuillez fournir plus d'informations.

This should help: https://forum.affinity.serif.com/index.php?/topic/169443-fixed-saving-to-an-external-drive-gives-failed-to-save-document-error-on-macos-ventura/&do=findComment&comment=1007308

@HeyTheresTony We've been able to replicate this issue with V2 and it's logged with our developers.

Unfortunately, this is a known issue and will be fixed in the next update. If you haven't already, please contact your account manager or send email to corpsupport@serif.com we can offer you a working solution.

Thanks for the offer and if I think of anything else, I will let you know. I'm sorry that I couldn't find the cause of the issue but Windows can be a mystery sometimes

Did you use the Move app option in Apps > Apps & features or did you move the folder yourself and create your own symbolic links?

I've not forgotten about this. I've been continuing to look into this and i'm still having issues trying to move the app. I did try another MSIX app and that also had the same issue when trying to move it and gave the same error. I tried all the solutions listed here and a new user account and the same error occurred. I couldn't find much related to the error 0x80073CF6 but when I tried using Powershell to move the app, I got a more detailed error log: AppX Deployment operation failed for package SerifEuropeLtd.AffinityPhoto2_2.0.0.1640_x64__3cqzy0nppv2rt with error 0x80073CF6. The specific error text for this failure is: Authorization of capabilities for SerifEuropeLtd.AffinityPhoto2_2.0.0.1640_x64__3cqzy0nppv2rt failed with error code 0x800701C5. I've logged this with our developers to see if it's something they're aware of. If/when I get an update, I will let everyone know.

This thread is now closed/locked. This thread has been reported several times and everything that needs to be said has been said. Here's a link to the forum guidelines for anyone needing a refresher: https://forum.affinity.serif.com/index.php?/guidelines/

Not to be a killjoy or anything, but just wanted to reiterate what @T V mentions in his original post. Please make sure you backup your propcol files before overwriting them or messing with them, especially now that Affinity V2 shares content types such as Assets, Brushes, Swatches and Styles between Affinity apps. You may think you're only affecting one app but it could have a knock on effect to other apps and/or personas. Don't want to stop users sharing content to help others but also don't want users losing any data

Wir planen, MSI-Dateien wieder verfügbar zu machen. Sie können diesem Thread folgen, um über Updates zu seiner Verfügbarkeit benachrichtigt zu werden.

Okay, halte mich auf dem Laufenden 👍

Ich bin mir leider nicht sicher, was ich als nächstes vorschlagen soll. Ich denke, das Problem wird darauf zurückzuführen sein, dass Sie auf den WindowsApps-Ordner zugreifen können - dieser Ordner ist normalerweise gesperrt und für Benutzer nicht zugänglich. Wenn Sie den Inhalt dieses Ordners anzeigen können, wurden die Berechtigungen geändert. Ich habe in einem früheren Beitrag vorgeschlagen, ein neues Benutzerkonto auszuprobieren, um zu sehen, ob das funktioniert, aber Sie sagten, es sei nicht möglich. Liegt das daran, dass es sich um eine Business-Maschine handelt?

I'm sure it's something our QA team will test when they get their hands in the MSI builds. When we know more will let everyone know.

No ETA yet but it's being worked on.

We're expecting the issue saving to exFAT, FAT32 and FAT external drives to be fixed in the next update for both V1 and V2. No ETA for when that will be but hopefully not long.

Entschuldigen Sie die Verzögerung bei der Beantwortung. Haben Sie die Berechtigungen für den WindowsApp-Ordner geändert, um Zugriff zu erhalten? Das Ändern dieser Berechtigungen kann diese Art von Problemen verursachen.

☝️Sorry about that - we'll get the page rolled back. Sorry for the confusion.

Forgot to add, i'm also going to speak with our QA/Devs to see if they have any ideas.

I've been able to replicate this on a few machines using the MSIX build but then on some other machines it worked fine without error. Is your D drive a partition, VHD or another physical drive? is it internal or external and how is it connected? Sorry for the questions, just trying to find some common ground.

Thanks for letting me know. If you remember which DLLs you blocked that would be helpful

@sb101 Even when the MSI file is made available you will still need to make sure that your version of LTSC is the correct build to run our apps.

@James Webb I've not forgotten about you but as mentioned in a previous post in this thread, the apps install and run fine on a new user account on your machine. Because the MSIX and MS Store versions fail to work on your current account but work on a new account then the issue must be permissions related and unfortunately most of the other suggestions provided haven't worked for you either. I can only suggest that if you're not wanting to use a new user account, which is understandable, you should contact Microsoft to see if they can figure out what is causing the issue on your current account. Alternatively, you can temporarily use the apps on your new account until the MSI becomes available.

Even if you have access to the MSI file, you will still need to make sure that your version of LTSC is the correct build to run our apps.

I'm not sure what could be causing this error when trying to move the app as it's handled by Windows. I'm not getting much information for that error code either. How much free space do you have on D:?