|
Patch reliability is unclear, but widespread attacks make patching prudent. Go ahead and patch, but watch out for potential problems. |
But then clicking on either of these .EXE files results in Edge being opened.
I get this:
Opening it up and looking at its innards I found the xml file:
<?xml version=”1.0″ encoding=”UTF-8″ standalone=”yes”?>
<!– Copyright (c) Microsoft Corporation –>
<!– Note: This manifest needs to be kept in sync with iexplore.exe.manifest –>
<assembly xmlns=”urn:schemas-microsoft-com:asm.v1″ manifestVersion=”1.0″>
<assemblyIdentity version=”5.1.0.0″
processorArchitecture=”x86″
name=”Microsoft.InternetExplorer”
type=”win32″/>
<description>Internet Explorer</description>
<application xmlns=”urn:schemas-microsoft-com:asm.v3″>
<windowsSettings>
</windowsSettings>
</application>
<compatibility xmlns=”urn:schemas-microsoft-com:compatibility.v1″>
<application>
<!–This Id value indicates the application supports Windows Vista/Server 2008 functionality –>
<supportedOS Id=”{e2011457-1546-43c5-a5fe-008deee3d3f0}”/>
<!–This Id value indicates the application supports Windows 7/Server 2008 R2 functionality–>
<supportedOS Id=”{35138b9a-5d96-4fbd-8e2d-a2440225f93a}”/>
<!–This Id value indicates the application supports Windows 8/Server 2012 functionality–>
<supportedOS Id=”{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}”/>
<!– This Id value indicates the application supports Windows Blue/Server 2012 R2 functionality–>
<supportedOS Id=”{1f676c76-80e1-4239-95bb-83d0f6d0da78}”/>
<!– This Id value indicates the application supports Windows Threshold functionality–>
<supportedOS Id=”{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}”/>
</application>
</compatibility>
</assembly>
Looks like it isn’t supported in Windows 11.
Wow, check this out!
So I’ve managed to launch IE 11 (instructions are given at the URL shown in the background), but it will briefly load a requested page, then come back with the error, “We were unable to return you to xxx.yyy.”
There may be some way to get around this issue but it will take some digging. For now, I’m just astonished that IE does, in fact, seem to be present on Windows 11. My understanding was that it was simply not present, except for “IE mode” in Edge.
Query: in your opinion, would Internet Explorer sudden death be a better option over the long-term lingering fade out?
In those niche areas of Windows where parts of IE are still used, the code has to be replaced. Microsoft would likely prefer to cut it out in bits and pieces and risk fewer likelihoods of disruptions than to rip it out in force and have something, somewhere, stop working or throwing BSOD’s.
Just my opinion. From a programmer’s point of view, replacing active code is like walking on eggs.
Ok, for some reason or other, my system must be an outlier.
Win10 22H2 (OS Build 19045.2486) and Edge got updated to version 110.0.1587.46 (the Feb 14 update) this morning.
And, although I now see an “Internet Explorer 11 is now out of support” message when I try to run it (it use to just say Switch to Edge), it still works just fine and I can click the × on the right to close the message!
Maybe it didn’t get “removed” because neither MSIE nor Edge are my default browser (that’s SeaMonkey 2.53.15)
Microsoft can’t (yet) remove Internet explorer so it lives on in Windows 10 and 11.
Internet Explorer is never removed on LTSC editions of Windows 10
and it’s STILL ALIVE on Windows 7 Embedded Standard, Server 2008 R2 & Server 2012 editions as well as IE got a new cumulative update (KB5029243) in August 2023 – any newly released IE updates for these pre-Win10 versions CONTRADICTS IE’s death
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
