IE 9 Trap: Can't uninstall, can't upgrade to IE 10 or 11,

Question

My main issue is that I cannot install IE 11. IE 9 is somehow blocking the installation of any other version of IE. Through Googling, I've found that this is a common issue but the only
real solutions seem to be uninstalling IE 9 or having someone from Microsoft supply files specific to the user/poster's computer that resolves the issue. I tried both offline and regular installers, I tried installing the prerequisites, I even
tried going to 10 first which resulted with the same issues as 11 ....any sort of basic trouble shooting has been tried.
I've also tried uninstalling IE 9 in every way possible including....
Going into "View installed updates" in "Programs and Features" to attempt uninstalling the IE9 update which failed with message "An error has occurred. Not all of the updates were successfully uninstalled."
Using the command prompt with administrator privileges ("Run as administrator" in the context menu) to run the FORFILES command - failed with multiple dialogs all showing "0x80070005: Access is denied."
FORFILES /P %WINDIR%\servicing\Packages /M Microsoft-Windows-InternetExplorer-*9.*.mum
To throw another wrench into the situation, this is a company-wide issue so even if Microsoft could provide user specific files to resolve the issue on my computer. I still have handfuls of other computers with the same issue.
Hopefully there's another solution out there but any help or suggestions are appreciated.

Answer 1

IE 9 is somehow blocking the installation of any other version of IE.
Try to find out what is really happening.  E.g. in some cases something is preventing users from getting complete maintenance at the IE9 level, so trying to install IE10 or IE11 might only confuse things. 
Using the command prompt with administrator privileges ("Run as administrator" in the context menu) to run the FORFILES command - failed with multiple dialogs all showing "0x80070005: Access is denied."
That's usually what code 5 means, so it would be explained as such but it could also mean that something unexpected happened, in which case you should run ProcMon to try to figure out what is really happening.  E.g. a very common cause of the problem
symptoms, and what this procedure was designed to try to work around, is corruption in WinSxS.  So, one possible meaning of the code might only be that  "Yes, there is corruption in your WinSxS." 
company-wide issue so even if Microsoft could provide user specific files to resolve the issue on my computer. I still have handfuls of other computers with the same issue.
Have you tried using MBSA to see if there is a pattern?  Unfortunately, I don't think it is quite as useful as it once was when Shavlik were supporting their HFNetChk  tool but perhaps you could get some clues from it?  Certainly supplementing
the reports with ProcMon traces would help clarify what was being found.
Good luck
Robert Aldwinckle