Try Installing Edge and then Installing Webview2. I know it says you can run it without Edge but it's worth a try to Install Edge First and then Webview2. Once its is installed try removing Edge and see if it works. Here is some Documentation as well to look at...
-us/microsoft-edge/webview2/?form=MA13LH
I've been redirected(from there) to ask here about one issue I have. Microsoft Edge Webview2 Runtime keeps getting installed on my PC. I can't uninstall it as next day it somehow installs itself back. Can someone please tell me what is going on? I don't use either MS Edge or MS Office so I want a clear answer on what it is and how to stop it.
Thanks in advance
I don't know what is going on but every time my windows starts up windows Edge 0opens on my computer with data and programs to open. I don't use it and it seems to be a bother. I have an understanding that it is call Windows Runtime2 Webview. I have followed instructions on how to uninstall it in uninstall programs but all it will let me do there is change it.. Can anyone give help on this.
I have a usb camera input into my client zoom. The host zoom had stopped and restarted their zoom. I didn't stop my zoom but started another instance. My zoom started flickering. I clicked on task manager and saw two instances of zoom. One had 8 instances of microsoft edge WebView2 and two zooms under it.
I understand the catagorizing of windows vital components as being tied into how the OS operates smoothly, but this is just sus. Why are they integrating their proprietary browser functions to the operation of windows. This just seems like straight up malicious spam. I get it, widgets are flashy, more content shoved in our face to keep us occupied, and that needs curated access to the interwebs, what better way to do it through their browser. What if we JUST DON'T WANT IT? Where's the choice? I would understand if windows was subscription based or free with ads, but really, come on. I don't want your useless garbage that just bloats my hardware. Just another straw to break my back and then I'll finally crawl over to Linux if there's no real solution to this latest scheme.
Edit: Just an FYI, here's a plausible option, since even Ccleaner couldn't handle the job. I used the 4th method to remove the 'Windows web experience pack' and no sign of Webview running anywhere, so a good start.
On our end, when this is stuck at startup, there are a TON of events being logged in Event Viewer showing that the msedgewebview2.exe is crashing. Over and over again. This seems to be what is bogging down the machine really. So even when you disable things in CAD and get it to startup, it's still causing the webview process to crash continually.
While we could rename the exe, I don't think this is a solution and it should be something Autodesk seeks to resolve correctly. What if we actually want to use the startup page? What else are we "breaking" when disabling this Windows application tool (Autodesk or otherwise)?
Thanks for the info @BhaskarMurari. Unfortunately, we have tried removing and reinstalling the webview2 component. It actually doesn't seem to want to remove from the machine, just shows us a blank window when trying to uninstall. We were able to remove it by other means though, and when re-installed, it is the same / latest version that MS has to offer. We also did the same process and removed / reinstalled AutoCAD 2023 and the same version was installed with CAD. So there doesn't seem to be a way to make things work as intended while still actually using the features that rely on webview2.
I believe we have found that the issue was related to the Citrix VDA (vitrual delivery agent) version installed on our server. We have been on an older known good working version, but it seems to not like the newer webview2 applications used in 2023 ACAD (and potentially other software in the future).
So through lots of painstaking troubleshooting (thank you!), our systems admin finally updated the VDA version and everything seems to be working without issue. Caveat: We initially started with the issue on a server running Win Server 2016, through the troubleshooting process, we started fresh with a Win Server 2019. I don't know for sure if upgrading the VDA on a 2016 server would just work or not, so wanted to throw that out there.
I was experiencing the same issue with at least 8 instances of the Webviewer2 opening in the background. I was testing the new Trace and Markup features in ACAD 2023 (although i was using acad Arch as ACAD). As advised I renamed the webviewer2 to .old, and guess what, the 2 commands at least didn't work.
I had roll back the changes by accessing the Windows Start application, left click on it -> select "All Apps" button on top right of popup window -> select "AutoCAD 2023 - English" folder and scroll down to "Reset Settings to Default" option.
Wouldn't it be nice if AutoCAD, which is already a buggy pile of doggy doo, stayed in their lane and didn't try to pile in everyone else's buggy code so that we could have a product, that we pay an incredible amount of money for, that just worked? I'm not even counting the lost productivity cost when we have to deal with crashes. That is probable more then doubles the fee they are charging.
So I have to wonder, WHY are problems like this not addressed? At what level are they prevented from reviewing and fixing things like this? Reuse of components is great until that component breaks and you have no control over it (see: when AWS breaks, so can Autodesk licensing....)
This fix keeps other microsoft programs from loading . I use a VPN and it crashed, Teams will not work. Yes it will allow autocad to work the way it should without big brother getting in our business.
To learn more check out our documentation, a history of .NET browser controls, our Win32 announcement, additional WebView2 resources, and watch the demo of the usage of the WebView2 control from the .NET Conf 2020 keynote below.
Going forward, we will continue updating the WebView2 SDK approximately every 6 weeks driven by your feedback. To keep up with the latest updates checkout our Release Notes and follow the WebView2 Announcements Repo.
There are known bugs with the z-order on WinForms and WPF: If you could try it out or better describe your scenario in the WebView2 Feedback repo linked in the article, the team would be happy to follow up.
The version of the package is dependent on the version of the WebVIew2 Runtime required to run the package. The pre-release package requires the latest version of the WebView2 Runtime to work. Read more here: -us/microsoft-edge/webview2/concepts/versioning
The windows desk top version of Manager now used Edge / Webview2. Older versions used widows Internet explorer. You can block Webview2 internet access via your antvirus software (if yours support that) as Manager does not need webview2 to have internet access.
Thank you. I have downloaded Evergreen as recommended. The Manager works. I am now making myself familiar with the software and setting up. We are just a startup. Maybe later we will go with a server version or cloud.
Authentication Server is installed as part of the Blue Prism Hub installation (version 4.6 or later) if using the Blue Prism API and/or browser-based Control Room with version 7.1 and later. A Blue Prism environment must then be configured to use Authentication Server in order to allow users to log in via Authentication Server only.
Blue Prism native and Active Directory authentication can still be used to authenticate runtime resources, AutomateC commands, and when calling web services exposed on runtime resources. These requests cannot be authenticated via Authentication Server.
A Microsoft Edge WebView2 browser which delivers the embedded Authentication Server login dialog required to enable users to log into Authentication Server from the Blue Prism interactive client. The associated WebView2 runtime must be installed locally on any machine that runs the Blue Prism interactive client. For more details, see -us/microsoft-edge/webview2/concepts/distribution.
d3342ee215