Yes, we've seen this issue as well. We have a case open with Microsoft. It
appears to be related to gzip compression of files sent by Tomcat webserver,
the urlmon.dll file that gets updated, and network latency. For us, the issue
appears when the user is connected over wireless. The issue disappears when
they plug directly to network via cable. In addition, per Microsoft, a
temporary workaround (if you can't connect directly to network via cable or
dock laptop) is to un-check "Use HTTP 1.1" in Internet Explorer advanced
options. This has helped us prevent uninstalling the patch until Microsoft
can provide an update. They also provided another alternative whereby you can
copy an older urlmon.dll file into the program files directory of
iexplore.exe, along with creating a blank iexplore.exe.local file in same
location, so you have two client side "resolutions". To prevent modification
of clients, we're also look into temporarily disabling gzip compression on
the webserver; but we have yet to test this option and/or to determine the
ramifications of doing so. If it's an easy change, then we'd rather persue
the "temporary" backend resolution so we wouldn't have to modify the clients;
either way, we're trying to keep the patch applied in our environment until
Microsoft can provide an update.
