My guess is since you have remamants of failed installation still present in your system that is why you cannot install the new instance. This can be fixed by deleting few registry keys related to SQL server. Follow below method , this method was given by Microsoft forum team and is recommended way to remove have helped me and forum users many time . If you have multiple instances below suggesstion would not work so dont use it.
First please refer to below Microsoft support link for what actions to follow before removing SQL Server instance. Its is for 2008 r2 but would be applicable to 2012 as well.
http://support.microsoft.com/kb/955499/en-gb
If still you face problem you might as well try below suggesstion which involves removing registry entries.
Note: Removing necessary registry entries might cause inconsistency so backup registry before doing changes.
•1. Uninstall the existing SQL Server and all the components from the add remove program.
•2. Backup the registry . Please read in details the MS link before proceeding.
•3. Delete the following keys using regedit:
◦--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
◦--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
•4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing SQL Server.
•5. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing SQL Server.
•6. Rename all the SQL Server folders in the computer.
•7. Reboot the machine.
If you dont find this useful or have confusion dont proceed. Open a case with Microsoft and allow them to have a look at your system. with my experience with many failed installation registry keys are left in corrupted state and only solution would be to remove them.But you need expert to fiddle with registry
PS: Above method was suggested in SQL server forum and works well.
Of course if you can please revert it would be helpful
I was able to resolve the issue by uninstalling and reinstalling the entire Visual Studio and SQL Server software stack on my laptop.
The cause of the problem appears to be with the anti-virus that corporate security has setup on my laptop. Apparently, the group policy is too restrictive and blocking the update from successfully performing its job. There are no failures or warnings to this fact. I was able to isolate this as the cause because I have an identical setup on remote desktop servers that I can log in to. I was able to successfully update VS2017 to 15.9.9 and edit script tasks/components without error on the remote desktops.
Upon inquiring with our corporate security team as to whether my group policy matches the servers, it was confirmed that mine did not match, which is not necessarily a problem - user and server policies are different. However, it was confirmed that I was in the wrong user group policy. I was switched into a different policy and the installation was successful. This further backs my suspicion of virus scanner interference because I had to previously ask that the virus scanner be disabled so that I could perform re-installations (this was the third time that I had to reinstall the stack).
Best Answer
Hmm interesting it's calling out SSIS. This is just going out in a limb, but can you use the SQL installer to ensure SSIS is installed and then retry: https://docs.microsoft.com/en-us/sql/integration-services/install-windows/install-integration-services?view=sql-server-ver15
Hopefully that fixes the underlying issue.