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

Just wanted to circle back to this for ​@mikey and ​@deric incase you were not aware, on Thursday release notes were sent out for a minor release to the client v25.2.40

I have noticed that this new release is so far working for me on the items I was having the issues with prior to v25 releases.

Hello all , really helpful topic. 

We have same issue with dlls failing to register once updated to 25.2.11  . But the issue won’t resolve with Privilege Management for Windows  v25.2.40 update.

It won’t resolve even with the EnabledDriverFeatures DWORD set to Decimal set to 127

we downgraded to 24.8 and it resolved only then.

But there is the security risk with old version: Advisory ID: BT25-01 | BeyondTrust

so now i am confused what next steps to take.

     KindRegards,

Nicolas

Hey ​@Nicolas I hadn’t tried registering dll’s outside of elevated software installations… I know in talking with support before they released 25.2.40 there was 2 options, but neither was acceptable for my organization as they both indeed opened the vulnerability back up again.. 1 was downgrade, and 1 was a registry setting change which essentially did the same thing as downgrading in regards to the vulnerability…

My recommendation if you haven’t yet, open a support case… describe the problem and what you have attempted to do to resolve it, this way they can capture the as much detail to get the information back over to the engineering team…   

I will admit for my various systems I was bouncing them between v25.2.1 and v25.2.11 and did upgrades from both version to v25.2.40

I know my organization has a few use cases around dll registration, so I’ll start down that path again and see what I can do...

hi Mike,

 had some good progress today.

on our BeyondInsight Main Appliance Updated Endpoint Privilege Management Webpolicy Editor Bundle to 24.5.0 and then retested two scenarios:

1) applied EnabledDriverFeatures DWORD set to Decimal set to 127 - issue resolved for users calling vbscript/dlls via Visual Studio IDES, but does not get resolved for people manually clicking right-click run as administrator on regtool.exe. Same error as before 

2)updated again the agent to 25.2.40 - issue resolved for users calling vbscript/dlls via Visual Studio Code, but does not get resolved for people manually clicking right-click run as administrator on regtool.exe. Same error as before

Error example:

The following 6 libraries failed to register:

1.dll

2.dll

3.dll 

4.dll

5.dll

6.dll

kind Regards,

Nikola