AutoCAD OEM 2025.1.1 Service Release

In case you have not seen the announcement sent out via email, this is to inform you that we uploaded AutoCAD OEM 2025.1.1 Service Release – All Languages to our Developer Zone.

This version is based on AutoCAD 2025.1.1 and is primarily targeting security vulnerabilities.
The build will include fixes for the security vulnerabilities listed in these security advisories, as well as additional vulnerabilities identified in the last few months.

You can download this service release from Tech Soft 3D Developer Zone.

Please note that the previous AutoCAD OEM 2025 version must be uninstalled before installing this version (25.0.154.0).
You can reuse the serial number received for each language with the original production version of AutoCAD OEM 2025.

Follow these steps:
Start the installation by launching the self-extracting Autodesk_AutoCAD_OEM_2025_1_1_Update <_non-English-version>_Win_64bit_db_001_002.exe

Depending on where you placed the EXE above, you may get this message box:

If so, select ‘Browse file’ and navigate to the extracted folder:

C:\Autodesk\WI\Autodesk_AutoCAD_OEM_2025_1_1_Update <_non-English-version>_Win_64bit_db_002_002\image

Upon successful completion of the installer, you’ll see:

Run the Setup.EXE, enter your #serial when prompted:



Verify you now have V154:
image

1 Like

Our Install went smooth the other day with no issues. Had no issues with building OEM either. Satisfied with this Service Release so far.
Shawn Golden
Microvellum

I’m having issues with resources in this version.
AcBrandRes.dll contains no resources after the build, and the splash screen and icons are missing. Replacing the file with an old version works..

There are no changes to the OEM Make Wizard settings other than we have changed the company name, and downgraded Visual Studio to Professional (from enterprise).

There are no errors or warnings in the AcBrandRes_output.log.

Best regards,
Øystein Wiger
Sogelink Norway

1 Like

I did not have anything like that happen this year but in the past I had a similiar issue. Two things I would recommend would be to:

  • Check that your Microsoft Visual Studio Location is set correctly after the upgrade. Keep in mind your folder will be different based on the Visual Studio you used but you should be able to find it either way.
  • Sometimes the Toolkit folder needs to be refreshed\rebuilt. I typically will go in and make a small change in each category especially in the User Interface area and save those changes and then change it back and save. This will refresh\rebuild the Toolkit folder.
    Try to build after that.
    Shawn
    Microvellum