We are getting pretty well the same error with the latest version. However the rundll32 sub-process now exits and the parent call fails to GetProcessById.
*CAVEAT* we are running a test program instead of our full product (which produced the previous error).
We snooped into the process activity using procmon and see some other security software 'Digital Guardian Agents'
https://digitalguardian.com/products/digital-guardian-agents/windowsThere is also something called Tanium (which sems to be remote management software).
We did not get the custom dialog, but a generic Windows unhandled exception dialog.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Exception: ProcessLauncher failed:System.ArgumentException: Process with an Id of 7320 is not running.
at System.Diagnostics.Process.GetProcessById(Int32 processId)
at EO.Internal.jh.a(String[] A_0, String A_1, String A_2, String A_3, String A_4)
at EO.Internal.jh.a(String A_0, Boolean A_1)
at EO.Internal.jh.a(String[] A_0, String A_1, String A_2, String A_3, String A_4)
at EO.Internal.aat.a(String A_0, String A_1)
at EO.Internal.av2.a()
at EO.WebEngine.Engine.Start()
at EO.Internal.co..ctor(WebView A_0)
at EO.WebBrowser.WebView.v()
at EO.WebBrowser.WebView.Create(IntPtr hWnd)
at EO.WebBrowser.WinForm.WebControl.a(Object A_0)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
BrowserTest3
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Public/Documents/BrowserTest/BrowserTest3.exe
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34251 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34270 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
EO.WebBrowser
Assembly Version: 15.3.43.0
Win32 Version: 15.3.43.0
CodeBase: file:///C:/Users/Public/Documents/BrowserTest/EO.WebBrowser.DLL
EO.Base
Assembly Version: 15.3.43.0
Win32 Version: 15.3.43.0
CodeBase: file:///C:/Users/Public/Documents/BrowserTest/EO.Base.DLL
EO.WebEngine
Assembly Version: 15.3.43.0
Win32 Version: 15.3.43.0
CodeBase: file:///C:/Users/Public/Documents/BrowserTest/EO.WebEngine.DLL
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.