OpenSSL Communities

Drop legacy Windows support

Igor Ustinov PublicSeen by 97

The pull request #29585 was published on GunHub, this pull request proposes keep OpenSSL support only for Windows starting from Windows 10, i.e. drop the support of Windows XP and Windows 7.

As your representative in the Foundation TAC, I ask you to express your opinion on this proposal. Is it acceptable in 2026 not to pay attention to WinXP and Win7, or are these systems still in use and should be supported?

What should be the minimum supported Version of Windows

poll by Igor Ustinov Closed Wed 4 Feb 2026 9:00PM

Results

Zhihao Yuan

Windows 10

The products of my organization, which has been supporting Windows 7 and Windows 8.1 since I joined, has phased out that support for a while. We also have difficulty testing on Windows 10 earlier than 1511 (FYI, that version is already 10 years old).

Neil Horman

Windows 10

Based on our platform support page:

https://openssl-library.org/policies/general-supplemental/platforms/

Windows 10 is the only thing we currently support from MS anyway. There is an entry for XP on there , but it's community support and has no designated maintainer.

So we could claim support for something older than win10, but I'm not sure how we would above and beyond the lip service of saying we do.

Tim Hudson

@Neil Horman Our platform list is not a list of what works - it is a list of what we are actively (in theory) supporting. Our communities run across a much larger range of platforms than we do.

Nicola Tuveri

Windows XP

As an individual, I believe we are too late in the release process for 4.0 to gather enough feedback from the actual stakeholders affected by such change to fully assess the impact of abandoning support for windows versions below win10.

This to me seems mostly a BAC decision rather than TAC: this is about evaluating the risks of dropping support for pre-win10 against the benefits of such a move. So far I only see the potential risks and fail to grasp the expected benefits.

Geert Hendrickx

Windows 10

OpenSSL 3.5 will still be supported on older platforms.

Tim Hudson

Windows XP

There is no benefit at the moment in dropping support for older windows versions IMHO.

Our code should be able to operate on all platforms and dynamcially take advantage of later releases. Users can build their own OpenSSL version set with a different minimum release value. We can improve what we are doing in this area easily.

I don't think we should intentionally break working on older releases of one of the most widely used platforms - different if it was something odd.

Neil Horman

@Tim Hudson I respectfully disagree here. Not specifically with the cost/benefit assertion of keeping support for older windows versions where feasible, but rather with the assertion that we truly support it at all, in any meaningful way (be that an official support statement or simply a community "you should be able to get it working" statement)

By way of evidence, I went and setup a virtual machine running windows xp and Visual studio 2010 (the latest version that ran on winxp, obtaining both of which required downloads from the internet archive, which is neither here nor there, but is somewhat amusing).

I built our various stable branches, starting at 3.0, up to 3.6. Every branch, except for openssl-3.5 fails to build, due to the use of windows or other header files that don't exist on windows xp. For the openssl-3.5 branch, which happens to have landed on a state of the source tree that does build, every single unit test segfaults when running the test suite (I didn't dig into the root cause of why there), though I think it further speaks to the lack of any meaningful support on this platform.

What that implies to me is two things:

1) That every change we make is assumed to not impact this platform (or more specifically we're not really worried about the impact we may have here)

2) Since the release of at least 3.0, users of Windows XP (a) havent noticed this breakage or (b) have been toiling on their own to keep it functional

If (2)(a) is true, then that suggests that windows xp developers aren't actually using our more recent code, in which case this becomes more of question of whether we need to keep what is already broken code around.

If (2)(b) is true (which may well be the more likely scenario), those individuals are operating in an environment in which they already know they need to maintain a pile of code on their own. There can't be an expectation on those developers part that we will do anything to make that task easier, unless, they get involved with the community to call out their need for that assistance. Without that, any statement of support (be it official, or just "yeah, it should work" isn't particularly meaningful).

To your points below, yes, aws-lc, rust, etc maintain function on older windows releases, which is great. But they're taking on the required responsibility of being able to assert that support by running the appropriate ci jobs to ensure continued function in those environments. In the absence of a community support volunteer to ensure that this platform remains viable, any statement of support is really just saying "it works...maybe", which isn't really helpful to anyone.

We could of course be our own community volunteer and commit to that work on our own. I'd in fact be supportive of such a move if the consensus was that we believe that there is sufficient need in the community for it.

Perhaps that's a better way to couch this question. Instead of "Do we want to get rid of windows xp support?" we should instead be asking "is there sufficient need to support this platform that we are willing to to ensure its viability?" Without making that commitment, any statement of support (no matter how weak/loose) just isn't really true.

Sasha Nedvedicky

@Tim Hudson see my detailed answer further below. my preference here is to change the default value we use for _WIN32_WINNT to 0x0A00 so default build settings will require Windows 10 or later. People who need OpenSSL for older version should be using their own compile time settings.

Richard Levitte (individual)

@sashan, point is, there's a reference to #29585, and in that PR, you do much more than merely update the default value.

Do you mean to say that this vote is only about this default value, or does it still imply the removal of code in that PR?

Sasha Nedvedicky

@Richard Levitte (individual) I would contrain this vote about changing the default for _WIN32_WINNT: what windows version the default build options should support.The PR is draft and will be updated once decision will be made.

Matthias Kraft

Windows 10

May I remind everyone that even Windows 10 is already out of support. OpenSSL 3.5 still accommodates this legacy stack, and as an LTS release it will remain available for a while. This provides a window of opportunity to finally move away from these operating systems. At this point, absolutely nothing should be running on these Windows versions in any networked environment. Not even air‑gapped.

This is, of course, my personal opinion.

Maikel Mardjan

Windows 10

From a security and maintenance point of view: I can not think of a valid reason that someone still should support MSWindows <10 versions. Migration should be done for companies/people still using such an old MS platform.

Santosh Pandit

Windows 10

Active encouragement to users to move to Windows 11 and we should support until they do so.

Tim Hogard

Windows XP

XP is still widely used in medical imagining and a number of other industries and that will never change because they have to replace million dollar machines. Newer systems have other tls packages that are updated and current.

Armin Fuerst

Windows 10

I assume it would cause additional effort to continue supporting older versions. As they are not officially supported anymore, they should not be in use anymore (or at least not publically available). For "private" instances, existing versions of OpenSSL still word.

In my opinion it makes more sense to put the effort in keeping OpenSSL maintainable and keeping cryptography up to date.

Andreas Bank

Windows 10

Only worth focusing on (freely) supported software. Testing (ang giving garantees) more than one Windows platform costs a lot.

Tim Hudson

And for a topical post - AWS-LC on Windows 7 - code about to go in to make sure it works. See https://github.com/aws/aws-lc/issues/1997

There is also a PR for the change. And commentary around it.

And Rust when updating OS PRNG usage code ensured that Windows 7 still works.

https://github.com/rust-lang/rust/pull/121337

And if you want a set of platform definitions to look at and a set of tiers that make it clearer the sort of platforms still in widespread use:

https://doc.rust-lang.org/beta/rustc/platform-support.html

The Rust platform policy is also nicely written IMHO.

https://doc.rust-lang.org/beta/rustc/target-tier-policy.html

I mention these mostly for some broader context.

Sasha Nedvedicky

There are at least two details that need to be taken into account:

  • minimal required version where OpenSSL library and tools will be running (a,k.a. runtime)

  • minimal required version for MSVC (compiler and tools) required to build OpenSSL source code

the runtime requirement is controlled by _WIN32_WINNT macro which is explained here. OpenSSL currently uses value 0x0501, which constrains resulting binary to WinXP APIs. Anyone can change (override) default value defined by OpenSSL at build time by passing option '-D_WIN32_WINNT=0x0A00` to `Configure` command. Doing this changes minimal required version where OpenSSL binaries will run to Windows 10. The only difference I'm aware of in OpenSSL is that library uses `BCryptGenRandom()` in ossl_pool_acquire_entropy() (see: providers/implementations/rands/seeding/rand_win.c). So my personal preference here is to just change OpenSSL default for _WIN32_WINNT to 0x0A00 so default build settings produce OpenSSL library Windows 10 and later. The users who wish to procude OpenSSL library which will run on older Windows than 10 will have to use -D_WIN32_WINNT=... with desired value at build time to obtain OpenSSL suitable for older versions. Keeping code which allows OpenSSL run on older windows costs OpenSSL nothing it can stay. I would just change the default value.

The Microsoft Visual Studio tool chain version is determined by macro _MSC_VER macro. It can be used to restrict minimal Visual Studio required to build OpenSSL sources. Given OpenSSL has moved from ANSI-C to C-99 I feel the project should consider to move minimal Microsoft Visual Studio compiler to more recent version. My persnal preference is to require Visual Studio 2017 (_MSC_VER >= 1911) My only reason is that we can expect more modern C99 language features to gradually sneak in to OpenSSL-4.0 and I'm just concerned it may caught older tools in surprise. hnece I prefer to be honest upfront saying your tool must be _MSC_VER at least 1911. Whether to keep or drop code for branches we have for older studio version is yet another question.

given the question is wher WinXP should be supported, then I think yes it should but not as a default compile time settings.

Tim Hudson

Our code should dynamically detect the runtime version and use the latest RNG stuff available. Then this is a "non-issue" and a better result. There are three interfaces in recommended order - and by default we use only the oldest. Making it runtime check is the right outcome - but we haven't yet done that.

Moving forward Visual Studio versions is a major issue - like the OS - and we aren't planning to use any C99 features that aren't widespread - so I would be seriously hesitant to leap forward. I have active customers from Visual Studio 2005 up to Visual Studio 2026 (and there are reasons of course for each customer to decide at what point in the Visual Studio series they are stuck. VS 2010 started C99 features. VS2019 is mostly complete. So we have already basically orphaned older VS compiler users for OpenSSL 4.0.

https://learn.microsoft.com/en-us/cpp/overview/visual-cpp-language-conformance?view=msvc-170 is the "official" reference for that.

Sasha Nedvedicky

@Tim Hudson I agree runtime detection is better option.

Speaking of Visual Studio version, I wonder why people are stuck on old tool to build OpenSSL. Is it because Visual Studio (let's say 2017) produces code which is so much different to output from VS 2005? It feels like people are relying on some feature/bug in VS 2005. I'm just being curious here.

Shubham Kumar

IMO, OpenSSL should shift to Windows 10 as the default and remove support for Windows XP/7. As mentioned by @Neil Horman , builds are already failing (from 3.0 to 3.6, except for 3.5, which itself shows segmentation faults in all test cases, note: reasons unknown). If the intent is to keep supporting these legacy systems, then proper support should be added and tested against them. However, doing so without knowing the actual user base does not seem reasonable, especially considering there have been no concerns raised on github or other platforms (not 100% sure, please mention if someone has) regarding issues or errors on Windows XP/7 systems related to OpenSSL 3.x releases.

If there are users still relying on these legacy systems, they are likely either using very old OpenSSL LTS versions or maintaining their own downstream changes. In either case, it does not make much sense for OpenSSL to continue supporting them upstream.

Second, I also agree with @Nicola Tuveri that making a decision on this matter is quite late for the 4.0 release, and I believe this idea should instead be considered as part of a subsequent release.

Sasha Nedvedicky

I'm going to close the PR/draft so windows bits are kept as they are now. I don't feel strongly about the change, I just saw upcoming 4.0 release as opportunity to make those changes as I feel changes like this should be landing to major release only.

Also quick look at poll shows there is no strong desire to change that currently 33 out of 123 people participated in poll.

Viktor Dukhovni

I am not going to make a specific choice, because I haven't built any code for Windows for quite some time now, and haven't looked at what it takes to support Windows in general, or any specific version of Windows in OpenSSL. So any choice I'd make would be entirely uninformed.

That said, if there's a cutoff at which:

  • We'd be able to shed a substantial body of code or build complexity

  • The abandoned versions are unsupported by Microsoft and by open-source projects that use OpenSSL.

Then I'd be inclined to support that cutoff.