00maxx00

This is my batch file and it works good with Faststone. 
 
APhoho2.bat

Change
start /min cmd /c affinityphoto2.exe %1
exit
to
start affinityphoto2.exe %1
exit

Serif surely has to fix these problem, but the .bat file is a very simple and effective solution. with the time it took you to write all your complaints you would have already solved the problem and be using ap2.

Yes, we will be providing MSI installers to customers who require them. This FAQ will be updated with links to MSI downloads when they become available.
Yes. These are now available
 

This news will also help some in this thread

If you use /min the cmd window runs minimised to the taskbar. The /b did nothing for me. also if you use BAT2EXE it will make an exe if the program you use will not allow the use of a bat file.


The Bat file I use
start /min cmd /c affinityphoto2.exe %1
exit

Same problem with RawTherapee. I know where the "new" exe is, I can create working shortcuts, but there's no way to export from RawTherapee to Affinity Photo v.2.

I don't understand...why should anyone use this launcher instead of the .bat file? - I'm serious.
I read this launcher will have to be updated after every serif update, while the .bat will work forever (or at least until serif doesn't change the exe in the appdata\local\microsoft\windowsapp folder) and doesn't need to mess with authorizations. 

kid? I would love to be still one 😂 
please, your and my ages are irrilevant.
crybaby.

you're just a crybaby, interested in whining and not in solving the problem.
Uninstall the sw and ask for a refund. that's easy enough?

I already wrote this problem (the export from other softwares) should be addressed by Serif. Apart from it, ap2 works fine.
you're making it just too tragical about this single problem and refuse to spend 3 seconds to create this .bat and solve it, while waiting for the official solution.
 
and please, stop calling "hack" this procedure. you have to create a .txt file, copy 2 lines of text in it and renaming it to .bat.

Serif surely has to fix these problem, but the .bat file is a very simple and effective solution. with the time it took you to write all your complaints you would have already solved the problem and be using ap2.

@Patrick Connor: Thanks for your statement!
@00maxx00: Thank you! I wrote "out of the box" and meant that this proceeding is not very intuitive!

Cheers
Ludger  
 

Hi Ludger.
If you type "*" and press enter when you are in the folder with the .bat file, you remove the filter that shows only .exe files. Then you can select the .bat file.
It's the same with FastStone Image Viewer and DXO Photolab - and every other sw that works the same way.

You post too much about your poor situation that's why you don't have enough time. It takes a few seconds to make it work. Life must be hard on you !

Stop whining and write your batch file !

C'mon @cybertec69 make a man of yourself, stop crying, blow your nose, take a deep breath and ... write your batch file.
Or just stop posting, ask for a refund, sign up with Adobe and have a nice day.

you're just a crybaby, interested in whining and not in solving the problem.
Uninstall the sw and ask for a refund. that's easy enough?

I don't think he was referring to you.

No but this does
Go to
%LocalAppData%\Microsoft\WindowsApps\
and you'll see AffinityPhoto2.exe which is the Alias(broken?) for the true executable
Generate a bat file containing
start affinityphoto2.exe %1
exit
Setup a link in Photolab like this

I found it necessary to use a helper .bat file:
start /b affinityphoto2.exe %1 exit I named mine LaunchAffinityPhoto2.bat and saved it. Then I point to that bat file from the other programs that need to invoke Photo 2.

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.