It could be a stuck upstream cache, but you may not really have purged the cache well.

I use a tool (on windows) called 'ccleaner' by Piriform. (It used to be called 'crap cleaner'). It works well for clearing out history, cache, a lot of temp files (It still leaves a bunch behind), and so forth. Just download, install, and make sure that if you want the autocomplete history to save, you unclear the relevant options. Then run the 'cleaner' part.

BW

Internet Explorer 11 has a large number of flaws, and even now, shouldn't be considered usable for anyone with a choice. If you have the option, go into the control panel, programs and features, then the updates option. Remove IE 11.

Microsoft did not test it properly, and even now, umpteen months after the initial release, they have yet to fix their issues. EClinicalWorks, for one example, has a lot of problems running with IE11. (That's probably why they don't support Windows 8 with the software. Additional information about ECW at the end, for anyone that cares). Another example is almost every single major bank's business site throws errors at IE 11. When it first came out, I received at least nine panicked calls from accounting departments because they weren't able to do their normal daily bank work. (That was a busy couple of days). Reverting from IE 11 to IE 10 fixed the problems immediately. I find it reprehensible that Microsoft failed to test IE with _at least_ Chase, Bank of America, and Capital One's business sites. Testing with smaller ones? Well, that would take a while, and I can't blame them for that.

---
Aside on ECW. It's a popular electronic medical records software because it's less expensive for most small doctors. The problem is that from digging in the code and other work with it, it's been bastardized at least two different ways by the company. The first way is that their server is clearly designed to be installed and run on a Linux or other *nix platform, but their salespeople push it for windows servers. (Their programmers, on the other hand, are thrilled when it's run on a *nix box. It's a Tomcat driven system, using an ftp server and MySQL database. Which reminds me to talk to them about switching to MariaDB) The second way is that the client end was _very_ clearly originally written to be browser based. That's not a problem, but it looks like about half way or more through the development process, they decided they needed an actual windows _program_ to provide good interface with scanners and other electronic medical devices. That leads to the real problem - they didn't disconnect the program from the browser interface. To fix margins, you have to adjust them in IE, and if you are an office with IE locked down, it simply _doesn't start at all_.