Unable to package Autodesk Revit 2025 and Revit Civil 3D 2025 in app layer

[Corey Stewart]

We've previously been able to package Autodesk Revit and Civil 3D versions into  a new app layer.  However, 2025 version have been problematic.  Regardless if the install is being run from .exe directly or with a deploy package, the installation eventually rolls back and fails.  Logs will fail at different sub-package installs for each install. The issue does not occur when installing into the OS layer, so, I am positive the app layering software is interfering somehow.

 

I am just curious if anyone has been able to install these  2025 apps into a layer before I approach Citrix. I would also like to avoid upgrading ELM to latest version at this time due to the complexity involved with forced appliance migration for next version

 

Current app / ELM version 24.3.2.1021

OS WIn 10 22H2

 

Thanks in advance,

Corey

[Tyler]

We have a support case open now that is seeing this (or a similar issue).

Please trying the following

1. Before doing the install.  Enter regedit on the packaging machine
2. Navigate to HKLM\System\CurrentControlSet\Services\unifltr
3. Create a DWORD value called EnableExtendedDefenderNoiseFilter and set the value to a 0
4. Reboot the packaging machine
5. Try the install now with that setting.
6. If the install works, leave the setting in the registry, as there is a good chance that if that application used it once, it will use it again.

[Corey Stewart]

If it works, would it be advisable to put that registry change in the OS layer?

[Tyler]

No.  The issue appears to be with some of the file names that the install is creating (&&.dyn is what I saw).  That is being picked up by our filter that tries to prevent pollution in layers coming from Defender.  In general, you would want that filter on to try to prevent the pollution.  Since it is unlikely that most apps will see this issue (uncommon file names), it would be better to only disable the filter in the layer that requires it.

[Corey Stewart]

The registry addition appears to be working.  Thank You!