crash installing 2.0.4.1701 on windows 7

[THM]

Using WIndows 7 Home Premium with Service Pack 1
64 bit intel CPU with 16 GByte

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    Photo.exe
  Application Version:    2.0.4.1701
  Application Timestamp:    63ceb04f
  Fault Module Name:    KERNELBASE.dll
  Fault Module Version:    6.1.7601.23796
  Fault Module Timestamp:    59029714
  Exception Code:    e0434352
  Exception Offset:    000000000001a06d
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    1033
  Additional Information 1:    7ccb
  Additional Information 2:    7ccb2fa98342573c8a26d5624a3b51e6
  Additional Information 3:    8407
  Additional Information 4:    8407511ff5a00abf3e482bbf0d4b692e

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Could not install .net 4.8.1 because it said it was incompatible with windows 7.  Installed 4.8 instead.

Any suggestions ?

[Dan C]

Hi @THM,

Welcome to the Affinity Forums & sorry to hear you're having trouble!

On 2/13/2023 at 10:43 PM, THM said:

Using WIndows 7

Unfortunately, as can be seen in the below link under the 'Windows' section, Affinity Photo V2 requires Windows 10 or higher to be compatible -

https://affinity.serif.com/photo/full-feature-list/

I am however surprised this is crashing, rather than informing you that the OS version is incompatible, so I will be informing our development team regarding this now to better inform users of this in the future.

I hope this clears things up

[THM]

Thanks for pointing out my oversight. A check during installation would be appreciated.  It appeared to install properly and did not crash until I tried to run it.

[Dan C]

No problem at all,

On 3/1/2023 at 5:14 AM, THM said:

A check during installation would be appreciated.  It appeared to install properly and did not crash until I tried to run it.

I can confirm this is logged as a bug with our development team as it absolutely should inform you of this, before installing - our apologies!