Visual Studio 2026 and Windows 7

[jpsdr]

BIG WARNING
Redistributable of Visual Studio 2026 (versions 14.50 and up) doesn't install on Windows 7, there is a message saying it needs at least Windows 10.

I didn't check, but it's possible in that case that programs/DLL build with Visual Studio 2026 will not work on Windows 7.

We are far away talking about XP builds... :D

[tormento]

BIG WARNINGRedistributable of Visual Studio 2026 (versions 14.50 and up) doesn't install on Windows 7, there is a message saying it needs at least Windows 10.
AFAIK the same happens with latest Intel runtimes too.

[Cary Knoop]

I’m genuinely puzzled by these warnings. On true “don’t-touch” legacy systems you would never install the Visual Studio 2026 redistributables in the first place—doing so defeats the entire point of keeping the environment frozen.

And outside of those special cases, running a completely obsolete OS from 2009 is simply not a good idea. If someone is trying to install a brand-new MSVC runtime on Windows 7, they’re no longer treating it as a fixed legacy system, and they might as well move to a supported OS.

[GeoffreyA]

We are far away talking about XP builds... :D

Luckily, they've not removed XP targeting from VS2026 yet.

[DTL]

running a completely obsolete OS from 2009 is simply not a good idea.

But we not get any better new CPUs from 2009 to switch to new better OS for these CPUs. Win7 still support AVX512 if someone already uses such CPUs. Industry is in very slow development after 2009 and only Microsoft attempt to sell new and poorly designed interface. I not like interface design on Win10 and later. Also not like to turn off if possible all new features like everyday updates and something constantly changing here and there.
If user do not uses hybrid partially working with different instructions sets new consumer CPUs from intel with special threads planner required from OS - we can still run old OS. The professional CPUs from intel are all flat and do not need such special hacks.

Our AVS(+) core and filter design are still really at the era of single core CPUs of the beginning of 200x before massive multi-coring and multi-threading started for better performance. It even not uses good enough of the multithreading from Windows NT 4 or previous.

AVS+ core and most filters do not uses new features only present in new Microsoft API like DirectX 12 (12.x ?) from Win10 and later.

[jpsdr]

Made a new Windows 7 AVS+ build on my github.

[StainlessS]

One small observation (And my personal preference),
If you want an executable to work across all windows platforms,
Install XP (cant remember off hand any particular one, bit pissed right now),
MSDN document type stuff, and only use those (XP docs and functions),
newer Windows docs and functions may well be more sensible to use on induividualy projects,
BUT, using the older perhaps not quite so 'easy' or 'modern' interface aint that much more difficult,
use the old docs/functions, and your project will work on all OS versions since then.

Edit: You dont have to output multiple versions of an exectable, they all work just fine across the board.
(From XP, way into the future, assuming windows continues much into the future )

[GeoffreyA]

One small observation (And my personal preference),
If you want an executable to work across all windows platforms,
Install XP (cant remember off hand any particular one, bit pissed right now),
MSDN document type stuff, and only use those (XP docs and functions),
newer Windows docs and functions may well be more sensible to use on induividualy projects,
BUT, using the older perhaps not quite so 'easy' or 'modern' interface aint that much more difficult,
use the old docs/functions, and your project will work on all OS versions since then.

Edit: You dont have to output multiple versions of an exectable, they all work just fine across the board.
(From XP, way into the future, assuming windows continues much into the future )

That's what I used to do. I remained on VS 6.0 till 2021, and stuck to functions/APIs in that MSDN documentation, so 98/NT4-era specification. I'm using VS2026 now, and 2019 and 2022 before that, but am hesitant to touch newer functions. The other day I learnt that Microsoft broke GetVersionEx() on purpose to force deprecation; it returns 6.2 even on 10.

[clsid]

That function works totally fine if your application has a manifest that signals compatibility with W10/11. It is mentioned in its documentation.

[GeoffreyA]

It's good to know, thanks, though I think the older behaviour was better and simpler.

[Z2697]

That's why we need AI to write code nowadays :devil:
(Or "they", because I haven't)

[GeoffreyA]

If K2 is being AI coded, Windows is dead meat :-)