Why is a random msi running for standard users the first time they open AutoCAD?

[thielen.adam]

AutoCAD 23 and 25. Just running setup as admin through SCCM deployment. Nothing fancy. Serial key licensing.

UAC prompts for admin credentials, but if UAC is disabled, which it can't be any longer, it works fine.

Can't run this as any other user or it just doesn't work, and just tries to run it again with the standard user. 

How do I stop this behavior?

[jorma_heikkuri]

About two weeks have been gone. Autodesk has released again new update, Sep 25, 2025.

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/After-installation...

So subtle changes I don't see anything new. All of you can start DWG TrueView without UAC prompt after installation.

[bwilkerson]

This is something Autodesk needs to address with a patch that can be installable and distributed. The installer can create the necessary registry keys.  Future installers need to address this issue at the time of the install instead of putting the burden on the schools and companies that use the software.

[bert.vanroosbroeck]

The earlier issue we had with Inventor2026 and Revit2026 was resolved with setting the HKLM\SOFTWARE\Microsoft\Policies\Microsoft\windows\installer\DisableLUAInRepair to 1

But the same issue with Autocad2026 remains as the SecureRepairWhitelist-method did not solve the problem.

[ej25wrx]

Are you certain that you have added the correct Product Code for AutoCAD 2026 in the SecureRepairWhitelist? We don’t currently deploy this version in our production environment, but I can test this out and confirm.

[bert.vanroosbroeck]

The productcode Orca retrieved from the .msi that is lanched (e6a82.msi) is {28B89EEF-9101-0409-2102-CF3F3A09B77D}, which points to Autocad 2026 ENG.
KB5065426 is installed on the machines.

[ej25wrx]

Yep thats correct. I didn’t encounter any issues with AutoCAD 2026 after adding the Product Code to the SecureRepairWhitelist. The only difference is that my environment is currently on 23H2. I’ll test on 24H2 with the patch installed to see if I can reproduce the issue. Silly question but did you check to see if you might have a extra space at the end or at the beggining of the Product code like in this example? If you do, remove them.

[MMishiev]

For me, Civil3D is launching to a domain_username_$ windows user profile when launching. Our machines are in Intune and for so unknown reason it won't launch to our non-admin users account.

[bert.vanroosbroeck]

Oh, I wish it was a typo, but alas, no spaces, the valuename is correct

[mcina]

Thank you for this workaround!!

[mmanousKRX8E]

Autodesk updated their support article today with MSP patches for AutoCAD and Civil 3D 2024 through 2026. I tested the patch for 2025 and it worked. It doesn't use the Secure Repair Whitelist method at all (I deleted those registry values prior to installing the patch). 

Unless they release patches for versions prior to 2024, it looks like we are stuck using the Secure Repair Whitelist in those scenarios. The script that I posted a few weeks back can make that process easier if you have to use older versions of AutoCAD and/or Civil 3D.

[bert.vanroosbroeck]

Yes, the MPS patches did the trick. No more issues for our students (so far 😉 ).

Thank you for the assistance.

[jorma_heikkuri]

Few programs which have the same UAC problem during user's profile creation.

Autodesk support article does not tell anything about DWG TrueView 2023, product version T.222.0.0

DisplayName = Autodesk DWG TrueView 2023 - English

DisplayVersion = 24.2.222.0

Go to folder where is Recap file and double click with the mouse the .rcp file.

Same profile creation case like AutoCAD and DWG TruView.

DisplayName = Autodesk ReCap

DisplayVersion = 26.1.0.205

Same as 2026.1 => 2026 Update 1

[schuhRGNUV]

Trying to deploy AutoCAD 2026 with English and German Language pack.

The MSP only fixes the launch of the English shortcut, not the German one.

[catil25024]

This issue is disrupting daily workflows across multiple Autocad versions. Temporary rollbacks are not realistic for IT teams. A coordinated timely resolution from Autodesk and Microsoft is essential to restore stability and user confidence quickly.

[sarnoldCG9UJ]

I definitely agree that a permanent solution needs to be provided here, instead of workarounds.  I'm holding off until we get a fixed installer that solves the problem at the source, rather than having to patch it afterwards (this was fixed in 3 days by another software vendor I reported the issue to for their product, so I'm not sure why it's taken Autodesk 2 months).  I'm really hoping that whatever their .MSP files are fixing are embedded in the next AutoCAD release, presumably 2026.2.  We're waiting on that so we can avoid requiring post fixes for installs.

[jorma_heikkuri]

Yes you are right. Each software has different product code based on release, product and language.

Autodesk has about 1k software version under support waiting to be fixed. 

Note. The following only applies to software that's been installed in English.

One line from: https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/After-installation...

No updates since Oct 9, 2025.

[rtnascimento]

..

[patrick_seymour]

Attached are our detection and remediation scripts for Intune, if anyone wants to use them. They detect the products installed and add registry entries appropriately.

[robert_jones39WA3]

Does this happen in earlier versions of AutoCAD - 2024? Or does it matter? I only have one student that has an issue and this student has been using it with no issues for the last 3 weeks.  The student cannot access on any computer.

[phil.burchell]

My understanding is that this is a long-standing issue specifically with AutoCAD (and its verticals such as Civil3D) that has only come to light after Microsoft tightened security settings in a recent update for Win11 24H2.

The issue doesn't present in the same form with 23H2 or where 24H2 hasn't received the specific KB update mentioned earlier ... however in our organisation at least, for the past few years we needed to whitelist each new version of ACAD in Applocker before it would run (unlike any other Autodesk app).

I suspect the same problematic secondary installer has been included with previous versions of AutoCAD for some time - at least back to ACAD22 and likely 21 and 20 as well - but it was somewhat benign under Win10 and pre-24H2 versions of Win11.

For your one student with the issue, possible their machine has received that cumulative update (or upgraded to Win11 24H2) recently which would explain the change. You just need to provide one-time Admin creds for UAC on that secondary installer (while in the User's context) for ACAD to launch from then on.