This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 48%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
Hi,
I have a strange problem when installing WebView2 on a new Windows Server 2019 Standard (Version 10.0.17763 Build 17763).
The problem is the same using the standalone installer (MicrosoftEdgeWebView2RuntimeInstallerX64.exe) or the bootstrap installer (MicrosoftEdgeWebview2Setup.exe).
When the installation is run with administrator privileges, there's one folder missing after the installation:
C:\Program Files (x86)\Microsoft\EdgeWebView\Application\102.0.1245.44\EBWebView\x64
Only the +x86 folder is there.
(On my laptop this works fine, both folders are available after running the setup)
When the installation is run on the Server with normal user privileges (=> installation in user specific folder), everything works fine, both folders are available after setup.
What is the reason for this behavior and how can it fixed? My .NET Application needs WebView2 from the x64 folder to run...
Best regards,
Andreas
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 0%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXP%3C/text%3E%3C/svg%3E)
Hi @Andreas Molisch ,
I tried to reproduce this issue with these two methods you mentioned but it still failed in Windows Server 2019 Standard Datacenter Version 10.0.17763 Build 17763 . I recommend that you could test this issue on other machines, if this issue only occur in the specific machine, then the problem should be related to the local environment. And if this case, I suggest that you can open a support ticket (create a support request) so that you can get more help. Thanks for your understanding.
Problem is solved!
I could solve this issue by reinstalling the Edge Browser (remove and install again) on the Windows Server. Afterwards the problem was gone and did not appear again.