Skip to Content

SAPGUI (740 & 750) make windows 10 crash after W10 1703 update

Good morning,

After patching W10 to 1703, on edun edition, our Windows client machines crash

when our users try to process workflows in their business workplace.

The problem occurs with 740 patch 13 and 750 windows GUIs.

Have you faced or be aware of similar issues?

Could you provide me more information on how I could diagnose this problem?

Have a good day and thanks in advance for your answers.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

6 Answers

  • Best Answer
    May 31, 2017 at 07:21 AM

    Good morning,

    As I have had no answer on scn, I post the answer from SAP support:

    In this specific case it seems to be a known issue with the creators update from Microsoft.

    Microsoft knows about this issue and there is an open case where you can refer to, when you contact Microsoft:

    Issue 2099418: RS2 RTM: Bluescreen when opening SAP Easy access app

    Regards,

    Add comment
    10|10000 characters needed characters exceeded

  • Jun 23, 2017 at 09:58 AM

    Hi, do you have any feedback? We have the same Bluescreen as far as we move with the mouse over an HTML Inplace section ...

    Add comment
    10|10000 characters needed characters exceeded

  • Jun 28, 2017 at 10:03 AM

    Hi,

    I have the same issue with the scase, in the cases with a Workflow associated.

    Windows crashes with a blue screen at the momento of calling the transaction.

    Regards

    Add comment
    10|10000 characters needed characters exceeded

  • Jun 28, 2017 at 02:21 PM

    I have de same issue here with SCASE also.

    Waiting for the resolution.

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 10, 2017 at 01:48 PM

    Same problem with SEGW transaction with 7.50 patch lvl 1 while entity mapping fields to CDS view

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 12, 2017 at 06:31 AM

    Good morning,

    Our Microsoft support contact person has told us that this should be solved by KB4022716.

    Has someone try to patch with this KB and tested if it solves the problem?

    Which fix/recommendations do you get from your MS support?

    Have a good day.

    Add comment
    10|10000 characters needed characters exceeded