@Caute_cautim, the quote you supplied requires a bit more context...
Internet Explorer is a component of the Windows operating system and follows the Lifecycle Policy for the product on which it is installed. [...] Beginning January 12, 2016, only the most current version of Internet Explorer available for a supported operating system receives technical support and security updates, as shown in the following table:Windows Desktop Operating Systems Internet Explorer Version
Windows Vista SP2 * Internet Explorer 9 Windows 7 SP1 Internet Explorer 11 Windows 8.1 Update Internet Explorer 11 Windows 10** Internet Explorer 11
Customers had until January 12, 2016, to upgrade their browser after which time the previous versions of Internet Explorer reached end of support. End of support means there are no more security updates, non-security updates, free or paid assisted support options, or online technical content updates.
Basically, Microsoft is saying those running Windows 7 will no longer receive support or maintenance for Internet Explorer 8, 9 or 10 and that the solution is to upgrade to IE11, which is supported on Win7 and was released through their normal "patch Tuesday" servicing cycles.
Since @mcnj reports that Edge works properly, we know he is running Win10 and therefore we also know his Internet Explorer is version 11 because that is the only IE ever released for Win10. Although there are no assurances that @mcnj is current on his maintenance, we do know that he is not fatally behind.
I think we can all agree with Microsoft's sentiment that staying current on maintenance is an important security control, independent of how much one may like or dislike a particular piece of software, the company, or their policies. Even Krebs agrees.
@mcnj hit the nail on the head with his comment, "[...] when one develops a website, they should make sure it works on all current browsers [...]" . Reporting this incorrect behavior is the correct answer. Tagging @amandavanceISC2 to ensure this gets noticed and reported to the proper personnel.
About the only thing I could add to what @mcnj already provided is to include the browser and OS version strings to maximize the chance of reproducing the problem. I can reproduce @mcnj's symptoms using IE 11.471.17134.0 on Windows 10 version 1802 (build 17134.471).
It sounds and feels like a self-fulfilling prophesy.
Perhaps Quantum Chemistry would resolve it quicker and provide greater insights.
I must be running IE6 on Windows 98
I "collected the evidence" before creating this thread. I planned on opening a support ticket, but figured I'd post it here first to share with the community. I'm pretty sure I have the troubleshooting part down. I didn't need my CISSP for that 😉
@denbesten thanks for testing. I'm running Windows 10 (1803), IE 11.285.17134.0