BORIS for Autodesk Inventor - Secure Your CAD Designs

.NET 10 Update for Inventor and Vault: What CAD Managers Must Do Before 10 November 2026 | Autodesk Inventor | Register and Certify Ownership of CAD design

2026-10-24 15:27 News
Microsoft ends support for .NET 8 and .NET 9 on 10 November 2026, and Autodesk has moved its 2025 and 2026 desktop products, including Inventor and Vault, to .NET 10 to stay supported. On 14 October 2026, Autodesk reseller IMAGINiT warned that 2025 and 2026 products can crash or fail to open when only some of the updates are installed. The fix is simple to state and easy to get wrong: Inventor, Vault and every add-in have to move together.
For most Inventor users this looks like a routine update. For CAD managers it is a small migration project with a deadline. Inventor 2026.4 and Vault 2026.4 carry the new runtime for the 2026 release, Inventor 2025.5 and Vault 2025.5 do the same for 2025, and every add-in that loads into Inventor or Vault has to run on .NET 10 as well. A mismatch does not just cost time. When a Vault add-in stops loading, engineers start saving files locally, and the version history you rely on for releases, audits and ownership questions gets gaps.
This article explains what changes, which versions you need, what can break, and a step-by-step plan for the next two and a half weeks. It follows our guide to what to do with Windows 10 workstations now that ESU Year 1 is over, which covers the operating system side of the same upgrade season.
TL;DR: update Inventor, Vault and add-ins as one package before 10 November

.NET 8 and .NET 9 stop receiving security fixes from Microsoft after 10 November 2026. Autodesk moved Inventor and Vault 2025 and 2026 to .NET 10 through Inventor 2026.4, Vault 2026.4, Inventor 2025.5 and Vault 2025.5. Autodesk says the API does not change, but add-ins hit by .NET 10 breaking changes must be rebuilt. Partial updates are the main cause of the crashes IMAGINiT describes. Inventory your add-ins, test in a pilot group, update Vault server and clients with Inventor, and keep a backup and dated proof of your designs before you roll out.

What is changing, and why now?

.NET is the Microsoft runtime that Inventor and Vault use to run their own code and most add-ins. Inventor 2025 moved from the older .NET Framework 4.8 to .NET 8, and the 2026 release stayed on .NET 8. In September 2025 Microsoft extended support for its short-term releases to 24 months, which moved the end of support for .NET 9 to 10 November 2026, the same day as .NET 8. After that date, neither version gets security fixes or technical support from Microsoft.
Autodesk's answer was to move the 2025 and 2026 products to .NET 10, the current long-term release. Autodesk's developer blog announced the plan in July 2026: the 2026 updates were targeted for the first week of August and the 2025 updates followed later. The blog says there are no API changes, only the runtime moves, and that the updates for one release year should be installed together. Inventor 2027 already uses .NET 10, so if you are on 2027, this transition is behind you, although your add-ins still need to be tested on .NET 10.
Updates like these are easy to postpone, because they arrive as separate packages in Autodesk Access and add-in vendors ship their own builds on their own schedule. That is why the 10 November date matters now: after it, the old runtime keeps working, but it is no longer patched. If you want to understand the security side, our report on the Autodesk ADP Desktop SDK vulnerability shows how quickly Autodesk components on a workstation become an exposure when updates are delayed.

Which Inventor and Vault versions do you need?

IMAGINiT's support team published a list of minimum update versions on 14 October. For Inventor and Vault environments the key lines are below. If you also run AutoCAD Mechanical, AutoCAD Electrical or Navisworks next to Inventor, they have their own minimum versions in the same list, and they belong in the same rollout.
Release yearRuntime beforeMinimum update for .NET 10What to watch
2027.NET 10 alreadyCurrent 2027 updatesAutodesk says existing .NET 8 add-ins should keep working; test them anyway
2026.NET 8Inventor Professional 2026.4, Inventor Interoperability 2026.4, Vault 2026.4 (Client, File Server, Server)Install Inventor and Vault updates together; Vault add-ins may stop loading if one side is behind
2025.NET 8Inventor Professional 2025.5, Inventor Interoperability 2025.5, Vault 2025.5 (Client, File Server, Server)Same rule; Vault 2025.5 also raised the bundled DevExpress version for add-in developers
2024 and older.NET Framework 4.8Not part of this transitionDifferent runtime, but check whether these releases are still in your support plan
Note the Vault line: the minimum version covers the client, the file server and the Vault server. Updating only the Vault client on CAD workstations is not enough. Our Inventor Vault setup and management tips cover how to plan server updates with the least downtime.

What can break when updates are mixed?

IMAGINiT's support article describes products that crash or fail to open after updates on 2025 or 2026 software. Its advice is to update all components, not just one or two, and it warns that add-ins and object enablers that are not updated will keep causing the same crashes and fatal errors.
Autodesk's own help for Inventor 2026 warns that Inventor updates using .NET 10 may create a temporary compatibility gap with existing Vault add-ins, and the Vault 2026.4 help tells users to install both the design product's .NET 10 update and the matching Vault update. In practice there are four common failure patterns:
  • Inventor updated, Vault not. The Vault add-in inside Inventor no longer loads, so users cannot check files in or out from Inventor.
  • Vault updated, Inventor not. The same gap from the other side, often on the one workstation that missed the rollout.
  • Third-party add-in not rebuilt. Autodesk says add-ins keep working unless they are affected by .NET 10 breaking changes. Those that are, for example code that still depends on BinaryFormatter, which Microsoft removed from .NET 9 onward, must be recompiled and retargeted.
  • In-house tools forgotten. Add-ins written by a former colleague, Vault job processor extensions and iLogic rules that call external .NET assemblies are rarely on anyone's update list.
The data risk is the part that is easy to miss. When the Vault add-in fails, engineers keep working: they save to the desktop, copy assemblies to a shared drive or email files to a supplier. Those copies are outside Vault's version history and access control. Our guides on preventing CAD file version conflicts and common CAD security mistakes explain why those side copies cause trouble long after the crash is fixed.
Keep a dated record that does not depend on one update.

BORIS for Autodesk Inventor registers your CAD files with a blockchain timestamp and a certificate of ownership, directly inside Inventor, so key versions have proof even if your vault has a bad week.

👉 Discover BORIS for Autodesk Inventor

What do add-in developers and in-house tool owners need to do?

Autodesk's message to developers is consistent: the Inventor and Vault APIs did not change, so most add-ins built for .NET 8 should load on .NET 10. Some will not. Autodesk's April 2026 guidance for Inventor 2027 add-ins recommends testing on .NET 10, avoiding BinaryFormatter, and rebuilding .NET Framework 4.8 add-ins whose resource files contain embedded images or binary data. For Vault, the SDK interface stays the same, but its runtime dependency moves to .NET 10, and Vault 2025.5 raised the bundled DevExpress version, which matters if your add-in references DevExpress directly.
If your company builds its own tools, this is a good moment to look at them properly. Our guides to Inventor automation with iLogic, add-ins and the API, building your first Inventor add-in and plugin security architecture cover project setup, deployment and the access rights an add-in gets when it runs inside Inventor. Ask every commercial add-in vendor, including us for BORIS, which build supports your exact Inventor update, and test it before rollout.

How should CAD managers plan the next two weeks?

A practical plan for an Inventor and Vault team, from today to 10 November 2026:
  1. Inventory every workstation. Record the Inventor, Vault client and AutoCAD-based product versions on each machine, plus the Vault server and file server versions.
  2. List every add-in. Include commercial add-ins, in-house tools, Vault job processor extensions and iLogic rules that load external .NET assemblies, with the owner and the vendor contact for each.
  3. Ask vendors for .NET 10 builds. Get written confirmation of which add-in version supports Inventor 2026.4 or 2025.5 and the matching Vault update.
  4. Back up before you touch the server. Take a full Vault backup and test that you can restore it. Our CAD file backup strategies and notes on backup tools as an attack path explain how.
  5. Run a pilot group. Update a few workstations and a test Vault first. Check in, check out, release, copy design and job processor tasks, plus every add-in.
  6. Roll out as one package. Update Vault server and file servers, then Inventor, Vault client and add-ins on each workstation in the same session, using official Autodesk Access or manage.autodesk.com packages only.
  7. Look for files saved outside Vault. After rollout, ask users to check in anything they saved locally while add-ins were down, and compare recent local files against the vault.
  8. Record what you changed. Keep a dated log of versions per machine and register key design versions with a timestamp, so you can show what existed before and after the update.
Download installers only from official Autodesk portals. Our report on the Siemens Software Center ClickFix attacks shows how attackers use fake update prompts and genuine, signed installers to get onto engineering workstations, and update season is exactly when users are primed to click. For the people side of a rollout, see change management frameworks for CAD process updates.

The bigger picture

This week's news on our sister sites shows the same pattern from three angles: the systems around your design files change, and you need records that survive the change.
  • Patching under pressure. On CADChain, the report on the critical GitLab vulnerability covers a CVSS 10.0 flaw in self-managed GitLab fixed on 21 October 2026, and why engineering repositories need file-level protection as well as patches.
  • Supplier sharing. BORIS for SOLIDWORKS looks at the Ford v. InterMotive trade secrets appeal, argued in the Sixth Circuit on 22 October over a $13.2 million verdict, and what it teaches about sharing designs with large customers.
  • Contributor rights. Blended BORIS explains the Getty Images Chapter 11 filing and what it means for 3D stock artists who license their work through the platform.
CADChain explains how its CAD data protection technology works across CAD systems, and our article on blockchain timestamps for proving design authorship shows how dated records work in practice. For the AI features that arrived in Inventor this autumn, see our Autodesk University 2026 summary.

Conclusion

The .NET 10 transition is not a new feature, and nobody will thank you for it. But it is the kind of change that quietly breaks the link between Inventor and Vault if it is done piece by piece. Treat Inventor, Vault server, Vault client and add-ins as one package, test in a pilot, back up first, and make sure no design work ends up outside the vault while you update. Do it before 10 November 2026, and keep a dated record of what you changed and what your designs looked like on the day you changed it.
Your designs, your proof.

BORIS for Autodesk Inventor gives every registered file a blockchain timestamp and a certificate of ownership, without sending your models to a cloud service.

👉 See how BORIS for Autodesk Inventor works

FAQ: Inventor, Vault and the .NET 10 update

When do .NET 8 and .NET 9 reach end of support?

Microsoft ends support for both on 10 November 2026. After that date they no longer receive security fixes or technical support.

Which Inventor versions are affected?

Inventor 2025 and 2026, which run on .NET 8. The minimum updates for .NET 10 are Inventor Professional 2025.5 and 2026.4, with the matching Inventor Interoperability updates. Inventor 2027 already uses .NET 10.

Which Vault versions do I need?

Vault 2026.4 for the 2026 release and Vault 2025.5 for 2025, covering the client, the file server and the server, installed together with the matching Inventor update.

Will my add-ins still work?

Autodesk says the API has not changed and most add-ins should keep working. Add-ins affected by .NET 10 breaking changes, such as code that uses BinaryFormatter, must be rebuilt for .NET 10. Ask each vendor which version supports your update.

Why does Inventor crash after the update?

IMAGINiT reports crashes and failure to open when only some products or add-ins were updated. The usual fix is to bring every 2025 or 2026 product, the Vault client and all add-ins to the minimum .NET 10 versions.

Does this affect Inventor 2024 or older?

No. Those releases were built on the older .NET Framework 4.8, which is not part of this transition. Check separately whether they are still covered by your Autodesk plan.

What happens if we miss 10 November?

The software keeps running, but the .NET 8 or .NET 9 runtime underneath it no longer gets security fixes. That leaves CAD workstations with an unpatched component, which security and compliance reviews will flag.

How does BORIS help during an update like this?

BORIS for Autodesk Inventor registers CAD files with a blockchain timestamp from inside Inventor. Each registered version gets a dated certificate of ownership, so you can show what you designed and when, independent of a single vault, workstation or update.