Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to manually update the WebView2 Runtime? #3371

Closed
ajtruckle opened this issue Apr 8, 2023 · 6 comments
Closed

How to manually update the WebView2 Runtime? #3371

ajtruckle opened this issue Apr 8, 2023 · 6 comments
Assignees

Comments

@ajtruckle
Copy link

ajtruckle commented Apr 8, 2023

User is running Windows 10, 64 bit.

My application won't run and shuts down.

They are using:

  • WebView2 Runtime Version: 108.0.1462.54
  • WebView2 SDK Build: 1661.34

I am using:

  • WebView2 Runtime Version: 111.0.1661.62
  • WebView2 SDK Build: 1661.34

There is quite a difference between 108.0.1462.54 and 111.0.1661.62. How can I get it up to date?

@ajtruckle
Copy link
Author

ajtruckle commented Apr 8, 2023

Think I found the solution on the internet:

To install or update the WebView2 Runtime:

  1. Go to page https://developer.microsoft.com/en-us/microsoft-edge/webview2/.
  2. Scroll down to section Evergreen Bootstrapper, select Download > Accept and Download.
  3. Find the executable file in your Downloads folder, right-click it and select Run as administrator.
  4. Enter your administrator credentials. The installation starts and is completed in the background.

After I ran this my runtime went from 111.0.1661.62 to 112.0.1722.34. I am now checking with the user in question.


By the way, according to this link it does say:

To keep WebView2 up to date with the latest security and reliability updates, WebView2 Runtime uses its own automatic update process, separate from the update channel used by Microsoft 365 Apps. WebView2 Runtime is updated approximately a few times each month. Updates usually range in size from 5 MB to 30 MB, depending on the type of update. Differential updates and Delivery Optimization are used where possible. For information about managing these updates, see Managing WebView2 applications.

@ajtruckle
Copy link
Author

ajtruckle commented Apr 8, 2023

The user has now managed to update to the latest runtime and my software runs again. This begs the question:

Why was his runtime not up to date if the operating system is supposed to manage it? 🤔

@ajtruckle ajtruckle changed the title How to force WebView2 to update on users PC? Critical issue for user. How to manually update the WebView2 Runtime? Apr 8, 2023
@sln162
Copy link

sln162 commented Apr 8, 2023

According to my current test, WebView2 is installed on the Win10 machine through Edge's task plan/service (the actual test should be task plan) #3317

I guess that the relevant task plan may not be executed, or EdgeUpdate is not installed or the file is missing

@novac42
Copy link
Contributor

novac42 commented Apr 11, 2023

@ajtruckle Can you collect the installation log?

@ajtruckle
Copy link
Author

@novac42 We have asked this before. There is no simple way to obtain a log.

@LiangTheDev
Copy link
Member

WebView2 Runtime is designed to auto update, using scheduled tasks. Auto update would not work if the IT admin setup policy to block it, those scheduled tasks are disabled. We need Edge update/installer logs to tell us what's going on.

@MicrosoftEdge MicrosoftEdge locked and limited conversation to collaborators Oct 10, 2023
@victorhuangwq victorhuangwq converted this issue into discussion #4036 Oct 10, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants