2.4.0 update killed my Windows 10 laptop

[ColchesterDave]

I updated from 2.3.1 to 2.4.0 yesterday on my Windows 10 laptop and iMac desktop, with very different results.  The iMac is turbo-charged with 2.4.0, developing a RAW (.CR2) file seems much quicker.  However, the Windows 10 experience was very different.  Select a RAW file and the image is either not displayed at all before the Develop button, or the screen is just black. When I did get the Photo Persona displayed, there was erratic behaviour; black screen for a few seconds, I could crop ok but if I selected an adjustment such as Curves, nothing was displayed in the edit box, no histogram, no default selections filled. If I tried to make any selections at that point, all that happened was a (Not Responding) in the banner.  I re-booted and tried a 'cold start' but it made no difference.

I re-installed v2.3.1 and  everything is working fine again - though I do see a prompt to update to 2.4.0.23101 on startup, but haven't made that leap yet.  I posted on the Affinity Facebook Group, where Paul Mudditt suggested I report here.  Having backed out 2.4.0, sorry I can't post any screen dumps.

My laptop is an HP Envy with 2.3GHz i5 cpu and 8GB RAM, so never really had any issues with AP and performance before.

[GarryP]

Which graphics card do you have installed and are your drivers up-to-date?

Have you tried switching Hardware Acceleration OFF in Settings/Performance?

I read something in the forums (if I am remembering it correctly) that Serif increased the range of graphics cards that the software could use Hardware Acceleration with in V2.4, and because of this, the V2.4 installation procedure checks to see if your graphics card is in this wider range and automatically switches Hardware Acceleration ON if so.

Unfortunately however, the compatibility is not 100% so some cards in this wider range still cannot be used and switching Hardware Acceleration ON has caused various problems.

[ColchesterDave]

It's the Intel R (HD) Graphics 520.  Yes. drivers are up to date.

 

[GarryP]

Thanks for the information.

Did you look at the Hardware Acceleration setting and try switching it OFF if it was ON?

(The card I’m using with the Affinity applications is the HD Graphics 530, with Hardware Acceleration ON, without problems so far, but I haven’t updated to 2.4 yet.)