Revit 2027 and AutoCAD 2027 Need Windows 11: What Design Firms Should Do Now

You went to install the 2027 release and it stopped. Revit 2027, AutoCAD 2027, and Civil 3D 2027 all require Windows 11, and the machine sitting on that desk still runs Windows 10.

Here is the short version. Autodesk’s 2027 releases require Windows 11. Revit 2027, AutoCAD 2027, AutoCAD LT 2027, and Civil 3D 2027 all list one operating system: 64 bit Microsoft Windows 11. Windows 10 is off the list. Microsoft’s own Windows 10 clock is looser than people think, because Microsoft quietly added a second year of Extended Security Updates in June 2026, pushing that program to October 12, 2027. But Autodesk did not move. So your CAD roadmap, not Microsoft, sets your timeline. The right move is to inventory every machine, check the BIOS before you condemn anything, test one workstation with your full software stack, then upgrade and replace in stages.

The deadline that did not move

Here are the plain facts, straight from Autodesk.

Revit 2027, Revit LT 2027, and Revit Server 2027 list the operating system as 64 bit Microsoft Windows 11. AutoCAD 2027 and AutoCAD LT 2027 say the same thing. So does Civil 3D 2027. One line, one operating system.

Compare that to last year. Revit 2026 supported Windows 10 version 1809 or later. So 2026 was the last release that met your Windows 10 machines where they were.

This matters more than a Microsoft date, and here is why. You control when you take a Microsoft update. You do not control when a client or a partner firm sends you a model saved in the 2027 release. Revit files do not open backward. Once one architect on the project team moves up, everybody on that project moves up. That pressure does not care about your IT budget calendar.

Microsoft moved its deadline once already. Autodesk did not move at all.

Microsoft moved its date. That is the point.

Windows 10 reached end of support on October 14, 2025. From that day, Microsoft stopped shipping it free security updates.

Microsoft offered a bridge called Extended Security Updates (ESU). It sends critical and important security patches only. No new features. No bug fixes. No general technical support.

Here is the part most firms have not caught. The consumer ESU program was supposed to run one year, to October 2026. In late June 2026, Microsoft quietly extended it a second year. Microsoft’s page now says you can enroll any time until the program ends on October 12, 2027, and if you are already enrolled, your coverage continues to that date with no action needed.

We are not pointing that out so you can relax. We are pointing it out to show you which deadline is real. Microsoft has now blinked once. It could blink again. Autodesk publishes system requirements per release and does not walk them back. Build your plan on the Microsoft date and you are planning around the softer of the two numbers.

The ESU trap: the free option probably does not apply to your firm

This is where a lot of internet advice gets small firms in trouble. There are two ESU programs, and they are not the same thing.

The consumer program is the easy one people talk about. You enroll from Settings, Update and Security, Windows Update. It is free if you sync your PC settings with a Microsoft account, or 1,000 Microsoft Rewards points, or a one time $30 purchase. One license covers up to 10 devices.

And most business machines cannot use it. Microsoft’s own words: the consumer ESU program cannot be used in commercial scenarios, and enrollment will not be offered for devices in kiosk mode, or devices joined to an Active Directory domain or Microsoft Entra, or devices enrolled in a mobile device management (MDM) solution. Microsoft goes further. If a device enrolls and later becomes a commercial device, the enrollment gets suspended.

Read that against your own office. Do you have a domain controller? Are your PCs Entra joined for Microsoft 365? Are they managed by an RMM or Intune? If yes to any of those, that free path is closed to you. Your office manager can click Enroll now all day and nothing will happen.

That is the dangerous part. Not that the firm is unprotected. That the firm thinks it is protected and is not.

The commercial program is the one that actually applies. You buy it through Microsoft volume licensing and activate it with a key, not a button. It is $61 per device for Year One, and the price doubles every year after, to a maximum of three years. Minimum purchase is one license, so a small firm can buy exactly what it needs.

One catch nobody mentions. ESU is cumulative. Microsoft states it plainly: if you buy in Year Two, you have to pay for Year One too. Waiting does not save you the first year, it just stacks it. A firm that stalls until Year Two pays $183 per machine, not $122.

One more prerequisite stops people cold. Any ESU, consumer or commercial, requires the machine be on Windows 10 version 22H2 with current updates installed. A workstation still on 21H2 gets nothing at all.

Before you buy a single computer, check the BIOS

Now the money part, and the mistake we see most often.

Windows 11 has three hardware requirements. A security chip called TPM 2.0. A modern boot setup, meaning UEFI with Secure Boot turned on. And a supported processor, roughly an 8th generation Intel Core or an AMD Ryzen 2000 series or newer.

You will run the compatibility check, a pile of machines will fail, and the temptation is to write them all off, don’t.

Microsoft says it directly: in some cases, PCs that are capable of running TPM 2.0 are not set up to do so. Most motherboards ship with it turned off. The setting lives in the UEFI BIOS, and every maker labels it something different. Intel PTT. Intel Platform Trust Technology. AMD fTPM. AMD PSP fTPM. Security Device Support. TPM State. Same idea, different name.

Secure Boot is similar. Plenty of machines were set up years ago with an older disk layout (MBR) that has to be converted to a newer one (GPT) before Secure Boot will turn on. Microsoft ships a tool for that. It is a job for your IT provider, not a reason to buy a computer.

For example, let us say you have eight workstations from 2018 with 8th generation Intel chips. All eight fail the check. Six fail only because TPM and Secure Boot are off in firmware. That is a firmware visit, not eight new workstations. At real workstation prices, that mistake is thousands of dollars for nothing.

The processor is the honest wall. If the CPU is not on Microsoft’s supported list, no setting fixes it and no part you can add fixes it. Those machines get replaced. But find out which ones those actually are before anybody signs a purchase order.

And one thing you should not do. You may hear about tricks to force Windows 11 onto a machine that does not qualify. Do not do that on work computers. It is unsupported, updates can stop arriving, and it is exactly the kind of shortcut that turns into a mystery problem in the middle of a deadline week.

What actually breaks on migration day

Every fact above can be true and a migration can still go badly. Here is what a real plan accounts for, and what most articles skip.

• Old Autodesk versions on new Windows. Autodesk says Windows 11 is compatible with products version 2023 or above, except Autodesk CFD 2023 and 2024. For 2022 and earlier, Autodesk’s own language is that some were designed and tested for Windows 11 but many were not. If you run perpetual licenses of AutoCAD 2019 or Revit 2020, check the system requirements for your exact product and version first.
• License servers and dongles. Network licensing, and any hardware key with its own driver, needs to be confirmed on Windows 11 before the workstation that depends on it moves.
• Plotters and large format printers. Older wide format devices are a common casualty. The driver (the small program that lets Windows talk to the device) may not have a Windows 11 version.
• The rest of the stack. Survey packages, structural analysis tools, older Bluebeam installs, and Revit add ins. The add ins are the ones that bite, because a plugin your team uses every day may not have a build for the 2027 release.
• Graphics drivers. On a real CAD workstation, use the certified driver for your card and your Autodesk release, not whatever Windows Update hands you.

So here is the rule. Migrate one workstation first. Not the principal’s. Pick a heavy CAD user who will work on it for a week with the full stack, plotting, licensing, add ins, everything. Find the surprises on one machine instead of twelve.

Windows 11 is not a finish line

One more thing, because we would rather you hear it from us.

Windows 11 has its own lifecycle. Home and Pro editions get 24 months of updates per version. Windows 11 version 24H2 Home and Pro reaches end of updates on October 13, 2026. Move to Windows 11 and then never touch it again, and you are right back where you started, just later.

You will also hear that Microsoft 365 apps keep getting security updates on Windows 10 until October 10, 2028. True, and it does not save you. Patched Word and Excel on an unpatched operating system is a locked door in a wall with a hole in it. And it does nothing for Revit 2027.

A plan you can start this week

Here is the whole thing, in order.

1. Inventory every machine. Model, age, processor, and whether TPM and Secure Boot are on or just off.
2. Sort into three piles, not two. Ready for Windows 11. Fixable in firmware. Truly too old, meaning the processor is not supported.
3. Fix the firmware pile. This is the pile that saves you real money.
4. Inventory the software, not just the hardware. Autodesk versions, add ins, license servers, plotters, dongles, specialty tools.
5. Migrate one CAD workstation and live on it for a week. Full stack, real projects.
6. Then roll the rest in stages, heavy CAD users first, so the people who feel the pain the most get relief the soonest.
7. Use ESU only as a bridge for stragglers, and use the right ESU. If your machines are domain joined, Entra joined, or MDM managed, that means commercial ESU through volume licensing, not the free consumer button.

Proactive is better than reactive. The work is the same either way. Doing it on your schedule is calm. Doing it the week a client sends you a 2027 model is not.

The honest part about cost

We are not going to tell you a forced hardware refresh is a gift. It is not. New CAD workstations are real money, the setup time is real time, and some of that is billable time you do not get back.

What we will tell you is that the cost is controllable, and most of the control is in the first two steps. Every machine you rescue with a firmware setting is a machine you do not buy. Every surprise you find on one test workstation is a surprise you do not find on twelve at once. That is where the savings are. Not in a discount, in a plan.

If a machine really is too old for Windows 11, it was probably already slow in Revit and Civil 3D. When you replace it, size it for the work.

Do not forget the security side either. Ransomware crews look for old, unsupported systems on purpose. Your cyber insurance application may also ask, in writing, whether you run supported software. Ask your broker what your specific policy says. Do not take a blog’s word for it, including ours.

Frequently asked questions

We will get your firm to Windows 11 without stopping work

Migrating a design office is not really a Windows project. It is a CAD project. It means knowing which machines upgrade, which get rescued in firmware, which get replaced, and which add ins, plotters, and license servers need attention, all sequenced so nobody loses a deadline.

That is exactly the kind of work we do for small architecture and engineering firms around Knoxville. Inventory, firmware check, software audit, one test workstation, then a staged rollout.

If your team is bumping into the 2027 releases, or you are not sure which machines are actually too old, give us a call. We will build you a migration plan that fits your budget and your calendar, so your team can focus on the work, not on an operating system.

Sources: System requirements for Revit 2027 products (Autodesk); System requirements for AutoCAD 2027 including Specialized Toolsets (Autodesk); System requirements for AutoCAD LT 2027 (Autodesk); System requirements for Autodesk Civil 3D 2027 (Autodesk); System requirements for Revit 2026 products (Autodesk); Windows 11 compatibility and support for Autodesk products (Autodesk); Windows 10 Consumer Extended Security Updates (Microsoft); Extended Security Updates (ESU) program for Windows 10 (Microsoft Learn); Windows 10 support has ended on October 14, 2025 (Microsoft); Windows 11 System Requirements (Microsoft); Enable TPM 2.0 on your PC (Microsoft); Windows 11 Home and Pro lifecycle (Microsoft Learn); Windows 10 end of support and Microsoft 365 Apps (Microsoft Learn)