MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: Watchguard VPN SSL Client with SAML is no longer working

Open
#5,337 5 comments 2 reactions 1 assignee View on GitHub

@prija-microsoft is already working on this.

Since Oct 14, 2025.

bug
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

Watchguard VPN SSL Client with SAML is no longer working since Edge WebView2 139 (08.08.2025)

Only extracting the 138.3551.121 to a folder and run setx WEBVIEW2_BROWSER_EXECUTABLE_FOLDER "C:\WebView2_Fixed\138.0.3351.121" /M solved the issue as a workaround.

Importance

Blocking. My app's basic functions are not working due to this issue.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

139.0.3405.86

SDK Version

No response

Framework

Win32

Operating System

Windows 11

OS Version

10.0.26100.4652

Repro steps

Open VPN client, check use SAML Authentication, click connect.
Normally a windows would open that let you enter Email and Password and Token. But no windows appears, client stays at "fetching configuration"

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

No, this never worked

Last working version (if regression)

138.3551.121

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.