I just chose the Intel processor ID utility because this as a pretty simple and not very important program already installed on my computer to test the effects of various potential solutions to my problem, instead of something like, say, iTunes, which creates a huge footprint and writes stuff all over the Registy, and would therefore be a real pain to try and repair if I screwed things up (though I am making disk images all the time right now). My point is that I could have chosen any program that uses the MSI installer, whether for install, reinstall, repair or uninstall, and get the same error 2203 impasse. I was hoping that the MSI logs would point to some specific Windows problem, as I don't know how to interpret them myself. Are there any other system logs or third-party logging programs that might be able to pinpont exactly where things go wrong? Of course Event Viewer records the problem, but this also does not provide much help to the average use. Following online threads to Windows technical resources is usually a waste of time, as their technical assistance people are rarely able to solve anything if Checkdisk, SFC and DISM don't fix it -- and as I mentioned, the so-called Microsoft Installer diagnostic cab only succeeded in ruining two other installed programs for me, which I am now unable to reinstall again.
Thanks,
Stephen