Internet Explorer Icon: Here to Stay? Microsoft Reverses Decision on IE Erasure After Corporate Backlash
In the light of Microsoft’s product policy, the Internet Explorer (IE) browser was previously announced to have ended its support, followed by the company’s intent to expunge it from Windows 10/11 entirely. Users were abruptly shifted to Microsoft Edge as the software giant began forcibly disabling the IE browser through a Windows update. Any attempt to launch IE was met with an automatic redirect to Microsoft Edge.
Moreover, the company initiated the process of removing all traces of Internet Explorer from their Windows 10/11 systems, including the IE browser icon, related elements, and settings via a Windows update.
However, this sudden decision caused quite a stir among corporate clients. With a significant portion of these customers still dependent on IE, Microsoft’s drive to eradicate the browser was met with considerable backlash. Listening to the outcry from the corporate sector, Microsoft finally decided to allow customization options to retain IE components if required.
In their recent product announcement, Microsoft stated:
“In response to customer feedback, the IE11 visual reference, such as the IE11 icon in the Start menu and taskbar, will no longer be removed by the Windows update as previously mentioned. Organizations (government enterprises, educational institutions, etc.) can control the time when IE-related elements are deleted. If customers have not configured these options, the system will continue to remove IE11’s visual reference elements.”
As per the announcement, it’s imperative for IT administrators in enterprises to modify group policies to regulate devices in the intranet. If they do not actively set these configurations, Microsoft’s settings will be adopted by default. Therefore, it’s crucial for the enterprises that need to maintain IE to act promptly.
This significant policy shift by Microsoft once again highlights the tech giant’s responsive attitude to its user base feedback and underlines the intricate balance needed to navigate legacy software transition.