Michelle-138172 - Friday, September 22, 2017 8:28 AM
It's not the first time they hosed out version numbers - it was worse with one they did for 2005. I guess they do it because they are good at it due to a lot of experience 🙂
It could be the different versions messing things up - the whole caching process for updates, finding previous installs is just problematic.
That link you first have in the error has a vbscript to run that tries to fix the paths to installers - it's worth trying that.
There is also a link about trying to uninstall when you have issues - not exactly the same but similiar to what you are dealing with and might give you some more things to check:
Cleanly Uninstalling Stubborn SQL Server Components
Sue