

- #Microsoft kb2538242 keep showing up in updates how to
- #Microsoft kb2538242 keep showing up in updates install
- #Microsoft kb2538242 keep showing up in updates full
- #Microsoft kb2538242 keep showing up in updates software
Re-pack entire folder as a CAB (use Makecab.exe or something like CabPack).
#Microsoft kb2538242 keep showing up in updates software
Unless anybody has those files squirreled away for safekeeping the v7 runtimes would be 32-bit only (I doubt there's any software out there that would benefit from 圆4 v7 runtimes anyway, so only extreme completists would ever want those). v7 once had an 圆4 set of DLL's available from MS when it first introduced 圆4 C++ compilers.but it was only available from them by user request, was never released to the general public, and they stopped distributing it altogether after VC++ 2K5 came out. Unless there's some tiny devil in the details it should be relatively seamless. I believe the files are an exact 1:1 match in name and quantity between architectures based on what the VC++ MSI's look like in Orca. If somebody has a solution to that, it should be pretty easy to just overwrite the 圆4 DLL's.
#Microsoft kb2538242 keep showing up in updates full
I only have to check if v7 has the same bug that the VB6 Common Controls have in which MS violates its own rules by requiring the 32-bit DLL's to be installed in SysWOW64 instead of system32 the way it works with everything else.Ī full True Addon for 圆4 is in the same boat as x86 with that all that ASMS folder legacy stuff. I can't find any documentation online about how that would work.Īs for 圆4 the Mixed Addon can just use the existing 32-bit v7 files with swap-out of an 圆4 switchlesses (like N0ak's).

Unless there's some seamless translation layer in there between the XP-era ASMS folder structure to the Vista/7 method to slot all them in the right place that's going to be a very difficult one.
#Microsoft kb2538242 keep showing up in updates install
The full True Addon I'm not sure about because Win7 does away with the ASMS folders on the install media in favor of slotting every single file in a separate winsxs folder on the image. The mixed addon should be a pretty easy one since v7 is just a file dump and the rest is switchless. Don't have any real intention of maintaining an addon, but it'll get the ball rolling. Haven't quite got it licked yet since I'm on 圆4, but I'll try for it over next several days and post something beta on the Win7 forum.
#Microsoft kb2538242 keep showing up in updates how to
And also don't know how to do mixed RVMI/DXI syntax so wouldn't be a one-size-fits-all (not hard to do, though). I'm playing around with trying to retrofit these, although I don't know how to do uninstallable syntax yet so would be install-only. (In case it's not obvious, you need the x86 variant.Adric wrote:Has anyone implemented the changes needed for these addon runtimes so they can be integrated into Win7 with DXIntegrator or a similar tool? In general, it's safe to install multiple/parallel versions of these files, so anybody having this problem should try that link. A google search for that version number points to for a description (security bulletin) of that precise version the actual download link is buried at. I'm not entirely sure if lists the actual versions required by a file or whatever they resolve to on my computer, but for the GF that comes with Sins, its is linked against (or at least works ok with) the libraries of VC++ 7.6195. The GF exe is a "pure" dotnet app, but (which GF exe probably loads dynamically because it's not listed as a static import thereof) is a mixed (there's some official term for this, but I don't recall it now) binary using both dotnet and VC++ 8.0. Meaning you need to have all the old/buggy versions installed for programs linked against those to work. The way Windows handles this insanity is SxS (side-by-side). Was beginning to think I had something installed that was actually conflicting with it.Īlas every program linked to MS Visual C++ libs needs precisely the version of the libraries (dlls) with which it was compiled/linked against, down to security fix version. C++ alone has close to a dozen different installs.
