We had a ransom-ware scare a couple weeks back. Been looking for new ways to tighten up security on the network. Yesterday I changed the User Account Control (UAC) settings on all users via Group Policy. I changed them to this:
Admin Approval Mode for the Built-in Administrator account = Disabled
Allow UIAccess applications to prompt for elevation without using the secure desktop = Disabled
Behavior of the elevation prompt for administrators in Admin Approval Mode = Prompt for consent on the secure desktop
Behavior of the elevation prompt for standard users = Prompt for credentials
Detect application installations and prompt for elevation = Enabled
Only elevate executables that are signed and validated = Disabled
Only elevate UIAccess applications that are installed in secure locations = Enabled
Run all administrators in Admin Approval Mode = Enabled
Switch to the secure desktop when prompting for elevation = Enabled
Virtualize file and registry write failures to per-user locations = Enabled
Shortly there after I received a report where webpages with textboxes were locking up. We do a lot of online forms for e-filing, research, etc. On webpages with textboxes everything works fine including links, navigation, etc. First time a textbox is used still okay. But when the user tries to enter content in a textbox a second time the page become unresponsive. For example, doing research she can type in a textbox to search and bring up a case on Westlaw. But when she tries to go back and search another term, it won’t let her put anything into the search box the second time. Similar thing happens with printing. User can print from a website once but when they print a second time nothing happens. All IE menus unresponsive. Nothing happens with Ctrl + P. Both issues clear if the user closes IE and reopens. A nuisance, though.
Users have Windows 7 Professional 64bit and Internet Explorer 11.
It can be recreated on employee workstations. It cannot be recreated on mine, but then I’m an administrator on the network and local administrator on my workstation. Today I have more reports of the same problem. Leads me to believe it is related to the security change above. Anyone else see this happen? Is it related to UAC? If so, what UAC setting needs to change to undo this?