We are having similar problems, with a similar ticket open with support. The answer I got from them was to downgrade the client to 24.8, and they have passed this information to their developers to work on a fix. No ETA from them at the present though for how quickly they will get this resolved.

Thanks for your reply Deric. 

We did update to the latest version due to a vulnerability that is in versions prior to 25.2 that they announced here: Advisory ID: BT25-01 | BeyondTrust

regards

Michael
 

We upgraded as well because of this advisory as we had a hard deadline date to have this completed internally, and since then I’ve been having the same battles trying to figure out applications that previously worked that are no longer working as intended. I am glad to know its not just me… 

I’ve tried various registry elevations with various tokens and custom tokens and so far I was striking out… I was getting close to opening a case with BT Support… but given this is a known issue I guess I’ll just be getting one out there for them to escalate over to the devs :D 

​@deric Just wondering if they have given you anymore insight into this? I did also open a case and offer to work with the Devs around this to give them any additional information or logging they might need. My organization is unfortunately not able to downgrade due to the security advisory, so we are in limbo right now.

Hi ​@MikeK, the last word I got from support was as follows:

“I fully understand where you're coming from here and apologize for the inconvenience. It is safe to assume that the fix will be included in our next client release, I just cannot provide a specific timeframe for you.

We do have a KB article on this, it will be updated as more information becomes available.
KB0022120 : DLL registration policies cause failures with error "The module <path> was loaded but the call to dllregisterserver failed with error code 0x80070005"”

Ironically a different KB than what I was sent :D Endpoint Privilege Management - EPM-W client failing to install "Error 2738. Could not access VBScript run time for custom action" Which this KB could have helped, however, All of my organizations machines are still on Win10 as we are just starting up a pilot for in place upgrade to win11