P: Allow CPUs without AVX2 to install Adobe Products

Well with this avx2 issue. I am dead in the water in upgrading beyond 14.0 nor can I update Bridge or Photoshop. Without spending 1500.00 on a new pc

This discussion also applies to the new version of Photoshop 26.1

It seems Adobe have issued these updates and I am unable to take advantage of due to the computer I had them installed on being an older machine (but is perfectly adequate for everything else I want to use it for) and I have no intention of spending hundreds of pounds needlesly to upgrade it.

So, Adobe, can you tell me exactly why I should need to continue spending my subscription fee on 2 peices of software that will no longer be supported or updated? 

I'd really like someone from Adobe to tell me what my options are? Do I cancel my monthly subscription that I have been paying loyally for so many years?

@DexterGordon: "it's a very far-fetched explanation"

You've apparently never managed product teams in a large corporation and have a naive understanding of the inherent issues.

The LR team clearly wasn't aware of the "dynamiclinkmediaserver.exe" restriction at the time they released LR 14, which has left many customers confused and frustrated (see here and here).  (Only a true conspiracist would think the LR team deliberately released LR 14 with those bugs and consciously didn't alert its customers.)

Why didn't the video team notify the LR team prior to the LR 14 release? Maybe the restriction is a typo, and the video team didn't become aware of it until after the October release. Maybe the restriction is intentional -- that you can apparently remove the restriction by editing a file isn't dispositive, since there may well be resulting bugs that you're unaware of.  Maybe the video team did alert other Adobe product teams but in a poorly written email the LR product manager missed. Maybe the video team had incorporated a new version of a third-party library and only became aware of that library's restriction after the October releases. Maybe the library was incorporated by a lower-level engineer who didn't understand the implications of dropping AVX support, and those implications only became clear after customer complaints started coming in. Maybe the video team's QA doesn't include 11-year-old CPUs. Maybe the LR product manager complained up the management chain, perhaps with data showing they'd lose x% of annual revenue by dropping support for 11-year-old CPUs, and maybe the video manager pushed back, observing that if they backed out the intentional change, they wouldn't be able to meet their own team's goals of improving performance without spending y man-months of higher-quality engineering effort, deferring the other important goals. And maybe the upper-level manager decided in favor of the video team.

I have no inside information, and this is all speculation, but educated speculation that anyone who has worked in a large company is all too familiar with.  These sorts of issues aren't uncommon. Business-school academics and gurus have for decades studied the management problems of large companies and written dozens of books about it.

You are having the same discussion here as in the Photoshop forum. Current software requires current technologies and therefore correspondingly current and powerful hardware.

Even if you don't want to admit it.

"Hanlon’s Razor states: never attribute to malice that which can be adequately explained by neglect, ignorance or incompetence."

In LR 14.0, people with older CPUs were having problems importing from folders containing videos. Some evidence pointed at the component "dynamiclinkmediaserver.exe", which LR and other Adobe apps use for displaying video. According to posts in that thread, this newer version required AVX2 instructions. So it appears that rather than reverting that component back to not requiring AVX2 instructions, the LR team changed the system requirements for LR Classic.

I believe that a different team in Adobe maintains "dynamiclinkmediaserver.exe". It appears that the LR team was unaware that the new version of that component included in LR 14 required AVX2 instructions.

It most likely would be technically straightforward for "dynamiclinkmediaserver.exe" to continue to work on AVX CPUs while taking advantage of AVX2 if present.   Based on my decades of managing software teams, I know how hard it can be in larger companies to coordinate such issues across organizational boundaries and get informed decisions that best meet the overall needs of the company. So perhaps the LR team took the expedient route and jettisoned support for older CPUs rather than trying to win the organizational battle.

(I'm not justifying any of this, just trying to provide more context.)