HCHTech
Well-Known Member
- Reaction score
- 4,204
- Location
- Pittsburgh, PA - USA
Remember back in the Windows XP days, there was a Microsoft tool that would list all of the products that had been installed with the MSI installer on a computer. If you had a computer that kept popping up an installer dialog with an error something like "Install source unavailable", and the product no longer lived on the computer; you could run that tool, find the offending entry and delete it.
Something like that, anyway. I'm pretty sure that tool went away with Windows 7.
Anyway, I have a client's workstation that has some kind of corruption in the MSI installer. Anytime I try to install any software that uses the MSI installer, I get a popup referring to a pending install of the 2014 version of Sage 50, and it won't let the current install continue. The current version of Sage 50 is on the computer, but the 2014 version no longer is. A search through the registry did not find any entries for the 2014 version, and running the Tweaking all-in-one tool for repairing the MSI installer didn't help. If that old tool still existed, I would say this is a perfect problem for it to solve.
So before I suggest more drastic steps like an complete uninstall/clean/reinstall of Sage 50 or a Windows reload, does anyone have suggestions for a more surgical fix?
Something like that, anyway. I'm pretty sure that tool went away with Windows 7.
Anyway, I have a client's workstation that has some kind of corruption in the MSI installer. Anytime I try to install any software that uses the MSI installer, I get a popup referring to a pending install of the 2014 version of Sage 50, and it won't let the current install continue. The current version of Sage 50 is on the computer, but the 2014 version no longer is. A search through the registry did not find any entries for the 2014 version, and running the Tweaking all-in-one tool for repairing the MSI installer didn't help. If that old tool still existed, I would say this is a perfect problem for it to solve.
So before I suggest more drastic steps like an complete uninstall/clean/reinstall of Sage 50 or a Windows reload, does anyone have suggestions for a more surgical fix?