Skip to Content

The Windows 10 so called “Creators Update” from March 2017 caused several problems with rendering Webdynpros. One affected transaction is for example: SOAMANAGER.

Affected SAP releases are 7.31, 7.02 with SP 18. Not affected: 7.4x and 7.50.
(this list is not complete!)

Another problem was reported with transaction “nwbw”, it also didn’t render correctly anymore.

Solution for all issues was to apply Microsoft KB 4016240.

See: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB4016240

This is the cummulative rollup patch from April 2017.

 

 

 

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Ichsan Basarif

    Thanks for your help, and I did what you told me, for some reason giving me error message “The update is not applicable to your computer”

    I have  SAP 8.8 PL 18, we are in the process of migrating to SAP 9.2, so for now we are still using SAP 8.8, I noticed after windows 10 upgrade to latest build (build 1703) from build 1607, we have some problems with SAP 8.8:

    • Opening print window when click the preference it crashes the SAP
    • Opening print window when choose primo pdf (pdf maker) it also crashes the SAP

    If you have updates regarding this issue, please share, or anyone in this community able to help.

    Thank you

    (0) 
  2. Ichsan Basarif

    I just read your post again, I like to add up to your list:

    • SAP 8.8 pl 18-on print dialog window when click preferences with selected printer it will crashes the SAP with event viewer message: faulting module name: b1_engines.dll
    • the same thing when we choose primo pdf(pdf maker) from print dialog box, but not all workstation has this problem

    Thank you

    (0) 
  3. reyar malik

    Lots of people, including myself, are having big problems trying to update Windows 10 to the Fall Creators Update. We all get error message 0xc00000bb when trying to reboot to install the FCU. It seems as though almost all the people have the same thing in common: ASUS X299 MOB, a Samsung NVMe SSD, and lots of us also seem to have SATA drives with the SSD. due to this i am unable to use Nox

    (0) 

Leave a Reply