Interaction with Windows CEIP on Win 7 Pro

We just had a strange tech support issue where a previous version of our application ran correctly, but after installing a new version which includes LimeLM, the application would not launch. The Event Viewer showed exceptions in WS2_32.dll, which StackOverflow led us to disabling the Windows Customer Experience Improvement Program - which allowed our application to launch correctly.

One of the interesting findings was that our application security logging was never being engaged, which meant it was dying prior to that DLL loading. AppSec is one of the first items initialized in our application, so this was dying trying to even load our DLLs apparently.

There has been quite a bit changed in the program, so we aren't certain this has anything to do with LimeLM, but I wanted to see if anyone had any experience or issues with CEIP and LimeLM not playing nicely?

SO article: https://stackoverflow.com/questions/25047316/ws2-32-dll-unloaded-exception-when-using-managed-c-library

Hey Christopher,

We cant reproduce this. Are you using the latest version of TurboActivate? Do you get the same freeze when using the TurboActivate Wizard?

That version of our software was built against 4.0.9.4 of LimeLM, statically linked, using VS2015. Since the customer was up and running, we left that machine alone, and are trying to reproduce it now. I will let you know if we are able to reproduce it internally.

We still have not been able to reproduce this issue, although we have seen it on a second customer's machine. Not convinced it has anything to do with LimeLM at this point, only that our application dies before reaching our LimeLM implementation.

Reply
Discard post