AseptSoft is versioned using the format Major.Minor.Revision.Build and can automatically check for and install updates when new versions are available. Two deployment formats are supported — pick whichever matches how your IT environment installs AutoCAD plug-ins.
🧩 Supported AutoCAD and Plant 3D releases
AseptSoft ships as a single bundle that carries a matching module for every supported release line of both AutoCAD and AutoCAD Plant 3D. When you launch your CAD application, the bundle inspects which release you are running and loads the module built for that exact version — there is nothing to pick or configure by hand.
|
Product line |
Supported releases |
How the right module is chosen |
|---|---|---|
|
📐 AutoCAD |
2018 through 2027 |
The bundle matches your AutoCAD release and loads the corresponding module automatically. |
|
🏭 AutoCAD Plant 3D |
2018 through 2027 |
The bundle matches your Plant 3D release and loads the corresponding module automatically. |
✅ The most recent AutoCAD 2027 and AutoCAD Plant 3D 2027 release lines are fully supported. Installing AseptSoft on a 2027 machine works exactly like every other supported year: the correct module loads on its own, with the same ribbon, commands, and behaviour as on earlier releases.
🔄 Running several AutoCAD versions side by side
A single AseptSoft installation covers every supported AutoCAD and Plant 3D release on the machine at once. If your team keeps, say, AutoCAD 2025 and AutoCAD 2027 installed together, both will load AseptSoft correctly from the same install — each picks up the module built for its own release.
💡 Pharma example: A validation team finishing a CIP-skid project in AutoCAD Plant 3D 2025 can open the same machine's newer AutoCAD Plant 3D 2027 to start the next sterilization-loop P&ID — AseptSoft activates in both, so no re-installation is needed when the site rolls forward to the new release.
📦 Deployment formats
AseptSoft can be installed in either of two formats. Both are recognised automatically and can be kept up to date through the same Software Updates window.
|
Format |
Where it installs |
Admin rights required |
Typical use |
|---|---|---|---|
|
🏛️ MSI |
|
✅ Yes |
IT-managed fleet deployments. |
|
📦 bundle.exe |
|
❌ No |
Per-user installations on machines without admin rights. |
The Software Updates window detects which format your installation uses and applies updates with the matching mechanism.
⚙️ Update settings
Configure how AseptSoft handles updates through the update settings window. Updates are categorised by significance:
|
Category |
Triggers When |
Example |
|---|---|---|
|
🔴 Major updates |
The Major or Minor version number changes |
1.1.1.1 → 2.1.1.1 or 1.2.1.1 |
|
🟡 Minor updates |
The Revision or Build number changes |
1.1.1.1 → 1.1.2.1 or 1.1.1.2 |
Each category can be independently configured with one of three update behaviours:
|
Setting |
Behaviour |
|---|---|
|
🔄 Auto Update |
Automatically downloads and installs the update without prompting. |
|
❓ Always Ask |
Shows a prompt when a new version is found. You can choose: Yes (install now), Cancel (ask again next launch), or No (skip this version — only prompted again when an even newer version is found). |
|
🔧 Update Manually Only |
No automatic prompts. Check for updates manually through the settings window. When a newer version is detected, a manual update button appears next to the "Updating status" field. |
🔁 Switching to auto-updates
If your installation isn't currently managed by auto-updates (e.g. you ran the installer manually), the settings window offers two switch options. Each one is explained in a single sentence directly next to the button so you can pick the right deployment without reading the docs.
|
Option |
What you get |
|---|---|
|
🏛️ Use MSI auto-updates |
Future updates install into Program Files via MSI. Requires admin rights. Adds an Add/Remove Programs entry. Best for IT-managed installations. |
|
📦 Use bundle.exe auto-updates |
Future updates install per-user under |
A confirmation dialog reiterates the consequences of your choice before committing — so you can back out if you picked the wrong one.
💡 If your installation is already managed by auto-updates, the switch panel doesn't appear; instead the window shows a single Update now button.
🔍 Checking for updates on demand
The Product Update Settings window always shows three live fields — Current version (what is installed), Available version (the latest on the Aseptconn server), and Updating status (the progress or result of the latest check). Two buttons sit beneath them:
|
Button |
When it shows |
What it does |
|---|---|---|
|
🚀 Update now |
When a newer version is available and your installation is managed by auto-updates |
Downloads and installs the available version immediately. |
|
🔍 Check again |
Always available |
Re-reads both your installed version and the latest version on the server, regardless of what the window currently shows. |
To re-check for a release at any moment:
-
Open the Product Update Settings window.
-
Click Check again.
-
Watch the status line step through Checking installed version… → Checking for updates… and settle on either Already up to date or New version available .
-
If a newer version is found, the Update now button appears so you can install it on the spot.
💡 Check again is the quickest way to confirm you are on the latest release right after a new version has been announced — there is no need to close the window or restart your CAD application to force a fresh look at the server.
📥 Update process
When an update is triggered (automatically or manually), AseptSoft follows this workflow:
-
📋 Check current version — reads the installed version.
-
⬇️ Download installer — downloads the new installer (MSI or bundle.exe, matching your deployment format) from the Aseptconn update server.
-
🔐 Verify signature — validates that the downloaded installer's certificate matches the currently installed version (prevents tampering).
-
👤 User decision — based on your settings, either proceeds automatically or prompts for confirmation.
-
🚀 Execute installer — launches the installer to perform the upgrade.
Security: AseptSoft verifies the digital signature of every downloaded update to ensure it originates from Aseptconn. If verification fails, the update is rejected and you are prompted to contact support.
⚠️ Runtime update limitations
On certain systems, AutoCAD may lock specific files at runtime, preventing the installer from updating them while the application is running. If you encounter this:
-
Set the update mode to Always Ask.
-
When prompted about an update, select No (to skip for now).
-
Close AutoCAD completely.
-
Run the installation kit manually to update to the latest version.
-
Reopen AutoCAD.
🔗 Related Pages
-
Login and Subscription — Account and license management.
-
File System — Where settings and application data are stored.
-
First Time Setup — Initial configuration guide.