In this guide
You’re trying to install AutoCAD, and then it happens: “Install Failed — Error 1603. Fatal error during installation.” The progress bar stops. The installer rolls back. And you’re left staring at a dialog box that tells you absolutely nothing useful about what went wrong.
I’ve seen this error frustrate everyone from solo freelancers to IT admins deploying across fifty workstations. Error 1603 is one of the most common — and most vague — installation failures in the entire Autodesk ecosystem. It hits AutoCAD, Revit, Civil 3D, Inventor, and basically anything that uses the Microsoft Windows Installer (MSI) engine.
The good news: it’s almost always fixable. The bad news: there’s no single magic button. Error 1603 is a generic catch-all code, which means you often need to work through several possible causes before you land on the one that applies to your machine.
This guide walks through every known fix, ordered from quickest to most involved. I’ve also added version-specific notes for AutoCAD 2022, 2025, and 2026 — because Autodesk keeps changing the installer architecture, and the fixes aren’t always the same.
Quick answer: AutoCAD Error 1603 is a generic Windows Installer failure. The most common causes are a corrupted Autodesk Desktop Licensing Service, leftover files from a previous installation, antivirus interference, or insufficient permissions.
Start by running the installer as Administrator, clearing your TEMP folder, and restarting the Autodesk Desktop Licensing Service. If that doesn’t work, perform a clean uninstall and reinstall.
Common symptoms
- AutoCAD installer rolls back at 60–90%
- “Installation Failed — Error 1603. Fatal error during installation.”
- MSI Error 1603 in the setup log file
- Autodesk setup exits unexpectedly without a clear error
- Installation progress bar stalls, then the installer closes
What is AutoCAD Error 1603?
Error 1603 is a standard MSI (Microsoft Windows Installer) return code that means “fatal error during installation.” It’s not specific to Autodesk — any software that uses MSI can throw it. But AutoCAD users see it disproportionately often because the Autodesk installer deploys a complex stack of dependencies: Visual C++ redistributables, .NET Framework components, the Autodesk Desktop Licensing Service (AdskLicensing), and — since 2024 — the Interoperability Engine Manager.
When any one of these sub-installers fails, the parent installer catches the failure and surfaces it as the generic 1603 code. That’s why the error message is so unhelpful — it’s a wrapper around a dozen possible failures, and the dialog box doesn’t tell you which one actually broke.
Common causes at a glance
Before diving into fixes, here’s a quick overview of what typically triggers the error:
| Cause | Likelihood | Versions affected |
|---|---|---|
| Autodesk Desktop Licensing Service corrupted or stopped | Very common | 2020 and later |
| Leftover files from a previous installation | Very common | All versions |
| Antivirus / security software blocking the installer | Common | All versions |
| Corrupted Visual C++ Redistributables | Common | All versions |
| Interoperability Engine Manager conflict | Common | 2024, 2025, 2026 |
| Insufficient disk space on C:\ drive | Moderate | All versions |
| Corrupted .NET Framework | Moderate | All versions |
| Windows Installer service stopped | Occasional | All versions |
| Permissions issue (non-admin or UAC) | Occasional | All versions |
| 8.3 short filename creation disabled | Rare | All versions |
Now let’s go through each fix. Start at the top and stop when one works.
Fix 1 — Run the installer as Administrator
This sounds obvious, but it catches more people than you’d expect. Even if you’re logged into an admin account, Windows doesn’t always grant full elevated permissions by default.
Right-click the installer EXE → select Run as administrator.
If you downloaded from the Autodesk Account portal, the extracted setup file is usually in your Downloads folder or a temp directory — find the actual Setup.exe and right-click that one specifically.
On Windows 11, also check that UAC (User Account Control) isn’t set to the maximum level. The default “Notify me only when apps try to make changes” works fine. The top-level “Always notify” setting can interfere with MSI sub-installers.
Fix 2 — Clear the TEMP folder
The Windows TEMP directory collects thousands of temporary files over time. If it’s bloated or contains corrupted files from a previous failed installation attempt, the MSI engine can choke.
Press Win + R, type %TEMP%, hit Enter.
Select all files (Ctrl + A) and delete them. Some files will be “in use” — skip those.
Also clear the secondary temp directory: C:\Windows\Temp (you’ll need admin rights).
Try the installation again.
Fix 3 — Restart the Windows Installer Service
The Windows Installer service itself can get stuck, especially after a failed installation or a Windows Update.
Press Win + R, type services.msc, hit Enter.
Find Windows Installer in the list → right-click → Restart.
If it shows as “Stopped,” click Start instead.
Attempt the installation again.
Fix 4 — Fix the Autodesk Desktop Licensing Service
This is the single most common cause of Error 1603 on AutoCAD 2020 and later. The Autodesk Desktop Licensing Service (AdskLicensing) handles license validation, and if it’s corrupted, stopped, or running under the wrong account, the installer fails immediately.
Step 1 — Check if the service is running. Open services.msc, find “Autodesk Desktop Licensing Service.” It should show Status = Running, Startup Type = Automatic.
Step 2 — Fix the Log On account. Right-click the service → Properties → “Log On” tab. Make sure “Local System account” is selected. If it’s set to “This account” (a specific user), that’s the problem. Change it back to Local System, click Apply, restart the service.
Step 3 — If corrupted, reinstall it. Navigate to C:\Program Files (x86)\Common Files\Autodesk Shared\AdskLicensing and run uninstall.exe. Then download the latest Autodesk Desktop Licensing Service installer from Autodesk’s support site and reinstall.
C:\Program Files\Autodesk\AdODIS\V1. If you see a RemoveODIS.exe file there, run it as Administrator to cleanly remove the service before reinstalling.
Fix 5 — Reinstall Visual C++ Redistributables
AutoCAD depends on multiple versions of the Microsoft Visual C++ Redistributable runtime. If any of these are corrupted — which happens more often than you’d think, especially on machines that run lots of different software — the installer fails.
Open Settings → Apps → Installed apps (or Programs and Features on older Windows).
Find all entries labeled “Microsoft Visual C++ Redistributable” — you’ll typically see versions from 2012 through 2022.
Uninstall all of them. Reboot.
Download the latest all-in-one Visual C++ Redistributable from Microsoft’s official page and install it, or let the AutoCAD installer re-deploy them during a fresh install.
Fix 6 — Temporarily disable security software
Antivirus and endpoint protection software is a surprisingly frequent culprit. Products like Bitdefender, Kaspersky, Norton, ESET, and even Windows Defender can quarantine installer files mid-extraction or block MSI sub-processes.
Temporarily disable real-time protection (or add the entire Autodesk installation folder to your exclusion list).
Run the installer again.
Remember to re-enable protection after installation completes.
For enterprise environments: Autodesk maintains a list of known conflicting applications. If you’re running SentinelOne, CrowdStrike, or Carbon Black, check Autodesk’s “Known Conflicting Applications” knowledge base article for specific workarounds.
Fix 7 — Clean uninstall and reinstall
If you’ve previously installed — or attempted to install — a different version of AutoCAD, leftover registry entries and files will almost certainly cause 1603. A standard uninstall through Windows Settings is often not enough. You need a clean removal.
Option A — Microsoft Program Install and Uninstall Troubleshooter. Download this free tool from Microsoft. It detects and removes registry ghosts from failed MSI installations that the normal uninstaller can’t clean up.
Option B — Manual clean uninstall. Uninstall all Autodesk products through Windows Settings first. Then manually delete:
C:\Program Files\Autodesk\
C:\ProgramData\Autodesk\
C:\Users\[YourName]\AppData\Local\Autodesk\
Reboot, then attempt a fresh installation.
This is the nuclear option, but it resolves the vast majority of persistent 1603 errors. If you’re upgrading from AutoCAD 2024 to 2026, a clean removal of the older version first is strongly recommended.
Fix 8 — Interoperability Engine Manager (2024–2026)
Starting with the 2024 product cycle, Autodesk introduced the Interoperability Engine Manager as a shared component across products. When this component fails to install or can’t be upgraded over an older version, the entire AutoCAD installation fails with Error 1603.
Confirm the issue: Open the installation log at C:\Users\[YourName]\AppData\Local\Autodesk\ODIS\ and search for “Interoperability Engine Manager” — if that component shows error code 1603, this is your culprit.
Fix: Download the standalone Autodesk Interoperability Engine Manager installer (version 1.4.0 or later) from Autodesk’s support page and install it separately.
If an older version is stuck, use the Microsoft Program Install and Uninstall Troubleshooter to remove it first, then install the new version before re-running the AutoCAD setup.
Fix 9 — Check disk space and 8.3 naming
Two less obvious issues that still catch people:
Disk space: Even if you’re installing AutoCAD to a secondary drive (D:\, E:\), the installer requires temporary space on your C:\ drive — roughly twice the size of the installation files. AutoCAD 2026 needs about 10 GB of free space on C:\ regardless of the target drive.
8.3 short filename creation: Some Windows installations have short filename generation disabled for performance. The MSI engine still requires it in certain scenarios. Check the registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
If NtfsDisable8dot3NameCreation is set to 1, change it to 0 and reboot.
Fix 10 — Create a new Windows user profile
If nothing else works, the issue might be a corrupted Windows user profile rather than anything related to AutoCAD itself. Create a new local administrator account on the machine, log into it, and try the installation from there.
If it works, the problem was your original user profile — not the installer. This is a last resort, but it’s solved cases that had IT admins pulling their hair out for days.
Version-specific notes
Autodesk changes the installer architecture with almost every major release, which means the same error code can have different root causes depending on your version:
| Version | Key considerations |
|---|---|
| AutoCAD 2022 | First version to use the newer ODIS installer system. Shell Folders registry key must point to a local C:\ path — redirected (network) folders cause 1603. Check HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders. |
| AutoCAD 2025 | Introduced the Interoperability Engine Manager dependency. If upgrading from 2024, the older IEM version may conflict. Remove it manually before installing 2025. |
| AutoCAD 2026 | Requires .NET Framework 4.8+ and Visual C++ 2022 Redistributable. Windows 10 version 1809 or later, or Windows 11. Older Windows 10 builds will throw 1603 without a clear message about the OS version being unsupported. |
| Revit 2023–2026 | Shares the same licensing service and IEM components as AutoCAD. If Revit throws 1603, the fix workflow is identical — start with the Autodesk Desktop Licensing Service. |
AutoCAD Error 1603 on Windows 11
Windows 11 introduced several security changes that can interfere with AutoCAD installation. All of the fixes above still apply, but there are three additional things to check:
Smart App Control — In Windows 11 22H2 and later, this feature can silently block unsigned or uncommon installer components. If Smart App Control is set to “Evaluation” or “On,” try setting it to “Off” temporarily during installation. (Note: once turned off, Smart App Control can’t be re-enabled without a Windows reset.)
Memory Integrity (Core Isolation) — This virtualization-based security feature occasionally conflicts with Autodesk’s licensing service driver. If you see 1603 specifically during the licensing component: Settings → Privacy & Security → Windows Security → Device Security → Core Isolation Details → toggle off Memory Integrity. Reboot and retry.
Controlled Folder Access — If enabled, this ransomware protection feature blocks the installer from writing to protected directories. Add the Autodesk setup executable to the “Allow an app through Controlled folder access” list.
How to read the installation log
When none of the standard fixes work, the installation log is your best friend. It tells you exactly which sub-component failed — instead of the generic “1603” wrapper that the dialog box shows.
Log location:
AutoCAD 2022+: C:\Users\[YourName]\AppData\Local\Autodesk\ODIS\
Older versions: C:\Users\[YourName]\AppData\Local\Temp\
Open the most recent .log file in a text editor and search for “1603” or “error” or “failed.” You’re looking for the line immediately before the 1603 code — that’s the component that actually broke.
Common culprits in the logs: AdskLicensing (licensing service), VCRedist (Visual C++), dotNetFx (.NET Framework), IEM (Interoperability Engine Manager), ODIS (installer framework).
When nothing works
If you’ve worked through every fix on this list and the installer still fails, you can contact Autodesk Support directly — they can remote into your machine and diagnose issues that aren’t visible from the log files. The Autodesk Virtual Agent also offers guided troubleshooting for common installation errors.
But honestly? If you’re spending your third hour fighting an installer instead of actually doing CAD work, it might be worth asking a different question: does the software have to be this complicated to install?
CAD software that doesn’t fight you on installation
I run a CAD software distribution site, so I’m biased — but one of the most common things I hear from customers who switch to SmartCAD is some version of “I downloaded it, ran the installer, and it just… worked.”
SmartCAD is an IntelliCAD-based DWG editor with native .DWG support, AutoCAD-compatible commands, and solid 2D/3D drafting. There’s no licensing service to troubleshoot, no Interoperability Engine Manager dependency, no Visual C++ stack that needs to be in exactly the right state. The installer is a single EXE, and it doesn’t phone home during setup.
If Error 1603 brought you here and you’re open to exploring, there’s a free 30-day trial — full features, no credit card.
Related reading
AutoCAD Tips Best AutoCAD Alternatives with Perpetual Licensing AutoCAD Tips AutoCAD Commands PDF — Complete Reference SmartCAD Support SmartCAD System Requirements Blog More CAD Tips & GuidesFrequently asked questions
What does Error 1603 mean in AutoCAD?
Error 1603 is a generic code from the Microsoft Windows Installer (MSI) that means “fatal error during installation.” It’s not specific to AutoCAD — it can occur with any software that uses MSI. The code itself doesn’t identify the actual problem, which is why it’s so frustrating to troubleshoot. The real failure is usually in a sub-component like the Autodesk Desktop Licensing Service, Visual C++ Redistributables, or the Interoperability Engine Manager.
Can antivirus software cause AutoCAD Error 1603?
Yes. Antivirus and endpoint protection software is one of the most common causes. Products like Bitdefender, Norton, Kaspersky, ESET, and even Windows Defender’s real-time protection can quarantine installer files or block MSI sub-processes mid-execution. Temporarily disabling real-time protection during installation usually resolves this. Enterprise security tools like CrowdStrike and SentinelOne are also known to conflict with Autodesk installations.
Does Error 1603 affect all AutoCAD versions?
Error 1603 can occur on any AutoCAD version, but it’s particularly common on versions 2020 and later because of the Autodesk Desktop Licensing Service dependency. Versions 2024, 2025, and 2026 have an additional failure point — the Interoperability Engine Manager — that older versions don’t use. Each generation of the Autodesk installer introduces new components, which means new potential points of failure.
How do I fix Error 1603 on Windows 11?
All standard fixes apply on Windows 11, but there are three additional things to check: Smart App Control (which can silently block installer components), Memory Integrity / Core Isolation (which can conflict with the licensing service driver), and Controlled Folder Access (which can prevent the installer from writing to protected directories). Temporarily disabling these features during installation often resolves Windows 11–specific 1603 errors.
What is the Autodesk Desktop Licensing Service?
The Autodesk Desktop Licensing Service (also called AdskLicensing or ODIS) is a background service that validates your Autodesk product license. It was introduced with the 2020 product cycle. If this service is stopped, corrupted, or running under the wrong user account (set to “This account” instead of “Local System account”), the AutoCAD installer will fail with Error 1603. Reinstalling the licensing service is the single most effective fix for modern AutoCAD versions.
Where is the AutoCAD installation log file?
For AutoCAD 2022 and later, the log is at C:\Users\[YourName]\AppData\Local\Autodesk\ODIS\. For older versions, check C:\Users\[YourName]\AppData\Local\Temp\. Open the most recent .log file in a text editor and search for “1603” or “failed” to find the specific component that caused the installation failure.
Is there a way to avoid AutoCAD installation errors entirely?
The most reliable approach is to perform a clean uninstall of any previous Autodesk products before installing a new version, keep Windows and all system components up to date, temporarily disable antivirus during installation, and always run the installer as Administrator. Alternatively, some users switch to CAD software with simpler installation processes — IntelliCAD-based tools like SmartCAD, for instance, use a single-EXE installer with no dependency on Microsoft licensing services or the Interoperability Engine Manager.
