Skip to content
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

Webview2 application running in a Citrix environment #1082

Open
AndersAlfredsson opened this issue Mar 17, 2021 · 9 comments
Open

Webview2 application running in a Citrix environment #1082

AndersAlfredsson opened this issue Mar 17, 2021 · 9 comments
Assignees
Labels
bug Something isn't working priority-low We have considered this issue and decided that we will not be able to address it in the near future. tracked We are tracking this work internally.

Comments

@AndersAlfredsson
Copy link

AndersAlfredsson commented Mar 17, 2021

We have faced problems with Citrix hooks when running our application which is using WebView2. The hooks in Citrix is preventing the WebView2 component from starting. This can be fixed by adding the WebView2 process as an exception from all Citrix hooks, this can be done in the registry as described in this link: https://support.citrix.com/article/CTX107825.

Would it be possible to make this configuration default in Windows or possibly make it a setting in WebView2?

AB#32169480

@champnic champnic added bug Something isn't working tracked We are tracking this work internally. labels Mar 18, 2021
@champnic
Copy link
Member

Thanks for the feedback @AndersAlfredsson - you may have provided the solution to #675! :)

I'll work with our outreach team to see if we can get Citrix to update their default configuration.

@sanjayhirani
Copy link

Hi. I tried adding WebView2 process as an exception from all Citrix hooks (both 32bit and 64bit) But still get the same errors. We have 2 different Citrix environments. One being 7.15 on Server 2016 and the other Xenapp 6.5 on Server 2008 R2. It works fine on Server 2016 but not on the 2008 R2 environment.

@champnic
Copy link
Member

@sanjayhirani Are you able to update and just use Server 2016? Does it work on 2008 R2 without Xenapp?

@sanjayhirani
Copy link

Hi. These servers cannot be upgraded to 2016 as they host XenApp 6.5. I will try it out on a non XenApp 2008 R2 server later today and let you know.

@sanjayhirani
Copy link

It worked without issue on a server that doesn't have XenApp. I then went back to the XenApp server and removed all API hooks by setting this reg key:

"HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\LoadAppInit_DLLs = 0 [REG_DWORD]"

Which then allowed the app to load the webview2.

Thanks for the help.

@champnic
Copy link
Member

Thanks for confirming @sanjayhirani, and glad you got it working!

@dIeGoLi
Copy link

dIeGoLi commented Jun 13, 2022

I am facing as well core webview2 process failed event with reason unresponsive and exitcode 259. It is a 2016 citrix terminal server. I am using the fixed version. Will try the registry key :)

@Blackwater99
Copy link

I am dealing with this issue. Have tried the Hook Fix, have checked sanjayhirani's registry key setting. Its set to 0. Still cannot get webview2 to open thought citirix. Does anyone else have ideas? It works on our 2016 server, but not 2012/2008.

@Blackwater99
Copy link

@aseme Looking at the article: https://www.petenetlive.com/KB/Article/0001657

Can you try the described workaround but use msedgewebview2.exe instead of msedge.exe?

open the registry Editor (regedit) and navigate to;

HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services > CtxUvi
Locate the UviProcesExcludes REG_SZ value, edit it and add ‘msedge.exe;‘ 'msedgewebview2.exe' to the end.

image

Theres probably one service you can restart, but I simply rebooted the server, (problem solved).

This is what worked for us. For anyone else that is struggling.

@github-actions github-actions bot added the priority-low We have considered this issue and decided that we will not be able to address it in the near future. label Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-low We have considered this issue and decided that we will not be able to address it in the near future. tracked We are tracking this work internally.
Projects
None yet
Development

No branches or pull requests

7 participants