Haven’t seen corruption on a journaling NTFS file system for years now. Chkdsk confirmed. Plus, I’m sure that corruption is only affecting the last piece of software that was installed. Veeerrrry coincidental. My hunch is that it’s MCEBuddy having a problem reading its own .conf file, after I did some extensive configuration within the GUI.
UPDATE: followed everything in FAQ (removing service, whacking Program Files directory, searching through indicated points in Registry and deleting related keys, picking files out of root of %HOMEPATH% [which should in an MCEBuddy folder there, instead of root] and rebooting).
Attempted clean install and guess what? Installer believes that MCEBuddy is still installed! Given choice to remove or repair, I selected remove and got this:
Again, this is not due to file system corruption. I haven’t seen something so hard to uninstall since McAfee in its heyday. This is ridiculous! It’s clear that proper error handling in the app and in the uninstall app are nowhere to be seen. So, here we sit…