You do not need 64 GB of RAM. Visual Studio 2026 installs and runs on 4 GB, works acceptably on 8 GB for a single workload, and is comfortable at 16 GB for professional .NET work. The 64 GB figure is Microsoft’s “works best” ceiling, aimed at large solutions on 16-core machines.
The things that will genuinely block you are not memory: 32-bit and ARM32 are not supported at all, Windows 10 on ARM64 is not supported, and several managed-environment configurations — S mode, LTSC, App-V, shared VDI — will refuse to install. Those are covered below.
Genuine Microsoft key · Instant delivery · No annual fee
At a Glance: Minimum, Recommended, and Optimal
Microsoft publishes its hardware guidance as a single list, with “minimum”, “we recommend” and “works best” folded into each line. Split into three tiers it reads more usefully — the minimum column is what will install, the recommended column is what Microsoft suggests for day-to-day professional work, and the optimal column is the configuration they describe the IDE as working best on.
Processor, RAM, storage and display figures are Microsoft’s, from the Visual Studio 2026 system requirements (rechecked September 2026, against VS 2026 18.7.x). The tiering, the SSD type and the per-tier OS calls are ours.
Worth knowing before you start: typical installations sit between 20 and 50 GB, but the total can reach 210 GB if you install every available workload.
How Much RAM Do You Actually Need?
This is the question behind most searches for VS 2026’s requirements, so it’s worth answering properly rather than repeating the spec sheet.
Microsoft’s exact wording is: “Minimum of 4 GB of RAM. Many factors impact resources used. We recommend 16 GB RAM for typical professional solutions; works best with 64 GB RAM.” Three figures, three different meanings — and the third one is the one that travelled. When the 64 GB number began circulating, a fair number of developers read it as a requirement and concluded Microsoft had lost the plot. It isn’t a requirement. “Works best” is the ceiling of Microsoft’s guidance, paired with a 16-core CPU, and it describes the conditions under which a large solution stops being the bottleneck.
The number that matters is 16 GB. That is Microsoft’s recommendation for “typical professional solutions”, and it matches most developers’ experience. Below it you compromise; above it the returns get smaller quickly. The jump from 8 GB to 16 GB is far more noticeable than the jump from 16 GB to 32 GB.
What each tier actually gets you
4 GB — the installer will accept it. You can open a small project and write code. You will not enjoy it, and you should not plan around it.
8 GB — genuinely workable for a single workload on a modest codebase, provided you are selective about which extensions and Copilot features you keep active. This is the configuration most people are actually asking about, and the honest answer is that it’s fine for learning, side projects and small solutions.
16 GB — the comfortable baseline for professional .NET development. Combined workloads, a browser full of tabs, and the IDE all coexist without swapping.
32 GB — where you want to be if Docker, local databases, emulators or container work are part of your daily loop alongside VS.
64 GB — Microsoft’s “works best” figure. Meaningful for very large solutions on a 16-core machine. For most people it is money better spent on a faster NVMe drive.
Windows 365 requirements: if you’re running VS 2026 in a Windows 365 cloud PC, Microsoft requires a minimum of 2 vCPU and 8 GB RAM, with 4 vCPU and 16 GB recommended.
Supported Operating Systems
VS 2026 is 64-bit only — there’s no 32-bit installer and ARM32 isn’t supported. It runs on Windows 10 as well as Windows 11, which surprises some people, and three generations of Windows Server are also in scope.
| Operating System | Supported Editions | ARM64 |
|---|---|---|
| Windows 11 | Home, Pro, Pro Education, Pro for Workstations, Enterprise, Education | ✓ Yes |
| Windows 10 | Home, Professional, Education, Enterprise (supported versions only) | ✕ No |
| Windows Server 2025 | Standard, Datacenter | — |
| Windows Server 2022 | Standard, Datacenter | — |
| Windows Server 2019 | Standard, Datacenter | — |
Windows 10 ARM64 is not supported. Windows 10 on x64 is supported, but Windows 10 on ARM hardware is not. Windows 11 ARM64 is fully supported. If you’re running Windows 10 on an ARM device, upgrading to Windows 11 is required before installing VS 2026.
Windows 10 works — but it’s on a clock
Visual Studio 2026 supporting Windows 10 does not mean Windows 10 is a sound place to build for the next few years. Windows 10 reached end of support on 14 October 2025. What keeps it patched now is the Extended Security Updates programme, and the dates moved this summer: Microsoft quietly extended consumer ESU by a year to 12 October 2027, while organisations can buy ESU for up to three years, to 14 October 2028.
So a Windows 10 dev machine is supportable for now, and VS 2026 will run on it. But you are building on a platform with a published end date, on a machine that cannot use the ARM64 build, and Microsoft’s own recommended tier for VS 2026 is Windows 11. If a hardware refresh is coming anyway, it’s the obvious moment.
Configurations that won’t work
A few setups trip people up, particularly in corporate or managed environments. These aren’t obscure edge cases:
| Configuration | Notes |
|---|---|
| Windows in S mode | Cannot install unsigned applications; VS 2026 will not install |
| Windows Enterprise LTSC | Not supported for running VS 2026 (can still target LTSC in builds) |
| Windows 10 Team Edition | Not supported as a host OS |
| Windows IoT Core / Enterprise IoT | Not supported as a host OS |
| Server IoT / Minimal Server Interface | Not supported; Server Core is supported for Build Tools only |
| Windows containers | Not supported for the full IDE — Build Tools can install into containers |
| Non-persistent virtual machines | VMs without a persistent full Windows OS are not supported |
| App-V / MSIX virtualization | Application virtualization wrappers are not supported |
| Shared VDI / pooled hosts | Multiple simultaneous users on the same machine are not supported |
| FSLogix roaming profiles | Not supported |
| Administrator protection mode | Some development scenarios require running VS as administrator — incompatible with this mode |
Processor, Storage and Display
Processor
AMD64/x64 and ARM64 are both supported; ARM32 is not. There’s no minimum clock speed in the spec. Microsoft recommends quad-core as the sensible floor and says the IDE works best with 16 cores or more. That’s not surprising — when you’ve got a build running, Roslyn analysers firing, and Copilot doing its thing simultaneously, core count matters more than clock speed.
Storage
The 2.5 GB minimum only applies to the most stripped-down installation possible — not something you’d actually develop on. A realistic single-workload install sits around 20–50 GB. Stack up web, desktop, C++, mobile, and data workloads and you can push 210 GB. That’s not a gotcha, just worth knowing before you install on a machine with a small system drive. SSD is strongly recommended by Microsoft, and if you’ve ever waited for a large solution to load on a spinning disk, you’ll understand why. If you are choosing between more RAM and a faster drive on a mid-range machine, the drive usually wins.
Display
Minimum is 1366 × 768 at 100% Windows scaling. If you’re on a HiDPI display with scaling set higher than 100%, the physical resolution needs to be proportionally larger to meet that logical threshold. VS 2026 is genuinely better at 1920 × 1080 or above — there’s a lot of UI to work with, and cramming it into a small viewport makes everything harder than it needs to be.
ARM64: What’s Supported and What Isn’t
VS 2026 runs natively on ARM64, but only on Windows 11 — Windows 10 ARM64 isn’t supported. If you’re on a Surface Pro X or an ARM-based dev machine, the native build is solid for .NET, C#, and standard C++ work. Where it gets complicated is workloads. A fairly significant list isn’t available in the ARM64 build:
The XAML designer also runs in an x86 process on ARM64 rather than natively. None of this is a dealbreaker if your work sits squarely in .NET or C++ — but if Python, Azure, or Office development features in your day-to-day, an x64 machine is still the right call.
Additional Requirements
A few prerequisites are worth knowing before you start the install, particularly in managed or corporate environments:
Administrator rights are required to install and update VS 2026 — standard user accounts won’t get through setup. The installer needs .NET Framework 4.7.2 or above to run, and VS 2026 itself requires .NET Framework 4.8; if 4.8 isn’t present, setup handles it automatically.
If you’re running VS on a Windows 11 machine, turn Smart App Control off. Microsoft explicitly flags it as something that can degrade IDE performance, and it’s worth checking before you install rather than troubleshooting slowness after.
WebView2 in managed environments: the installer requires the WebView2 runtime and will attempt to install it if it’s missing. If Group Policy on your domain restricts WebView2 installation or updates, setup will fail entirely. Worth confirming with your IT team before rolling out to managed machines.
One other change from VS 2022 worth flagging: TFS Office Integration now requires Office 2021 or later. VS 2022 accepted Office 2016; that’s no longer the case.
Build Tools and Remote Tools have their own requirements
If you’re setting up build agents rather than developer workstations, the requirements are lighter and the OS list is wider. Visual Studio Build Tools needs 2.3 GB to 60 GB of disk space, adds Windows Server Core 2025, 2022 and 2019 to the supported list, and — unlike the full IDE — can be installed into Windows containers. Remote Tools are lighter still at 1 GB RAM and 1 GB of disk, and notably do support Windows 10 ARM and the LTSC editions that the full IDE refuses.
Side-by-Side Installation with Visual Studio 2022
VS 2026 doesn’t replace VS 2022 — they install and run independently. During setup you’ll be offered the option to import your VS 2022 settings: theme, keyboard shortcuts, window layout, the lot. It’s a good idea to take it; the IDE feels familiar from the first launch rather than needing a week of reconfiguration.
Workloads are managed per installation, so any VS 2022 setup you rely on for legacy projects is unaffected. One useful addition in VS 2026: MSVC build tool versions 14.30–14.43 from VS 2022 are included as optional installer components, which means you can compile older C++ projects from VS 2026 without having to keep a full VS 2022 installation around just for the toolchain. If you’re weighing up whether to move at all, our Visual Studio 2022 vs 2026 comparison goes through what actually changed.
Microsoft Visual Studio 2026 Professional
Not sure which edition fits your situation? VS 2026 is available in Community (free with restrictions), Professional, and Enterprise. Our Visual Studio 2026 editions guide covers the licence differences, and Is Visual Studio 2026 Free? explains exactly when Community stops being an option for commercial work.
Frequently Asked Questions
Does Visual Studio 2026 really need 64GB of RAM? ▼
No. Microsoft’s system requirements say Visual Studio 2026 has a minimum of 4 GB of RAM, recommend 16 GB for typical professional solutions, and state that it “works best with 64 GB RAM”. The 64 GB figure is a best-case target paired with a 16-core CPU, not a requirement, and it circulated widely enough to be misread as one. For the large majority of developers, 16 GB is the figure that matters.
Can I run Visual Studio 2026 on 8 GB RAM? ▼
Yes, it’ll run. For a single lightweight workload on a modest codebase it’s perfectly usable, provided you’re selective about extensions and which Copilot features stay active. Where 8 GB struggles is larger solutions, multiple combined workloads, or running Docker and a browser alongside the IDE. Microsoft’s recommended figure is 16 GB for professional use, and the difference is noticeable rather than marginal.
What are the minimum RAM requirements for Visual Studio 2026? ▼
The minimum is 4 GB, though Microsoft recommends 16 GB for typical professional development and cites 64 GB as where the IDE works best. For small single-workload projects 8 GB is fine. Once you’re running larger solutions, combining workloads, or keeping Docker and a browser open alongside VS, 16 GB is where things stop feeling cramped.
Does Visual Studio 2026 run on Windows 10? ▼
Yes. Visual Studio 2026 supports Windows 10 Home, Professional, Education, and Enterprise on x64 hardware, provided you’re on a currently supported version. Windows 10 ARM64 is not supported — only x64.
Bear in mind that Windows 10 itself reached end of support on 14 October 2025. Consumer Extended Security Updates now run to 12 October 2027 after Microsoft extended the programme in June 2026, and organisations can purchase ESU to 14 October 2028. VS 2026 will run on Windows 10 throughout, but Windows 11 is Microsoft’s recommended tier and the only one that supports the ARM64 build.
How much disk space does Visual Studio 2026 require? ▼
The minimum installer footprint is 2.5 GB, but this applies only to a bare-minimum installation. Typical installations with a standard workload selection land at 20–50 GB. If you install multiple workloads — web, desktop, C++, mobile, data — the total can reach up to 210 GB. Microsoft recommends installing Visual Studio on an SSD to improve build and load performance.
Does Visual Studio 2026 support ARM processors? ▼
Visual Studio 2026 supports ARM64 on Windows 11 ARM64. ARM32 processors are not supported. Windows 10 ARM64 is also not supported — ARM64 support is Windows 11 only. Developers on ARM64 hardware should be aware that several workloads are unavailable in the ARM64 build, including Azure development, Python, data science, mobile development with C++, and Office/SharePoint development.
Can I install Visual Studio 2026 alongside Visual Studio 2022? ▼
Yes. Visual Studio 2026 and Visual Studio 2022 install independently and run side by side without conflict. During VS 2026 installation you can import settings, themes, and keyboard shortcuts from VS 2022. Workloads are configured separately per installation, so your existing VS 2022 setup is unaffected. VS 2026 also includes VS 2022 MSVC build tool versions as optional installer components, so older C++ projects do not require keeping a full VS 2022 installation.
What processor does Visual Studio 2026 require? ▼
AMD64/x64 or ARM64 — ARM32 isn’t supported. There’s no minimum clock speed in the spec, but Microsoft recommends quad-core as a sensible floor and notes that the IDE works best with 16 cores or more. When you’ve got a build running, Roslyn analysers active, and Copilot processing in parallel, that core count earns its keep.
Why won’t Visual Studio 2026 install on my machine? ▼
If the hardware is fine, the cause is usually the Windows configuration rather than the specs. VS 2026 will not install on Windows in S mode, Windows Enterprise or IoT LTSC editions, Windows IoT Core, Windows 10 Team Edition, or 32-bit and ARM32 systems. It is also unsupported under App-V or MSIX virtualization, on non-persistent VMs, on shared VDI and pooled hosts, with FSLogix roaming profiles, and with administrator protection mode enabled.
In managed environments the most common single cause is Group Policy blocking the WebView2 runtime, which the installer requires. Setup will fail outright rather than degrade gracefully.
Does Visual Studio 2026 require an internet connection? ▼
The web installer needs internet access to download components. If you need to install on machines without connectivity — common in corporate environments with restricted dev boxes — you can create a layout by running the installer with a --layout flag, which downloads everything to a local folder you can then use offline. Copilot features need a live connection regardless of how VS was installed.
Gary Walsh is the Head of Tech Support at Software Supplies, with more than 20 years in the IT industry. Fully Microsoft-certified and experienced across the full business software stack — from Windows and Office to cloud infrastructure and device management — Gary delivers practical, no-nonsense advice that helps users and businesses get the most from their technology.
