Error 1603 is not an Autodesk error. It is the Windows Installer’s generic “something failed and I am not going to tell you what” code, and Autodesk’s own documentation says so in one sentence: it “is a generic error generated by the Microsoft Windows Installer (MSI)” and “tends to be system-related, rather than linked to specific software.”
That sentence explains why most fixes you find for it do not work. People post the fix for 1603 as though there were one. Autodesk documents eight distinct causes for the modern installer alone, and a further list for the older one. The install log is the same in every case. Guessing costs you an afternoon; working the list in order costs about forty minutes.
First: which installer are you using?
The wording of the failure tells you which of Autodesk’s two troubleshooting paths applies. Read the dialog carefully before you do anything.
| What you see | Installer | Applies to |
|---|---|---|
| Install error: [Product] — The install couldn’t finish. Error code 1603 | ODIS (the current one) | 2021 releases and newer |
| Installation incomplete. Some products failed to install. followed by Install error 1603: Fatal error during installation. | Legacy installer | Older releases and some deployments |
The setup log records the same thing either way — a line reading Install <Product> <Version> Failed Installation aborted, Result=1603. You will also see 1603 attached to a component rather than the product itself, which is a useful clue: Install .NET Framework Runtime 3.0 Failed or Install Microsoft Visual C++ 2008 Redistributable (x86) Failed Installation aborted, Result=1603 both point at a prerequisite, not at the Autodesk product.
The eight documented causes (2021 and newer)
These are Autodesk’s own eight, in their order. After each one, run the installer again before moving on — otherwise you will not know which fix worked, and you will carry unnecessary changes forward.
1. Corrupted Autodesk Desktop Licensing Service
This is the single most rewarding one to try first, because the fix is self-contained and takes four minutes.
- Open File Explorer and go to
C:\Program Files (x86)\Common Files\Autodesk Shared\AdskLicensing. - Right-click
uninstall.exeand choose Run as administrator. - Wait until the folder is empty. It genuinely empties — if files remain, the uninstall did not run elevated.
- Download and install the current Autodesk Desktop Licensing Service from Autodesk.
- Run the product installer again.
2. Corrupted Autodesk Installer (ODIS)
The installer can itself be the broken component, which is a strange thing to accept but a common one.
- Go to
C:\Program Files\Autodesk\AdODIS\V1. - Right-click
RemoveODIS.exeand choose Run as administrator. - Download and install the latest Autodesk Installer.
- Start the product installation again.
3. Corrupted Microsoft Visual C++ Redistributables
Autodesk products depend on several generations of the C++ runtime at once. If one is damaged, the install aborts with 1603 and no useful message.
- Press Start, type
appwiz.cpland hit Enter. - Uninstall every entry named Microsoft Visual C++ 2xxx Redistributable.
- Reinstall the latest version of each from Microsoft’s official redistributable page.
Two details matter here. Install only the latest build of each version line, not every historical build. And on a 64-bit system you need both the x86 and x64 packages — installing only x64 is a frequent cause of the install failing again in exactly the same way.
4. Missing Windows updates
Check Windows Update for both required and optional updates, install what is offered, and restart. The restart is not optional advice — pending-reboot state is itself a condition that makes MSI transactions fail.
5. Folder redirection
If your Documents or AppData folders are redirected to a network share — common on managed office machines — the installer can fail to resolve a path. Removing the redirection for the duration of the install clears it. This one usually needs your IT team, and it is worth checking early if the same installer works fine on a home machine.
6. Corrupt product registration
Registering the product manually before installation bypasses the failing step. Autodesk documents this under the related exit code: 100, output: (500)(error while saving feature) failure, and the same procedure applies.
7. Security software blockage
Disable or uninstall the antivirus for the length of the installation. If that is not permitted on your machine, add Autodesk’s documented folder exclusions instead. Autodesk maintains a published list of known conflicting applications, and it is worth reading rather than guessing — some endpoint-protection products are named explicitly.
While you are there, make sure the required URLs and protocols are reachable. A blocked licensing endpoint will not stop the install, but it will produce a licensing failure minutes later that looks like a completely different problem.
8. Corrupted installation
The last resort: a full clean uninstall of all Autodesk software, following Autodesk’s clean-uninstall procedure, then a fresh install. This is genuinely last — it removes every Autodesk product on the machine, and you will be reinstalling for the rest of the day.
Extra causes on the legacy installer
If you are installing an older release, Autodesk lists several conditions that do not appear on the modern list. They are all cheap to check.
- A locked file. Something is holding a file the setup needs to overwrite. Close everything running in the background, reboot, and run setup again before touching anything else.
- A full TEMP folder. Setup extracts to the system temp directory and runs from there. Press Start, type
%TEMP%, press Enter, select everything with Ctrl+A and delete it. - Not enough disk space. The catch is that it is the root drive that matters — the one Windows is installed on — and Autodesk’s requirement is twice the size of the setup files, even when you are installing to another drive.
- Files corrupted during extraction. Close virus scanners, browsers and office applications, then restart the installation.
- Short file name creation is disabled. This is the obscure one. Check
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem. A value of0forNtfsDisable8dot3NameCreationmeans 8.3 names are enabled;1means they are disabled and the install will fail. Change it, then reboot before retrying — the change does not take effect until you do.
The order I would actually work through it
Autodesk’s list is complete but not sequenced by effort. If it were my machine, this is the order:
- Reboot and retry. Free, and it clears the locked-file and pending-reboot cases outright.
- Empty %TEMP%, check root-drive space. Two minutes.
- Reinstall the Desktop Licensing Service. Four minutes, and it is the most frequently cited cause.
- Reinstall the Visual C++ redistributables — x86 and x64 both.
- Windows Update, then restart.
- Disable antivirus and retry.
- Reinstall ODIS.
- Clean uninstall everything Autodesk. Only now.
Steps 1 to 4 take under fifteen minutes together and clear the large majority of cases. Step 8 takes an afternoon and should never be step one, which is unfortunately where most forum advice starts.
What will not fix it
A different copy of the installer from a third-party site. This is the most common way a fixable install failure becomes a permanent one. 1603 is a condition on your machine, not a defect in the download — replacing a good installer with an unverified one changes nothing about the cause and introduces a package nobody has checked. Download from your Autodesk Account or Autodesk Access.
Registry cleaners and “1603 repair” utilities. There is no single registry key behind 1603. Tools that claim to fix it generically are guessing at the same eight causes with less information than you now have.
Reinstalling Windows. Autodesk does mention reimaging as a final option for environment-specific failures, but it sits below a clean uninstall, and a clean uninstall sits below everything above.
Common questions
Does error 1603 mean my licence is invalid?
No. 1603 happens during installation, before licensing is checked. A corrupted licensing service can cause it, but that is a broken Windows service, not a problem with your entitlement. Licensing failures produce their own distinct messages after the product is installed.
The error names .NET Framework or Visual C++, not the product. Does that change anything?
Yes, helpfully — it tells you which prerequisite failed, so you can go straight to that component instead of working the whole list. Repair or reinstall the named component, then run the Autodesk installer again.
Is this specific to AutoCAD?
No. The same code and the same causes cover AutoCAD, AutoCAD LT, Revit, Civil 3D, Inventor, 3ds Max, Maya, ReCap and Vault. The prerequisites and the installer are shared across the whole line.
Do I need administrator rights?
For nearly all of it, yes. Running uninstall.exe without elevation is the reason the AdskLicensing folder “will not empty” for a lot of people. On a managed machine you will need your IT team for the redirection and permission steps.
Before you install: check the machine actually qualifies
A surprising share of failed installs are attempts to put a 2026 release on a machine that does not meet its floor. Revit and Inventor both require 16 GB of RAM as a minimum in 2026, and Revit wants 30 GB of disk plus a further 100 GB of temporary space. Our Autodesk 2026 system requirements comparison puts every product’s figures side by side, and it is worth two minutes before you spend an afternoon on the install log.
If the install succeeds and the product then refuses to start, you have moved on to a different problem: see fixing Autodesk licensing errors. And if you are still deciding what to install, the pricing guides for AutoCAD and Revit cover what each licence actually includes.
Sources
The causes and procedures above are taken from Autodesk’s own support documentation, checked on 29 August 2026: “Install error: [Product] The install couldn’t finish. Error code 1603” when installing Autodesk products 2021 or above and “Install error 1603: Fatal error during installation” while installing Autodesk products with legacy installer. Always follow the current version of Autodesk’s own article for your release.
