SAP GUI HTML Control Issue / SAP GUI Chrome Issue in SAP GUI for Windows – schnelle Workarounds & Fix

Fixed! Windows Update SAP GUI issue. WebView2 Update 144.x: The problem with SAP GUI – and how to solve it.

Since January 20, 2026, the WebView2 Runtime 144.x has been causing real frustration in day-to-day operations in SAP GUI for Windows: buttons stop responding, views turn blank, and key transactions such as SM50, SE80, RZ11, or SBWP become a source of errors.

We explain what’s behind it—and how you can fix the issue quickly using official SAP options or a proven registry workaround. Good to know: Our current status C connect:IT, status C store:IT and status C scan:IT versions as well as all other software products from the Connected Warehouse are not affected.

Our authors and experts

Pascal Contursi

Business Development & Digital-Marketing

Author

Elias Tilegant

Development SAP

Expert
Last updated on 29.01.2026

WebView2 Update 144.x: What happened?

Microsoft has rolled out an automatic update of the WebView2 Runtime to version 144.x. According to SAP, this is an issue caused by a third-party product. Microsoft is working on a fix with Priority A (Ticket TrackingID#2601200050000910).

When will the fix be released? Microsoft has documented the bug in the Known Issues list for Edge version 144, but without an official workaround. A specific release date for the fix is currently unknown.

Affected: SAP GUI for Windows — independent of release/version (all versions as long as Edge/WebView2 is used as the browser control).

For companies relying on SAP GUI in daily operations, this means:

  • Reduced productivity due to non-working HTML controls

  • Blank screens in critical transactions

  • Action required to adjust the browser-control configuration

Typical symptoms at a glance

  • Unresponsive links and buttons: clicks on HTML controls have no effect

  • Blank displays: ALV headers in SM50, dropdown lists in SE80, and content in RZ11 are missing entirely

  • Blank workflow pages: detail pages and status views stay white/empty

  • Affected transactions: SM50, SM51, SE80, RZ11, SU53, SBWP, SOST, and others

How to check your WebView2 version:

(Get-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\Clients\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}" -Name pv).pv

If the output shows a version starting with 144., you are affected.

Do you require assistance? Contact us!

Official SAP workarounds:

SAP recommends the following solutions in Knowledge Base Article 3704912:

Option 1: Switch browser control to Internet Explorer

SAP Logon → Optionen → Interaction Design → Control Settings → HTML Control → Browser Control → "Internet Explorer"

  • Advantage: Quick to implement, no prior technical knowledge required

  • Limitations: Some transactions such as /UI2/FLP, WebGUI or SOAMANAGER require Edge.

Option 2: Fallback configuration for mixed operation

If you use both affected transactions and edge-dependent applications, you can set up a fallback configuration. For details, see SAP Note 2957665.

Requirements:

  • SAP GUI at least SP007

  • SAP Note 3153691 installed

Option 3: Reset WebView2 to version 143.xxx

If you have any questions about downgrading, SAP recommends contacting Microsoft directly (ticket tracking ID#2601200050000910).

Our recommendation: The registry workaround.

If switching to Internet Explorer was not successful in your case—or isn’t an option—we recommend the following registry workaround. In our tests, this workaround worked reliably and is quick and easy to implement.

Step-by-step instructions:

Step 1: Open Registry Editor

Press Win + R, type regedit, and confirm with Enter.

Step 2: Navigate to the correct path

SAP GUI Version 64-bit --> HKEYCURRENTUSER\Software\SAP\General

SAP GUI Version 32-bit --> HKEYCURRENTUSER\SOFTWARE\WOW6432Node\SAP\General

If the General folder does not exist, create it: right-click → New → Key → enter the name General.

Step 3: Create new value

  1. Right-click in the right-hand pane → New → DWORD value (32-bit)

  2. Enter name: OldCustomURISupport

  3. Double-click on the new value → Enter value 1 → OK

This will then produce the following result:

Step 4: Restart SAP GUI

Close SAP GUI completely and restart it. It is not necessary to restart Windows.

Reversing the workaround:

Once Microsoft provides a fix, you can remove the registry entry or set the value to 0.

Note: This workaround comes from the community and is not officially documented by SAP.

Let's talk!

References and further links

  • SAP KBA 3704912 – Main article on the issue (SAP Support Portal)

  • SAP-Note 2957665 – Browser Control Fallback Configuration

  • SAP-Note 3153691 – Fallback mechanism troubleshooting

  • Microsoft Known Issues – Edge Version 144 (no official workaround documented)

  • GitHub Issue – MicrosoftEdge/WebView2Feedback #5493

SAP has announced that it will update the KBA article as soon as Microsoft provides a fix.

Questions about SAP GUI or other SAP topics?

Please contact us – we will be happy to help.