The only difference between them is that the one where LibO fails to install was installed earlier (like 9 months before), and used more, notably for intrusive programming software such as Intel C++ compiler, Visual C++, etc = lots more of VC runtimes installations performed (not to mention the monthly Catalyst updates, which often come with VC updates too). This indeed occurs on one of my PCs, but not the other, although both have the very same version of Windows 7, with the same updates. ![]() ![]() I think that to reproduce it, you'd need to perform the install on a Windows where you've had _a lot_ of VC runtimes installations, reinstallations, updates, etc (so definitely not in some fresh new virtual machine), as per the description of the "solution" on Microsoft's bug page: "This is known issue when installing multiple interim releases."
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |