Skip to Content

Hello Community,

I would like to take the opportunity to announce several important updates regarding the lifecycle of SAP GUI for Windows.

  1. SAP GUI for Windows 7.40 will be out of support by 30th of June 2018 (less than 2 months left). If you are presently using this release, please upgrade to SAP GUI for Windows 7.50 as soon as possible.
  2. SAP GUI for Windows 7.50 is in full support until 9th of April 2019 and afterwards will be in a restricted support mode until 31st of March 2020. We extended this phase by 6 months today due to the announcement listed under “3.”. “Restricted support” means that we will be processing issues just like during mainstream support, but in the rare case that an issue cannot be fixed by us, because it is caused by an error in the C-Runtime belonging to Visual Studio 2013 (which is no longer fully supported by Microsoft after 9th of April 2019) we may respond by saying that an upgrade to release 7.60 is the only available solution.
  3. SAP GUI for Windows 7.60 is planned to be delivered on 25th of February 2019 and will be supported until 12th of April 2022. Originally, we planned to ship the new release in September 2018, but we are facing substantial problems in our migration to Visual Studio 2017. Therefore, we had to postpone the shipment by 5 months.

For those interested in what SAP GUI for Windows 7.60 will bring, I have a list of our key topics here:

  • Accessibility support for Belize theme
  • High Contrast Black and High Contrast White options for Belize theme
  • “Colors in System” for Belize Theme
  • Further Belize theme improvements (SAP Logon, Options dialog,…)
  • Input history in editable ALV
  • Further improvements for SAP Screen Personas 3.0 support
  • Clean-Up (removal of Enjoy theme, no support for saplogon.ini anymore)

Best regards,
Frank Krause

To report this post you need to login first.


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

  1. Matt Harding

    Thanks Frank for the timely reminder (it surprised me).

    I do have one concern though.

    With the delay in 7.60 to a tentative February, it seems a little unrealistic to give Customers less than 2 months to upgrade from 7.50 which is out of support in April to a brand new, not proven release that is 7.60.

    e.g. Packaging of SAPGUI is not a trivial exercise in many enterprises. The need to fully regression test SAPGUI and hence customers preferring to do this change with support packages which are done infrequently at specific times of the year. Many enterprises wanting to wait a patch level or 2 before implementing new functionality.

    All of this makes a month a crazy ask hence if 7.50 support can be extended another 6 months to accommodate the Visual Studio 2017 issues; that would be great.



    1. Frank Krause Post author

      Hello Matt,

      the maintenance of SAP GUI for Windows 7.50 was extended in a restricted mode until end of March 2020 (see my statement above) while SAP GUI for Windows 7.60 will be shipped in February 2019.

      Therefore you have more than one year for the packaging. We are aware that this is not trivial and this is exactly the reason why we always provide an overlap of at least one year.

      Extending the full maintenance period is not possible, because we won’t get corrections for the C++ Runtime from Microsoft after the end of mainstream support for Visual Studio 2013.

      Best regards,

  2. Christian Köhler

    Hi and thanks for the information.

    What does the follwing mean in detail: no support for saplogon.ini anymore.

    How does this work, starting with version 7.60?

    thanks and best regards


    1. Jude Bradley

      Hello Christian,


      As far as I can see, this would mean that only xml files will be created/generated in SAPgui 7.60 and that Saplogon.ini files will no longer be read from.

        1. Jude Bradley

          Yes, Christian.

          In the older (620,640,710) gui, the connection configuration was read from the text-based ini files.

          Now from 7.60, only the xml files will be read or interpreted.


          1. Frank Krause Post author

            Hello Christian,

            with SAP GUI for Windows 7.40 we have introduced the “SAP UI Landscape” format as an optional format for storing the information on connections, shortcuts, message servers and so on in SAP Logon. When you were using SAP GUI and the SAP Business Client, SAP UI Landscape was already mandatory in 7.40 onwards.

            With SAP GUI for Windows 7.50 we made SAP UI Landscape default. This means that since quite some years a replacement for the old saplogon.ini format is available. It works and has become mature. We offer automatic migration from the old world into the new world and there are also tools to support you. I recommend that you have a look at our “SAP UI Landscape Configuration Guide” which is delivered on the SAP GUI DVD (or here:

            The idea behind SAP UI Landscape is having a common configuration for SAP GUI for Windows, SAP GUI for Java and SAP Business Client in a modern XML format (and no more ini files being spread all over the client).

            The meaning of my statement “no support for saplogon.ini” means the following:

            • SAP GUI for Windows 7.60 can still handle saplogon.ini for compatibility reasons (if there should be any external program still needing the old format)
            • If there are issues with saplogon.ini we will not fix them.
            • Installations of SAP GUI for Windows 7.60 must therefore use SAP UI Landscape configuration files.

            Best regards,

  3. Peter Muschick

    It would be great if SAP GUI 7.6 would support multiple displays with different scaling. I do have a very small laptop 13′ screen with Full HD 1080p resolution scaled to 125% and a standard 24′ screen scaled to 100%. SAP GUI messes up nearly every dialog with to small boxes for the content and creates scrollbars everywhere. In small dialogs like CG3Z/CG3Y it even cuts off the complete text.

    There are notes about that – but this is really not working software if modern screen features are not support. I would rather want to skip working on themes than making the current GUI work.


Leave a Reply