AutoCAD Architecture, Revit and the .NET10 Transition

Before you Update: AutoCAD Architecture, Revit and the .NET10 Transition

Autodesk is rolling out a new software runtime (.NET10) across AutoCAD Architecture and Revit. It is already present in the 2026 releases, and is now reaching the 2025 service releases as well. Check the rule and tables in this article before you install any new ACA or Revit update.

THE SIMPLE RULE

• ‍hsbDesign 28 and 29   →  .NET8
• hsbDesign 30  →   .NET10

Staying on .NET8 needs no action. Moving your AutoCAD Architecture or Revit installation to a .NET10 version means moving to hsbDesign 30 at the same time.

Check your situation

‍

‍

What is changing

Autodesk is moving AutoCAD Architecture and Revit from the .NET8 runtime to .NET10. This is not a single cut-over: each release year switches partway through its update cycle, so two builds from the same release year can sit on different sides ofthe line. One on .NET8, the next on .NET10.

hsbDesign is built against a specific runtime and has to be updated to match. When Autodesk changes the runtime under a release, hsbDesign needs a corresponding release before it can be considered fully supported on that build.

‍

‍

‍

Why this matters for you

If you install an ACA or Revit update that switches to .NET10 before your hsbDesign version supports that specific build, hsbDesign may not fail directly, it can also become unreliable in less obvious ways. Because the rollout is staggered per release and per service pack, the risk depends on the exact version you run, not simply the release year.

‍

Before you click “Update”

• Check your exact version. AutoCAD: Help → About. Revit: the R menu → About. Note the full build number, not just the year.
• Look it up in the tables above.Match both the year and the runtime column (.NET8 or .NET10) for your product.
• Hold off if it is not listed assupported. If the update would move you to a .NET10 build your hsbDesign version does not cover yet, wait and contact us first.

Already updated and seeing issues?

hsbDesign may not fail directly, it can also behave unpredictably. If you have already moved to a  .NET10 build that is not yet listed as supported, contact hsbcad Customer Success before continuing to work in the affected project. In many cases we can help you move back to a compatible build, though Autodesk only keeps a limited number of past updates available for download, so it is best to act quickly.

Frequently asked questions

Will this affect my existing models or projects?

No. This is about which combination of Autodesk software and hsbDesign runs reliably, not about your model files. Separately, note that moving a model forward to a newer release year cannot be undone, once a model is opened in a newer release year, it can no longer be saved back to an earlier one.

Is the issue the same for AutoCAD Architecture and Revit?

The underlying issue is the same, but the two products are on their own release and update schedules, so check the table for your product specifically.

Do I need to update hsbDesign if I'm staying on my current AutoCAD Architecture or Revit version?

No. hsbDesign 28 and 29 continue to fully support .NET8 releases. There's no need to move to hsbDesign 30 unless you're also moving your AutoCAD Architecture or Revit installation to a .NET10 release.

Need help?

Contact Customer Success with your ACA or Revit version and your current hsbDesign build, and we will confirm whether your combination is supported.

‍