Autodesk Licensing Did Not Install- Error Code 240 | Fix

Guide / By

Error 240 means the Autodesk Desktop Licensing Service failed; reinstall the service and reset permissions to finish installation.

If a setup stops with the message autodesk licensing did not install- error code 240, the installer can’t register or start the Autodesk Desktop Licensing Service. Without that service, products like AutoCAD, Revit, and 3ds Max won’t complete setup or activate. The good news: in most cases you can clear the block by removing old licensing bits, installing the latest service build, and making a few quick checks on Windows.

Autodesk Licensing Did Not Install — Error Code 240: Fixes That Work

Start with the fast wins. These actions resolve the bulk of 240 failures across recent Autodesk releases.

  1. Close Every Autodesk App — Exit installers, Autodesk Access, and background tools. Open Task Manager and end stray AdskLicensing, Genuine Service, or product processes.
  2. Reboot Once — A session clears locked files and stale services that can block the licensing installer.
  3. Run The Installer As Admin — Right-click the setup EXE and choose Run as administrator so Windows grants service install rights.
  4. Temporarily Pause Security Tools — Endpoint protection can block service writes. Pause real-time scanning for the install window, turn it back on.
  5. Install From A Local Folder — Move the package to a local path with short names (e.g., C:\Autodesk\Setup) to avoid path and permissions snags.

What Error 240 Means And Common Causes

On current installers, Error 240 maps to problems installing or initializing the Autodesk Desktop Licensing Service. Typical root causes include:

  • Outdated Licensing Service — An older AdskLicensing build remains and conflicts with the new product installer.
  • Service Not Running — The service install succeeds, but the Windows service fails to start during setup.
  • Missing Version Metadata — The installer can’t detect the installed service level and halts.
  • Insufficient Rights — The user lacks the policy right to create services or symbolic links, which some installers require.
  • File Locks Or Corruption — Residual files in shared folders stop the new components from registering.

Next, walk through a precise cleanup and reinstall of the licensing component. This step removes conflicts left behind by old builds.

Clean Reinstall Of The Licensing Service

Do a quick check first: If you already tried a regular uninstall, do a complete service cleanup and then install the latest build before rerunning product setup.

  1. Uninstall The Existing Licensing Service — Open C:\Program Files (x86)\Common Files\Autodesk Shared\AdskLicensing and run uninstall.exe as an administrator. Wait until the folder empties.
  2. Download The Current Service Build — Get the latest Autodesk Licensing Service update from Autodesk, then extract the ZIP. On the EXE’s Properties, unblock if Windows shows the security banner.
  3. Install With Admin Rights — Run AdskLicensing-Installer.exe as administrator and let it finish. The Windows service should be set to Automatic (Delayed Start).
  4. Verify The Service — Open services.msc, find Autodesk Desktop Licensing Service, confirm the Startup type and Status show the service set correctly, then start it if it’s stopped.
  5. Retry The Product Setup — Launch the product installer from a local folder. If you use Custom Install, refresh the package after the service update.

The uninstall tool inside the AdskLicensing folder removes every registered licensing component for current product lines. Using that tool is safer than manually deleting files, and it resets the service so the next installer doesn’t trip over stale entries. After reinstalling the service, confirm it starts without errors before you run the product setup again.

When downloading the new service build, prefer the official update page. Autodesk posts release notes and the current installer there, which helps avoid old packages mirrored by third parties. Keep the ZIP in your local cache so you can reuse it across machines without another pull.

This fresh install resolves a large share of error 240 cases because it replaces legacy files and ensures the service can start cleanly.

Permissions, Policies, And Dependencies To Check

Some systems block service registration or startup by policy or by missing runtime pieces. Run the checks below before your next attempt.

  • Confirm Admin And Service Rights — Use an admin account. In corporate domains, ensure no software restriction policies block service creation or installers.
  • Set Startup To Automatic (Delayed) — In services.msc, set Autodesk Desktop Licensing Service to Automatic (Delayed Start) and start it.
  • Install WebView2 Runtime — If required by your service version, install the Microsoft Edge WebView2 Runtime, then reboot.
  • Keep Access Online — If you install via Autodesk Access or Desktop App, update Access first so it can stage the licensing files correctly.

Group Policy and endpoint tools often change the ground during big rollouts. A small setting can block service creation or delay a start long enough to trigger a timeout. Before a second attempt, double-check policy templates applied to the device and the installer account. If your org denies local service installs, schedule a temporary carve-out for the install window or run the job under a build account with the needed rights.

The WebView2 runtime shows up in many Autodesk notes because modern installers embed web components. If that runtime is missing or out of date, the service UI may fail to render during setup. Installing the evergreen runtime closes that gap in minutes.

Enable Create Symbolic Links

  1. Open Local Policy — Press Win+R, type gpedit.msc, and press Enter.
  2. Navigate To The Setting — Go to Computer Configuration → Windows Settings → Security Settings → Local Policies → User Rights Assignment.
  3. Edit Create Symbolic Links — Add Administrators or your installer account. Apply changes and reboot.
  4. Retry The Install — Run the service installer as admin, then start the product setup again.

If It Still Fails: Logs And Extra Repairs

Try a deeper fix if you still hit Error 240 after the clean service install. The steps below resolve edge cases seen on current releases.

  1. Reset The Licensing Folders — Empty cached licensing data under C:\ProgramData\Autodesk\ADLM and C:\ProgramData\Autodesk\CLM if present, then reinstall the service.
  2. Create The Version Metadata — Some older updates expect a version.ini file under the service path. If Autodesk guidance calls for it, create the file with the current version string so the installer can proceed.
  3. Use The Microsoft Install/Uninstall Troubleshooter — Clean stuck entries that hide in Programs & Features, then reinstall the service and product.
  4. Switch The Delivery Method — Try Browser Download instead of Access, or vice versa. For deployments, rebuild the package after updating the service.
  5. Reinstall .NET And Repair VC++ Runtimes — Damaged runtimes can break installers. Install current .NET and Visual C++ redistributables from Microsoft, then retry.

Logs matter on stubborn cases. A quick scan often surfaces a simple clue like an access block or a missing file. If you use a deployment tool, pull both the ODIS logs and the tool’s job log so you can line up timestamps.

Switching delivery methods helps when a stager times out. Browser Download gives you the full package that installs offline, while Access streams parts and expects a steady link. If a proxy or filter slows the stream, the offline route usually lands cleanly.

Version metadata matters on some updates. When the service can’t read a current version, the product installer may pause with 240. Adding a small version.ini with the current number lets the next step continue. Only do this when Autodesk notes call for it on your release.

Read Logs To Pinpoint The First Failure

  1. Open ODIS Logs — Go to %localappdata%\Autodesk\ODIS\logs and open the newest file in a text editor.
  2. Search For AdskLicensing — Jump to the first occurrence around the failure time. Lines mentioning service start, file copy, or version checks tell you which action failed.
  3. Correlate With Windows Logs — If you see Access denied or service start timeout, cross-check Event Viewer to see which restriction fired.

Admin Notes For Deployments & Preventive Steps

IT setups add layers that can trigger Error 240 during mass installs. If you deploy through SCCM, Intune, PDQ, or a login script, bake these items into the task so the service lands correctly every time.

  • Install Service As A Prerequisite — Push the current AdskLicensing package first, then the product. Mark the product task dependent on the service task.
  • Use Silent Switches — The service installer accepts quiet flags. Run it elevated with logging so you can audit failures later.
  • Refresh Custom Installs — Rebuild Custom Install packages after a service update so they ship the new files to endpoints.
  • Avoid UNC Paths On First Run — Extract to a local cache before install. Long UNC paths can confuse older stagers.
  • Open Required Domains — Allow licensing URLs in your web filter. If named users can’t reach sign-in endpoints, first-run checks may stall.
  • Delay Antivirus — For the deployment window, use a policy that relaxes scanning of installer folders so service files can register.

After deployment, build a small verification script that checks the service status, confirms the version string, and writes a line to a central log. That tiny step saves hours later when a shop floor PC fails to activate during a rush job. Many admins also keep a cached installer share inside each site so remote teams don’t wait on a slow WAN link. That keeps installs smooth under load.

Troubleshooting By Symptoms

Match what you see to a likely cause and next step. This saves time when logs are noisy.

Symptom Likely Cause Next Step
Installer reverses progress near “Licensing” Old service or blocked startup Run the service uninstall, install the latest build, set to Delayed Start
Setup ends with Exit Status 2 Service files didn’t register Install from local path as admin; confirm service is running
Products won’t launch after install Licensing not initialized Start the service in services.msc; repair the service package

These mappings steer you straight to the next action without diving through long logs on busy project days too.

Step-By-Step Summary You Can Follow Right Now

  1. Close Autodesk Tools — Quit installers and background processes.
  2. Uninstall The Service — Run uninstall.exe from the AdskLicensing folder as admin and wait until it’s empty.
  3. Install The Latest Build — Download the current Autodesk Licensing Service and install it as admin; set Startup to Automatic (Delayed Start).
  4. Reboot — Start fresh so the service registers and runs.
  5. Run The Product Installer — Install from a local folder. If it still fails, check policies for Create symbolic links and repeat.

With the licensing component refreshed and policies aligned, most installs finish cleanly on the next try. If you still see autodesk licensing did not install- error code 240, review logs for the first failure line and match it to the fixes above. That confirms the repair worked across setups well.