Quote:
Originally Posted by RbnJrg
I think I found the cause of the issue. I had already installed the lasted C++ VS 2015 runtime library. When I installed Sigil 0.9.10, I don't know why, it installed again the Visual C++ Redistributable para Visual Studio 2015. And with that distribution, Sigil didn't run. Then I did the following:
1. I uninstalled Sigil 0.9.10
2. I unistalled MS Visual C++ 2015 Redistributale (x64)
3. I installed again vc_redist.x64.exe
4. I installed again Sigil 0.9.10 and when Sigil wanted to install the C++ runtime library, I aborted the installation and this time, Sigil worked.
It seems that Sigil want to install MS Visual C++ 2015 Redistributale (x64) even when this package is present and updated.
|
I'm doing some testing to find the best solution for this, and I still can't, for the life of me, figure out why the Sigil installer would try to install its included version of the VC++ 2015 Runtime over top of a newer version you have have installed. The only thing I can come up with is that your Spanish version of the runtime must appear to be an older version than the one included with the Sigil installer (or it doesn't use the standard registry locations where Sigil looks to check if the 14.X.XXXXetc runtime is installed (and what version it is).
Could you please tell me: 1) what version of Windows you're using, and 2) what the exact version of the runtime you have installed is?
As for the latter, look at the list of the installed applications in Add/Remove, Apps & Features (whathaveyou) and see what the version string is for the "Microsoft Visual C++ 2015 Redistributable"? You may need to click on the entry to see the exact details.
I'd appreciate it. Adding an option to skip the VC++ runtime install in the Sigil installer is trivial enough (and it will be in the next release), but I'd still like to know what's going on. Those who don't know enough about these things shouldn't have to worry about Sigil potentially breaking their existing runtime installations in the first place.