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

[Problem/Bug]: Setting any policy in the registry will cause Edge to display 'managed by your organization' #4106

Open
sln162 opened this issue Oct 26, 2023 · 2 comments
Assignees
Labels
bug Something isn't working tracked We are tracking this work internally.

Comments

@sln162
Copy link

sln162 commented Oct 26, 2023

What happened?

When I set any value, even if it is meaningless, in the registration policy location of WV2, SOFTWARE\Policies\Microsoft\Edge\WebView2, and do not set any value in SOFTWARE\Policies\Microsoft\Edge, when I open the settings option of any version of Edge (stable/Beta/Dev/Canary), it will display "managed by your organization", but when I go in and view it, I cannot see any policy. The policy of WebView2 must also be a child of Edge, I don't know if this should belong to the Edge department or the WV2 department, but I don't think it should be like this.I think the policy for setting WV2 should not be displayed on the Edge.
image
image

image
image
image

Importance

Moderate. My app's user experience is affected, but still usable.

Runtime Channel

Stable release (WebView2 Runtime), Prerelease (Edge Canary/Dev/Beta)

Runtime Version

No response

SDK Version

No response

Framework

Winforms

Operating System

Windows 11

OS Version

No response

Repro steps

Create a subkey for SOFTWARE\Policies\Microsoft\Edge\WebView2 in the registry location, create a value with any name, open the Edge browser, and click on the settings icon.

Regression

No, this never worked

Last working version (if regression)

No response

AB#47286842

@sln162 sln162 added the bug Something isn't working label Oct 26, 2023
@vickiez vickiez added the tracked We are tracking this work internally. label Oct 27, 2023
@vickiez
Copy link
Contributor

vickiez commented Oct 27, 2023

Thanks for reporting this @sln162! We'll take a look and see if the issue needs to be routed to Edge team, will let you know here when there is an update.

@sln162
Copy link
Author

sln162 commented Oct 28, 2023

@vickiez Okay, I'm looking forward to good news, because I know some users will not be used to seeing this prompt in Edge and will search for solutions through search engines. The solutions they find are to delete the entire Edge policy, which can certainly help them solve the problem, but it also affects WebView2, because WebView2 is a child of Edge in the registry, and users will delete all policies at once.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working tracked We are tracking this work internally.
Projects
None yet
Development

No branches or pull requests

2 participants