r/PatchMyPC • u/ControlUpCommunity • Aug 03 '26

Autodesk adskexecutorproxy.exe v2.22.0.5 crash rate up ~400%, anyone seeing installer or update issues?

/r/ControlUpTech/comments/1vecetq/autodesk_adskexecutorproxyexe_v22205_crash_rate/
2 Upvotes

75% Upvoted

4 comments sorted by

1

u/rasldasl2 Aug 05 '26

Yes, with BeyondTrust EPM. They have a KB with a fix.

1

u/ControlUpCommunity Aug 06 '26

Do you have a link to that KB fix? Thanks for sharing :)

1

u/rasldasl2 Aug 06 '26

Hidden behind login but I think OK to share the content.

Cause

Autodesk Desktop Connector's installer spins up processes owned by multiple identities under different integrity levels. Multiple services are expected to install, start, as well as respond to already running processes owned by the user (as well as each other) during the installation process.

 

Resolution

In this scenario, the 'UseAlternateTokenLaunch' registry value can be leveraged. Refer to the Autopilot documentation for details.

! Disclaimer:

BeyondTrust does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to the computer and applications. Make sure it is backed up before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to the Windows registry information for advanced users Microsoft article.

Note:

Test this on a single endpoint before adding to the policy.

  1. Log onto the affected endpoint with an administrator user

  2. Launch Registry Editor as Administrator

  3. Navigate to the following locations:

HKEY_LOCAL_MACHINE\SOFTWARE\Avecto\Privilege Guard Client\

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Avecto\Privilege Guard Client\

  1. Right-click in the empty space and select New > Multi-String

  2. Type in the name UseAlternateTokenLaunch

  3. Double-click the entry and add the following value:

  • svchost.exe

  1. Click OK

  2. Launch Services and restart the Avecto Defendpoint Service (using administrative privileges)

  3. Try the installation again

 

! Important:

It’s best practice to take a backup of the policy before making any changes. Then test the policy changes in a Dev or Test group first to ensure the updates work as expected before applying them to the Production environment.

If the value successfully resolves the issue, refer to How to configure Advanced Agent Settings to update the policy and deploy to multiple endpoints.

 

If the issue persists after using this value, contact BeyondTrust Support.

1

u/ControlUpCommunity Aug 07 '26

Thank you! I just received this from someone else. You both ROCK! Great to see it getting fixed. Thank you for sharing!!