Hello,
Please note all testing has been done on Windows 10 1709 and 1803.
We are a financial institution and have the need to set compatibility view mode for The Federal Reserve. The sites are 170.209.0.2 and 170.209.0.3 (they are only accessible at a Financial institution with a Federal Reserve VPN router).
We've tried a login script method via Desktop Authority to set this registry key and we've also tried GPO to set this registry key. The key is HKU\Software\Microsoft\Internet Explorer\BrowserEmulation\ClearableListData\UserFilter. Desktop Authority
sets the key without issue. GPO does not, so for this case we will continue to use Desktop Authority to set the key at login (or by running the login script out of the NETLOGON share).
Upon initial logon this is working as we check the Compatibility View Settings under IE11's Gear menu. We see these two sites plus 10 others. The site list was created on one machine and then exported as a reg key. I run process explorer
and filter on Operation is RegSetValue and path contains UserFilter. I see our Desktop Authority login script correctly set this key, and its 518 bytes long. I launch IE and the sites are all there. But then at some point usually a minute
or two later after closing IE, there are 10 additional RegSetValue from rundll32.exe slowly chipping away at the UserFilter registry key (going from 518 bytes to 476,436,388,356,298,254,216,184,144 then finishing on 104 bytes).
Now going into IE after rundll32.exe manipulates this key, all of those preprogrammed sites are GONE, except for two, 192.168.1.9 and myappro.com. These two are also in the bigger list so I'm not sure why only these two survive. I checked group
policy and I cannot find anywhere this is being set, thats why I resorted to Process Monitor to try to figure out what is setting this. In the stack trace for rundll32.exe I see two items from inetcpl.cpl which are ShowHelpPageW and ClearMyTracksByProcessW
using rundll32.exe so it looks like that is what is setting this key.
Any idea how or where its getting the two compatibility sites from? We do have a GPO set to delete history on exit, but if that were to delete compatibility sites, then ALL sites should be removed, not just two leftovers remaining in the list.
Unfortunately talking to the Federal Reserve's tech support is like speaking to a brick wall. They don't want to hear ANYTHING because they have their guard up all the time. The security there is very tight. They do not want to hear that
setting X-UA-Compatible meta tag to the HTTP headers of their site would automatically make this work. The problem is if we go to do a wire transfer on their site, its just a blank white screen UNLESS its in compatibility view. They will not
support other browsers (Edge, Firefox, Chrome). IE 11 must be used or the site will not work.
Thanks for your assistance.