MicrosoftEdge
There was a problem installing. Error code: 0x800700b7.
It has been unable to install, and later found the problem by checking the log, MicrosoftEdgeUpdate(1).log
Hidden system files appear in the Microsoft folder: Edge, EdgeUpdate, EdgeWebView, Temp, these are in the form of files, so folders cannot be created, as shown in the figure.
Among them, after EdgeWebView and EdgeUpdate were forcibly deleted by me, WebView2 was successfully installed. It seems that some programs will prevent the installation of Edge/WebView2. I hope that Edge/WebView2 will check whether there are abnormal files in the installation location during installation. If there are any, they will be deleted forcibly. The administrators will obtain the ownership, and then clear the read-only attribute to delete it. up.
The probability of occurrence is not low. At present, my program performs a strong deletion of the folders of EdgeWebView and EdgeUpdate, and WebView2 can be installed normally. I just suggest that the official can detect abnormal files and perform strong deletion. This part of the code is built into Edge/WebView2 to prevent Some malicious programs prevent installation in this way.
Hello @sln162,
Thanks for the heads up, we will investigate and add it to our backlog for the upcoming sprint.
Thanks!
In addition, it is recommended to check whether the registry is a brand-new installation before installation. If it is a new installation and the folder exists, you should delete the folder first, because I also found that there are folder permission problems on some machines, which lead to the installation of WebView2. fail If deleting the folder fails, set the owner of the folder permission to the administrators, give the administrators delete permission, and check whether there is write permission when creating a new folder.
@sln162 do we have a guess of which software is creating the files? Are the time stamp on those files suggest that the files are created at the time of installation or far before that? If it is around the time of installation, we might be able to take a procmon trace to figure out which process created them. I will pass the suggestions to Edge installer team. My personal opinion is that it is better to expose the issue and fix the root cause instead of hiding it. Who know what else might also happen if the root cause is not addressed.
@LiangTheDev To be sure, this is a problem that occurred before the installation, not the behavior of the installation. Let me talk about the present first: My program has added corresponding processing. If a file with the same name exists (EdgeWebView/EdgeUpdate/Temp), set the file owner to the administrator group, then obtain the ownership control of the file, and remove the read-only attribute to ensure that it can be enforced delete it.
When a file with the same name is encountered, it will be reported to my server. At this time, the download and installation of WebView2 has not yet started, so it is certain that the problem occurred before the installation.
In the past two months, I have received reports of 238 IPs, but we have solved them through the above solutions. After tracking their installation results, I found that they were all successful.
Of course, there is also the issue of folder permissions, which we have also dealt with, so we share the solution so that WebView2 and Edge can handle these two issues.
Going back to the original question, we don’t know what software is doing the trick. This is my guess, because the systems involved include: Win10/Win11/Win7, almost all systems exist. I also asked users, but users Express ignorance.
Hi, sln162
I access the same problem like yours. I could install the webview2 after I just did the following steps.
