Photoshop 2024 V25.4 Laggy (almost useless)

[stefan_perriard]

The newest version of Photoshop V25.4 is so laggy is almost become useless. 
Here is a comparison of Photoshop 2023 V24.1.1 which is running fine. 

All drivers are updated. 

System: 

Dell XPS 15

Win 10
x64-based PC
Intel(R) Core(TM) i7-6700HQ CPU 
RAM 16 GB
Intel(R) HD Graphics 530
NVIDIA GeForce GTX 960M 2GB

[Ged_Traynor]

@stefan_perriard the feature level of the NVIDIA GeForce GTX 960M 2GB is only 11.0, Photoshop requires a GPU with a feature level of 12.0 and above

https://helpx.adobe.com/ie/photoshop/system-requirements.html

Have you tried manually resetting your Photoshop preferences
https://helpx.adobe.com/ie/photoshop/using/preferences.html#Manually
Remember to backup your settings before doing the preference reset
https://helpx.adobe.com/ie/photoshop/using/preset-migration.html

[stefan_perriard]

Thank you for the reply! So I will never be able to run Photoshop 2024 smoothly on my machine? 

It's an odd bug as everything works, the UI is just so laggy. 

[YC377682307e54]

Yes, same here. When drawing a stroke, the response is very slow,  I totally cannot draw with that kind of interaction. Before upgrading to 2024, it was working fine in 2023. Why the higher version is not an improvement but a problem to the user??? How can I downgrade back to 2023 version? 

[Ged_Traynor]

@YC377682307e54 "How can I downgrade back to 2023 version? "

You can do that from the Creative Cloud app

[Ged_Traynor · Accepted solution]

@stefan_perriard it's not really a bug, Photoshop runs fine on my system with an RTX 3090 GPU, the GeForce GTX 960M 2GB was released in early march 2015 so it's nearly 9 years old, Photoshop system requirements have changed a lot over that period.

[HannahBanana]

This update pretty much made Duplicate image useless.  Before you could have a live feed of what you were doing in dupilicate or original image but after the update you have to swap which is tedious and defeats it's purpose.  I rolled back the update and it worked. Please fix this.