Note that there are some explanatory texts on larger screens.

plurals
  1. POKB2465367 and 3rd party libraries
    primarykey
    data
    text
    <p>I'm using third party libraries that I obtained well before KB2465367 came out. My development computer has been updated with KB2465367 so all the binaries I generate seem to now be dependant on 8.0.50727.5592 of the CRT (the 2465367 version of the CRT).</p> <p>Now, when I want to deploy this application I'm using the 8.0 CRT merge module (also updated by 2465367). This installs 8.0.50727.5592 versions of MSVC libraries (like msvcrt80.dll).</p> <p>But, when I run my application on a machine that's never had the VC runtime installed, it complains about "This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem." I've traced this back to a system entry in the event log: "Generate Activation Context failed for C:\Program Files\MyCompany\MyApp.exe. Reference error message: The operation completed successfully." under the source "SideBySide".</p> <p>Of course, this update has basically meant I'm dead in the water.</p> <p>How do I proceed from here? Do my clients need to install 8.0.50608.0 version of the CRT <em>after</em> installing my application because the 3rd party libraries need 8.0.50608.0 and the MSM I used didn't include it?</p> <hr> <p>In my circumstance I'm using <a href="http://lynk.at/lj4Fb5" rel="nofollow" title="How To: Install the Visual C++ Redistributable with your installer">How To: Install the Visual C++ Redistributable with your installer</a> which only describes using a single MSM. It's recommended that a policy MSM also be used to redirect any DLLs dependant on older versions of the runtime. See also <a href="http://lynk.at/jlqsKx" rel="nofollow">http://lynk.at/jlqsKx</a></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload