VMware Horizon Community
system32AUT
Enthusiast
Enthusiast
Jump to solution

msedge.exe error, maybe because FlexHook64.dll ?

Hi there,

we might have a Problem since DEM 2111 or DEM 2203 with MS Edge 101 and up.

Some of our 7000 users get an error message when logging off Windows: "msedge.exe - System Error Execution of the code cannot continue because msedge_elf.dll was not found...."

MS Support just wrote me back, quote:

  • "For this issue we have performed an investigation internally. From it, we have concluded that this issue is a side effect of unsupported hooking techniques used by 3rd party software products. More specifically, calls to CreateProcess from the Edge browser process are being incorrectly hooked, resulting in a partially initialized crashpad handler process.The dialog with the error is then a consequence of this fact, since this process does not have the correct data structures in memory to find and load msedge_elf .dll as expected. This issue became more visible since we introduced a crashpad handler process launch optimization (for performance reasons) around Edge 101, creating visible impact to end users because of this unsupported hooking scenario. The only way to ensure Microsoft Edge works as expected is to ensure the mentioned system call hooking is removed, as Microsoft has no way to control the unpredictable array of situations that Windows API hooking/thread injection can create, either in other browser usage scenarios or when we introduce further optimizations (either performance but especially security related). In your case we have identified as culprit to be the below Module provided by VMware DEM: FlexHook64.dll.
  • Moving Forward: Please engage the vendor of the FlexHook64.dll as they must ensure that the mentioned system call hooking is removed. If you manage to have a statement from the third-party vendor in regard to this issue, please let us know if they are recognizing any flaws within their product and if they are committed to fixing it."

Anyone else? @DEMdev  

Thanks,
Dominik

0 Kudos
1 Solution

Accepted Solutions
system32AUT
Enthusiast
Enthusiast
Jump to solution

0 Kudos
1 Reply
system32AUT
Enthusiast
Enthusiast
Jump to solution

well okay... we will try this and after some days I will report here 🙂

 

https://docs.vmware.com/en/VMware-Dynamic-Environment-Manager/2203/com.vmware.dynamic.environment.ma...

 

0 Kudos