Skip to main content
N
NDRHelp
Inspiring
July 16, 2019
Answered

After applying Windows kb4507460 update, help calls from our application cause the application to crash

  • July 16, 2019
  • 2 replies
  • 1894 views

We are running RoboHelp 2015 and are creating responsive HTML 5 output. We publish our help on the RoboHelp server and also have a copy installed locally on the machine where the application is installed.

We have a password on the RoboHelp server that we pass in the call from the applications and if the server is not available, we fail back to the locally installed help. We call the same help from our Windows GUI and our browser application.

After installing the Windows update mentioned in the title, when we attempt to call help from our Windows GUI, the help and GUI crash. Calling help from our browser application works just fine. If we uninstall the Windows update, the help call from the Windows GUI works again.

From the details on the Windows update, it appears that one of the areas worked on was security. One of our developers suspects how RoboHelp authenticates using cross-origin resource sharing. Cross-Origin Resource Sharing (CORS) - HTTP | MDN

Is anyone else having issues after this Windows update? As far as I know we are following RoboHelp's instructions for the help call.

This topic has been closed for replies.
Correct answer rami

The KB4512517 update, released today, has resolved the issue.

2 replies

rami
ramiCorrect answer
Participant
August 13, 2019

The KB4512517 update, released today, has resolved the issue.

S
Community Manager
Stefan GentzCommunity Manager
Community Manager
August 14, 2019

Hi Rami,

as Microsoft Update KB512517 solved this issue, I have unmarked your first answer with the Registry change, and marked your other one with KB512517 as correct, as I think it it makes mores sense to refer to a regular Windows upate for this problem. Hope that's okay for you.

rami
rami
Participant
August 14, 2019

Thank you.

rami
rami
Participant
July 18, 2019

Hi @NDRHelp,

See Unhandled exception in jscript9.dll in Windows Server 2016 when using MFC's CDHtmlDialog, after installing Microsoft upd…

As a work-around, try setting the following registry value:

 

Key: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\Main
Value: Disable Script Debugger
Type: REG_SZ
Data: no

Hope that helps!

N
NDRHelpAuthor
Inspiring
July 18, 2019

Thank you! That fixed it!

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices