Skip to content

Planning for .NET 12 and Upcoming Hardware Requirements

This blog is a bit different than what we usually post. It contains a lot of technical information and jargon, which we generally try to avoid, but it’s important that we relay the information to you as it will have some far-reaching implications as we all plan for the future.

Towards the end of 2027 we plan to begin transitioning SmarterMail, SmarterTrack, SmarterStats and the SpamFoo Client to .NET 12. Microsoft recently announced .NET 11, but we’re going to skip upgrading to it, instead focusing on .NET 12 which will come later next year. This is because both .NET 11 and .NET 12 have updated minimum hardware requirements for x86 / x64 and Arm64 architectures. These new requirements “improve performance and reduce maintenance complexity.” By waiting for .NET 12, we're giving customers about a year to check their hardware to make sure it conforms to the new requirements, and upgrade if needed.

It’s worth noting that most customers on recent server hardware or current cloud instance families should already meet the upcoming minimums. The systems most likely to need attention are older physical servers, long-lived cloud instances and virtual machines configured to present an older CPU so they can move between hosts. If you run our software on your own servers, in a virtual machine or through a hosting provider, now is a good time to find out what processor your server uses, and plan your upgrades as needed.

Now comes the technical discussion.

The processor requirement

In .NET 11, Microsoft raised the minimum for x86 and x64 processors from x86-64-v1 to x86-64-v2. That level adds SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT and CX16 to the older baseline, and .NET won't run on hardware that lacks them. (Microsoft's hardware requirements notice shows the error you'd see: "The current CPU is missing one or more of the baseline instruction sets.")

We're using x86-64-v2 as the planning minimum for our .NET 12 releases, and we'll confirm the final processor and operating system requirements for each product before rollout. In practical terms, a server that runs the current release without trouble today could still fail to start the upgraded product.

Processors below the minimum

These are common examples of processors that won't meet the requirement. The years are approximate introduction dates for the examples listed.

Vendor Processor families and examples Approximate era
IntelCore 2 Duo and Core 2 Quad, including the E8400, Q6600 and Q95502006 to 2010
IntelCore 2-era Xeon server processors, including the Xeon E5410 and E54302007 to 2008
IntelOlder Pentium and Celeron models based on Core 2-era designs, including the Pentium E5800 and Celeron E3400Late 2000s to early 2010s
IntelEarly Atom designs, including the D525 and N28002010 to 2011
AMDK8 and K10-era processors, including Athlon 64, Phenom, Phenom II, Athlon II and older Opterons such as the 6100 seriesMid-2000s to early 2010s
AMDBobcat-based E-series and C-series APUs, including the E-350 and C-502011

Age alone isn’t a deciding factor, however. Nehalem-based Xeons and first-generation Core i7 processors meet the baseline, and so do Sandy Bridge Xeons. On the AMD side, some older processors advertise SSE4a, which is a separate instruction set from the required SSE4.1 and SSE4.2. What counts is the exact model, or the features your VM actually exposes. You can look up an Intel model in Intel's product specifications, and the GCC x86 options reference lists the instruction sets each processor family supports.

How to check a server

Check from inside the environment where our software runs. A VM or container can expose fewer CPU features than the physical host has, so the host's spec sheet isn't enough.

On Linux with glibc 2.33 or later, run /lib64/ld-linux-x86-64.so.2 --help and look for "x86-64-v2 (supported, searched)" near the end of the output. You can also check /proc/cpuinfo for the ssse3, sse4_1, sse4_2, popcnt and cx16 flags (Linux lists SSE3 as pni).

On Windows, run Microsoft's Sysinternals Coreinfo with the -f switch. Supported features are marked with an asterisk, so look for one next to SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT and CX16.

If your hosting provider manages the host, ask them to confirm x86-64-v2 support for your server or instance type.

Older hardware is a security question too

An older server can have plenty of capacity for its workload long after its platform stops receiving firmware fixes. Spectre and Meltdown are examples of CPU flaws that, on affected systems, can let malicious code infer or read data it normally couldn't access. Intel's 2019 microcode guidance for the MDS speculative execution flaws lists Wolfdale and Yorkfield (the designs behind many Core 2 Duo and Core 2 Quad chips) among the products it doesn't plan to update.

Operating systems can mitigate certain flaws, but the protection available depends on the exact CPU, firmware, operating system and hypervisor. It's worth checking platform support separately from .NET compatibility when you decide whether a server stays in production. Intel's speculative execution advisory and the Linux kernel's Spectre documentation are good places to start.

What newer processors could do for performance

Modern .NET uses vector instructions to compare text and bytes several values at a time (Microsoft's .NET 8 performance write-up covers several examples). On Windows and Linux x64, .NET 11 also precompiles its ReadyToRun code for x86-64-v3, a higher level that includes AVX2 and FMA. Processors that meet x86-64-v2 but not v3 still run .NET 11, though they may compile more code at startup. How much any of this helps depends on where your server spends its time.

  • In SmarterMail, message parsing, local filtering and mailbox indexing all scan text or bytes. Faster processing there could give busy servers more headroom during mail bursts and help CPU-bound indexing jobs finish sooner. Disk throughput and external reputation lookups will still affect delivery and search speed.
  • In SmarterTrack, inbound ticket processing, portal requests and report preparation can benefit when text processing or response serialization is the bottleneck, which helps keep the agent interface responsive while background work runs. Database-bound searches and reports will still depend mostly on SQL and storage performance.
  • In SmarterStats, importing web logs means scanning each line for separators and parsing fields before reports are built. Faster parsing could shorten CPU-bound imports and reprocessing, especially on servers with large logs or many sites. If storage is the bottleneck, expect a smaller gain.

The SpamFoo Client classifies messages on the processor by default (NVIDIA GPU acceleration is optional), and it ships with its own .NET runtime. Wider vector instructions could speed up parts of message preprocessing and local inference where the underlying libraries use them, though the benefit depends on the model and message mix. If you run SpamFoo on a separate server, include that server in your review. Current requirements are on the SpamFoo system requirements page.

What to do now

Inventory every server that runs our products, including standby and disaster recovery systems, and check each one using the steps above. It’s a good idea to get started now, and not wait. More and more applications will be moving to these new frameworks, and not every company will give you the heads up required to ensure you can upgrade reliably.

We'll publish the final requirements and upgrade guidance in another blog post once we have requirements finalized. When builds using the new .NET 12 framework become available next year, test startup and a representative workload before you upgrade any production servers.