* Error on links in KB page for FH Install errors

[jbtapscott]

This was reported on the FH Facebook pages.

The KB page in respect of "Family Historian Installation Problems" https://fhug.org.uk/kb/kb-article/famil ... RgjozrJakY throws a number of 401 Page not found errors in the section on Error 126 - namely, the three links to Microsoft pages all fail.

[ColeValleyGirl]

If somebody tracks down working replacements, the page can be updated.

[tatewise]

I could not find any suitable Microsoft Download links for any Visual C++ packages, not even the latest.
There are plenty from other websites but can they be trusted?

The advice to use Microsoft Visual x86 C++ 2010 Redistributable 10.0.40219 only applies to FH V6 (and maybe FH V5).

FH V7 uses Microsoft Visual C++ 2015-2019 Redistributable (x86) 14.28.29325.2 according to my Windows 10 Settings.

So I guess the advice in the 1st paragraph is Ok but the 2nd and 3rd paragraphs should be reworded to say:

Close ƒh and try reinstalling the ƒh installation file. It may be necessary to use Start > Settings > Apps > Apps & Features to Uninstall the C++ package beforehand (2010 version 10.0.40219 for FH V6 or 2015-2019 version 14.28.29325.2 for FH V7. If unsuccessful then contact Calico Pie for assistance.

[ColeValleyGirl]

I share your reluctance about third-party downloads.

Does https://www.microsoft.com/en-us/downloa ... x?id=26999 look viable for V6?

I can't find anything for v7 that doesn't need a Visual Studio subscription to access.

[tatewise]

That link might be OK for FH V6 but I'm not 100% sure.
I did see the link but was concerned about it being an MFC Security Update dated 5/12/2021.
Anyway, if that link is provided we must give instructions to choose the vcredist_x86.exe download file from the three choices available.
Should we check with CP that it is a viable package for FH V6?

I wonder how many FH V6 users are likely to run into this installation problem.
So are we trying to cater for a small and diminishing user base?

[ColeValleyGirl]

I wonder how many FH V6 users are likely to run into this installation problem.
So are we trying to cater for a small and diminishing user base?

Not sure how small it is -- we likely won't be hearing much from users of V6 who are using it without problems and have no reason to upgrade -- but they're on a stable platform, at least.

I'm coming round to your idea that we change the 2nd and 3rd paras to say:

Close ƒh and try reinstalling the ƒh installation file. It may be necessary to use Start > Settings > Apps > Apps & Features to Uninstall the C++ package beforehand (2010 version 10.0.40219 for FH V6 or 2015-2019 version 14.28.29325.2 for FH V7. If unsuccessful then contact Calico Pie for assistance.

except...

I don't have 2015-2019 version 14.28.29325.2 installed.

I have:

Screenshot 2022-12-27 140706.jpg (67.43 KiB) Viewed 3149 times

so which one should I delete? (Rhetorical question: I wouldn't touch anything without knowing what depends on it).

Plus the version distributed with FH might change.

So any advice to delete the C++ package might be risky.

[tatewise]

I agree we should not suggest to Uninstall specific C++ packages.

Your FH V6 C++ 2010 agrees with mine but I have none of the others installed!
It is fascinating that your recently installed versions are in 32-bit (x86) and 64-bit (x64) pairs when FH only uses 32-bit (x86).
Also, the order of installation is not in ascending version order. I wonder why. Maybe a Windows 10 v Windows 11 difference.

My MS Visual C++ 2015-2019 Redistributable (x86) 14.28.29325.2 was installed on 24/11/2022 when I installed FH V7.0.18.

[ColeValleyGirl]

There are a number of programmes on my PC which might have installed the version they use, and/or piggy-backed on a compatible version installed by another programme. Plus of course Visual Studio will have installed some.

Does this wording satisfy:

Close ƒh and try reinstalling the ƒh installation file. If unsuccessful then contact Calico Pie for assistance.

[tatewise]

That looks good to me.

[NickWalker]

I think the correct place to download the redistributable is: https://learn.microsoft.com/en-us/cpp/w ... w=msvc-170. The link to the specific download would be: https://aka.ms/vs/17/release/vc_redist.x86.exe.

[ColeValleyGirl]

Won't that hit the need for a Visual Studio login, Nick?

Mike T, assuming you don't have such a login, can you try?

[NickWalker]

Won't that hit the need for a Visual Studio login, Nick?

Mike T, assuming you don't have such a login, can you try?

I don't think so. I've just opened it in an Inprivate/Incognito tab and it downloaded OK.

[tatewise]

I can open the link to the website that Nick provided and choose the X86 download from there and also can download the VC_redist.x86.exe file directly using the link Nick provided. I have not tried to install that download file.

Is the suggestion that the VC_redist.x86.exe installation file is compatible with FH V5, FH V6, and FH V7?
Will that continue to be true throughout the lifetime of FH V7?

Are we going too far in offering that download when Error 126 arises rather than redirecting to CP if reinstalling FH fails.

[NickWalker]

I think it would probably be better to suggest they contact CP rather than mess around installing dlls.

[ColeValleyGirl]

I agree with both of you so I've gone with the text from earlier:

Close ƒh and try reinstalling the ƒh installation file. If unsuccessful then contact Calico Pie for assistance.

[Mark1834]

I’ve been surprised in the past by how many different versions of the redistributables get installed by different apps. Ideally, they would always be backwards-compatible, so you only need the latest and greatest, but I know that’s not the case in the real world .

[NickWalker]

I’ve been surprised in the past by how many different versions of the redistributables get installed by different apps. Ideally, they would always be backwards-compatible, so you only need the latest and greatest, but I know that’s not the case in the real world .

Each version of Visual Studio tends to correspond with a new version of the dlls. At least they are now packaging the more recent versions all together in one download