[Extremely disappointed that this installs as an "App" and not regular software program]

55 minutes ago, Mark Ingram said:

Do you have a picture of the error? 

Yeah:

[Extremely disappointed that this installs as an "App" and not regular software program]

1 minute ago, ChrisON said:

That doesn't work for DXO - you have to specify a path to the .exe. I don't want to use Affinity's raw developer because DXO has much better noise reduction and lens correction.

This is so frustrating - I intend to report this as a bug: unless someone already has? I don't really want to go down the refund path as l really do like Affinity Photo and have no desire to return to Adobe's subscription system.

Chris

 

It won't let you just put affinityphoto2.exe as the path?

[Affinity Photo v2 .exe file location]

2 minutes ago, Dan C said:

Windows preferred install method for applications going forwards is .MSIX, though we do appreciate we are slightly ahead of the curve here.

So that's a yes, it's just pseudo-DRM?

[Extremely disappointed that this installs as an "App" and not regular software program]

1 minute ago, carl123 said:

You can do that anytime from 14 days of purchase

Or you can stick around and possibly get your issue sorted like @yaywalter and @00maxx00 have

Or they can get a refund anyway, even if it's fixable.

[Affinity Photo v2 .exe file location]

24 minutes ago, Dan C said:

Our developers have been investigating this, and have confirmed the following:

Certain applications do not like using the generic %LocalAppData% path, instead please try the following:

• Affinity Photo V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\WindowsAppsAffinityPhoto2.exe
   
• Affinity Designer V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityDesigner2.exe
   
• Affinity Publisher V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityPublisher2.exe

They have also confirmed that these are 'execution alias' .exe files, and some third party applications don't yet appear to be compatible with these - unfortunately it is down to each third party app to support execution alias .exe files when launching external applications.

I hope this clears things up!

What's the reason for installing the app like this instead of in the Program Files folder like normal? Is it just meant to be pseudo-DRM?

If so, putting the onus on other apps to support execution alias files is kinda frustrating.

[Extremely disappointed that this installs as an "App" and not regular software program]

I found a solution... forget about specifying any paths, just running "affinityphoto2.exe" works.

Still rather annoying and disappointing that they've decided to go about it this way.

  

3 minutes ago, Danel said:

I have the same problem: I can't switch a raw from Faststone to affinity 2.
This is a very big problem for my workflow.
I will now advise my club not to migrate to this version until we have an exe.

Is it possible to cancel this sale and get a refund?

You can email affinityreturns@serif.com with your name and order number to initiate a refund if you'd like.

[Extremely disappointed that this installs as an "App" and not regular software program]

14 minutes ago, carl123 said:

I certainly did not have to change any permissions.

I just used that thread I linked to to get the folder name, copied it, added \photo.exe to the end and copied the entire path+exe name into HoneyView

 

If you copy the path and executable and put it in the Windows Run dialog does Photo 2 start up (if closed) for you?

It does not launch. But I know I have the path right, because if I paste it into Windows Explorer and delete "photo.exe" it goes to the right path. Can't launch it by double-clicking or right-clicking and running as admin either.

Looking at the permissions of Photo.exe, it looks like something's corrupt with the permissions as expected. Even considering the possibility that I borked the permissions when I gave myself access to the WindowsApps folder by changing the owner of the folder to Admin instead of SYSTEM, I've even now tried completely uninstalling Photo 2 and re-installing it. Still no good. I can launch the program from the taskbar and start menu, but anything else still won't work.

[Extremely disappointed that this installs as an "App" and not regular software program]

5 minutes ago, carl123 said:

I just downloaded HoneyView, configured it to open images in Photo 2 and it works fine here (Windows 11)

Great for you. Windows Apps have always been a hot mess permissions-wise, so there's probably something borked for me. I also tried pointing it at C:\Users\[MyUsername]\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe and get an error saying "The file cannot be accessed by the system" even though it looks like the permissions are in check. Also using Win 11.

 

So again... should've just been a regular windows program and we wouldn't have had any of this headache.

[Extremely disappointed that this installs as an "App" and not regular software program]

9 minutes ago, carl123 said:

Does this help (Windows)

 

Not for me, it's not. I gave myself access to the WindowsApps directory and tried pointing HoneyView to Photo 2 as its default image editor, and no dice... nothing happens when I try to send an image to the editor. Not sure why they felt the need to lock down v2 down like this, but it's really annoying... it should just install like a normal windows program that goes in the regular Program Files directory