Having problems installing V2-photo; OS+directX detection

[Astara]

I tried installing V2 of the photo app, and got an error message that it couldn't find a supported OS, however, I have the OS+DirectX version required.

I have Win7 SP1 w/DirectX 11 -- which seems to be what is required.  I was sent to MS, to upgrade my OS to SP1, downloaded the update -- and was told it was already installed (as I thought), and was then directed to download DirectX11 -- and also tried installing it -- and was also told it was already installed (I used DirectX11 programs nearly 10 years ago when Win 7 first came out).

So it seems there is a problem w/the V2-photo detecting both my SP level as well as my DirectX11 level.  I've never run into this before, and am wondering what could be the problem in the install detecting my OS+DirectX11 level -- especially since the MS-patches for both of these indicate they are already patched to the required (stated) level...?

 

Please help!

Thanks!

-Linda

 

[NathanC]

Hi @Astara,

The minimum OS requirement for the V2 applications is the Windows 10 May 2020 update or higher, so unfortunately it's not possible to use the apps on Windows 7, you can find the full list of minimum requirements on the tech spec page below.

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

[Return]

Sorry but version 2 only supports windows10+ and directX version 12

[Astara]

I'm not sure why the installer would claim SP1 of Win7 and DirectX 11 to be the minimums necessary.  Sigh.

 

[walt.farrell]

15 minutes ago, Astara said:

I'm not sure why the installer would claim SP1 of Win7 and DirectX 11 to be the minimums necessary.  Sigh.

 

Can you show us a screenshot of that message, and also a screenshot from File Explorer with the installer fine selected?

[Astara]

Sure ...  It pretty clearly shows Win7SP1+Dx11 as base requirements.

 

Not that it makes a difference, but it is a bit confusing.

[walt.farrell]

6 minutes ago, Astara said:

It pretty clearly shows Win7SP1+Dx11 as base requirements.

I meant the error message you get when you try to install. 

Where did you get the link to that web page? It's possible you're looking at an outdated page or one for V1.

[Astara]

From running the V2 exe and the V2 .msix binaries I just downloaded 

for 2.1.1.

 

They both have a link I'm to follow to explain the compat

issue.  ... oh, what do ya know, its still buried on my screen:

Maybe I followed the link from the wrong 2.1.1 installer? 

[walt.farrell]

Thanks. That page is definitely wrong for V2. The requirements are noted in the Affinity Store, under Technical Specs:

[Astara]

6 minutes ago, walt.farrell said:

Thanks. That page is definitely wrong for V2. The requirements are noted in the Affinity Store, under Technical Specs:

Good to know -- its definitely wrong.   *hmmmmm*

 

*Fortunately*, I was prevented from installing it.  :-)

 

FWIW, I have V1+upgrades and didn't expect a problem.

Reminds me of Photoshop disabling GPU accel if your CPU wasn't on their fixed-GPU upgrade list -- fortunately there was a way to remove the named-GPU list subbing actual features + perf so my newer GPU worked.  I understand how MS invented a tech (side-by-side) decades ago to allow compatible libs for newer HW to work side-by-side on newer OS's.  Too bad that concept seemed to fail around Win10/11 introduction time.

 

 

[Astara]

4 hours ago, Astara said:

 

Reminds me of Photoshop disabling GPU accel if your CPU wasn't on their fixed-GPU upgrade list -- fortunately there was a way to remove the named-GPU list subbing actual features + perf so my newer GPU worked.  I understand how MS invented a tech (side-by-side) decades ago to allow compatible libs for newer HW to work side-by-side on newer OS's.  Too bad that concept seemed to fail around Win10/11 introduction time.

 

 

BTW, I'm NOT saying new features in Photo.2 don't use new SW features in newer versions of the OS.  It's rather an opposite case of newer HW not supporting old SW which I found ridiculous, at best.  I do say that MS made a decision to stop providing compatibility via their own compat mechanisms, which has little to do with newer SW progs making use of the new features.  Just clarifying....