Webbrowser control ignores FEATURE_BROWSER_EMULATION reg entry

Question

Im developing a custom browser solution with .net's Webbrowser control. To disable the IE-Compatibilty View, I set the registry entry Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION:

[Sreenshot regedit] http://zbirk.mirk.at/browserreg.png "Screenshot"

i tried to use the values: dword=8000,dword=8888,dword=9000, but the webbrowser control seems to ignore these reg entries.

Maybe someone had this problems too and may help me.

This issue occurs consistently when running VS2010 x64 in the debugger. However, after publishing the app and running the .exe the registry setting that you describe takes effect properly. — pgfearo, Jun 06 '12 at 19:11

score 3 · Answer 1 · answered Mar 27 '12 at 20:31

The WebBrowser control definately DOES respect these keys.

Remember that while taskman may show application.exe in the name column, if you are debugging the exe name is application.vshost.exe

So in my application sI just attempt to create the key every time the app runs. If it fails to create it (because it already exists) then I continue running, if it creates the key then I inform the user that they need to restart the application.

score 2 · Answer 2 · answered Oct 27 '12 at 06:16

2

ensure that you are not running within vshost

the app name would be different ie appname.vshost.exe

answered Oct 27 '12 at 06:16

Ian---

63
5

score 1 · Answer 3 · answered Mar 17 '17 at 18:36

I too could not see that FEATURE_BROWSER_EMULATION made any difference in my application.

I was testing the FEATURE_BROWSER_EMULATION functionality by manually editing the registry with regedit. Nothing I did made any difference. My hosted page was still failing on any new-ish JavaScript and could not load external libraries.

I found my mistake:

I was editing the 64-bit view of the registry with regedit. My app was running as a 32-bit app and looking at the 32-bit view of the registry. That's why my changes to the registry seemed to have no impact on my application. By the way, the WPF project template defaults to "Prefer 32-bit."

Manually editing with regedit within the Wow6432Node key worked:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION

Of course, setting the DWORD value programmatically within your application will also work, since your 32-bit application will edit within the Wow6432Node.

Everyone keeps talking about `vhost` this is what I was looking for, thanks man. — Akash Shrivastava, Dec 12 '19 at 09:59

score 1 · Answer 4 · answered Mar 28 '12 at 01:49

Thx for your reply, now its working.

Her is my working peace of code:

public void setIEcomp()
    {
        String appname = Process.GetCurrentProcess().ProcessName+".exe";
        RegistryKey RK8 = Registry.LocalMachine.OpenSubKey("Software\\Microsoft\\Internet Explorer\\Main\\FeatureControl\\FEATURE_BROWSER_EMULATION",RegistryKeyPermissionCheck.ReadWriteSubTree);            
        int value9 = 9999;
        int value8 = 8888;
        Version ver = webBrowser1.Version;
        int value = value9;
        try
        {
            string[] parts = ver.ToString().Split('.');
            int vn = 0;
            int.TryParse(parts[0], out vn);
            if (vn != 0)
            {
                if (vn == 9)
                    value = value9;
                else
                    value = value8;
            }
        }
        catch
        {
            value = value9;
        }
        //Setting the key in LocalMachine
        if (RK8 != null)
        {
            try
            {
                RK8.SetValue(appname, value, RegistryValueKind.DWord);
                RK8.Close();
            }
            catch(Exception ex)
            {
                //MessageBox.Show(ex.Message);
            }
        }
    }

If you solved it you should accept some answer. Have you solved it? — Coder12345, Oct 10 '13 at 19:39
I wonder if you were initially editing the 64-bit view of the registry with regedit. When you switched to setting the key programmatically, it worked because your program was editing the 32-bit view of the registry. — Wallace Kelly, Mar 17 '17 at 18:38

score 0 · Answer 5 · answered Jan 31 '22 at 14:13

An older post and solution is no longer accurate.

Running procmon and watching for FEATURE_BROWSER_EMULATION shows the following registry variables actually checked. This was for WINWORD.exe but other than that - take your pick...

HKU\S-1-5-21-[my-sid-paws-off]\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION\WINWORD.EXE

HKU\S-1-5-21-[my-sid-paws-off]\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION*

HKLM\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION(Default)

HKLM\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION\WINWORD.EXE

HKLM\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION\WINWORD.EXE

HKLM\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION*

HKLM\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION*

Webbrowser control ignores FEATURE_BROWSER_EMULATION reg entry

5 Answers5

Linked