While the source of this issue is Microsoft, I suggest that Sage look at a more permanent fix to the help file issue so they are not at the mercy of Microsoft.

It is now out there both Windows 7 and Windows 10 machines not longer recognize the "white list" fix mentioned in Sage Customer Support (Error: "Page Cannot Be Displayed" message when accessing F1 help). For Windows 7, the issue appears to be the result of KB4284826 (https://support.microsoft.com/en-ca/help/4284826/windows-7-update-kb4284826) or KB4103712 (https://support.microsoft.com/en-ca/help/4103712/windows-7-update-kb4103712). For Windows 10, this can be imbedded in various updates. It is acknowledged that this issue affects all network CHM files and is not technically a Sage problem.

I would suggest, however, that Sage consider "alternative" fixes IF Microsoft does not fix this issue in a timely manner. Play out the what-if scenarios. All Sage customers are going to be without F1 help for months? a year until Microsoft fixes the issue? If I was Sage, I would want to make sure from the Sage perspective that "my customers" were looked after and I would be trying to get weekly updates from Microsoft (not sure if that is realistic) to ensure that they are still committed to fixing the problem (they acknowledge this as their issue). I suggest coming up with a Plan B if I was not getting warm fuzzy feelings on this from Microsoft.

Plan B could include one of the two alternatives:

1)changing the help files to be local and update the WSSetup files to install them and for the executables to call the local help files.

2) change the CHM help files (which seem to be in serious decline and falling out of favour), to HTML help, which could be stored on the network.

Right now, Sage is at the mercy of Microsoft and we the customers are left "waiting" and without F1 support.

Sage support has been good at handling the concern but it beyond their control.

The issue needs to be fixed and quickly. I recommend Sage take control of the issue and own the fix instead of waiting for Microsoft. Forget registry hacks and white lists. Both of the proposed solutions take ownership and control.

I would be willing to speak to anyone at Sage about this issue is I have not articulated my thoughts clearly.

by: Michael S. | over a year ago | General Enhancements