MicrosoftEdge / MicrosoftEdge/WebView2Feedback

GetAvailableBrowserVersionString with fixed version deployment fails on Windows Server 2012R2

Open
#2,025 13 comments 0 reactions 1 assignee View on GitHub

@champnic is already working on this.

Since Dec 16, 2021.

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

Description

Description
During application startup we call GetAvailableBrowserVersionString using a relative path (e.g. path/to/runtime) to a folder containing the fixed runtime. On Windows Server 2012 R2 the call throws the error that I've included below. The error does not occur on Windows 10 or Windows 7. The error also never occurred with the previous runtime (runtime 94.0.992.31, sdk 1.0.902.49). I have not yet tested whether it will still run since our application exits if it doesn't think a valid runtime is available.

System.Runtime.InteropServices.COMException (0x80070032): The request is not supported. (Exception from HRESULT: 0x80070032)
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at Microsoft.Web.WebView2.Core.CoreWebView2Environment.GetAvailableBrowserVersionString(String browserExecutableFolder)

Version
SDK: 1.0.1054.31
Runtime: 96.0.1054.43 x86 (from Microsoft.WebView2.FixedVersionRuntime.96.0.1054.43.x86.cab)
Framework: WPF (targeting .NET 4.6.1)
OS: Microsoft Windows Server 2012 R2 Standard, Version: 6.3.9600 Build 9600. Running on EC2. (.NET 4.8 release 528049)

Repro Steps
On Windows 2012 R2, call GetAvailableBrowserVersionString pointed at a folder containing fixed runtime 96.0.1054.43 x86.
Should return the available runtime, instead throws exception.

Additional context
Application is installed as a user install running from %localappdata%\Programs\CompanyName\AppName, running as administrator did not change results.

AB#37425847

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.